1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. (c) <optionally add copywriters name>
5 ===================================
6 OPNFV Barometer User Guide
7 ===================================
13 Barometer collectd plugins description
14 ---------------------------------------
15 .. Describe the specific features and how it is realised in the scenario in a brief manner
16 .. to ensure the user understand the context for the user guide instructions to follow.
18 collectd is a daemon which collects system performance statistics periodically
19 and provides a variety of mechanisms to publish the collected metrics. It
20 supports more than 90 different input and output plugins. Input plugins
21 retrieve metrics and publish them to the collectd deamon, while output plugins
22 publish the data they receive to an end point. collectd also has infrastructure
23 to support thresholding and notification.
25 Barometer has enabled the following collectd plugins:
27 * *dpdkstat plugin*: A read plugin that retrieve stats from the DPDK extended
30 * *dpdkevents plugin*: A read plugin that retrieves DPDK link status and DPDK
31 forwarding cores liveliness status (DPDK Keep Alive).
33 * `ceilometer plugin`_: A write plugin that pushes the retrieved stats to
34 Ceilometer. It's capable of pushing any stats read through collectd to
35 Ceilometer, not just the DPDK stats.
37 * *hugepages plugin*: A read plugin that retrieves the number of available
38 and free hugepages on a platform as well as what is available in terms of
41 * *Open vSwitch events Plugin*: A read plugin that retrieves events from OVS.
43 * *Open vSwitch stats Plugin*: A read plugin that retrieves flow and interface
46 * *mcelog plugin*: A read plugin that uses mcelog client protocol to check for
47 memory Machine Check Exceptions and sends the stats for reported exceptions
49 * *RDT plugin*: A read plugin that provides the last level cache utilization and
50 memory bandwidth utilization
52 All the plugins above are available on the collectd master, except for the
53 ceilometer plugin as it's a python based plugin and only C plugins are accepted
54 by the collectd community. The ceilometer plugin lives in the OpenStack
57 Other plugins existing as a pull request into collectd master:
59 * *SNMP Agent*: A write plugin that will act as a AgentX subagent that receives
60 and handles queries from SNMP master agent and returns the data collected
61 by read plugins. The SNMP Agent plugin handles requests only for OIDs
62 specified in configuration file. To handle SNMP queries the plugin gets data
63 from collectd and translates requested values from collectd's internal format
64 to SNMP format. Supports SNMP: get, getnext and walk requests.
66 * *Legacy/IPMI*: A read plugin that reports platform thermals, voltages,
67 fanspeed, current, flow, power etc. Also, the plugin monitors Intelligent
68 Platform Management Interface (IPMI) System Event Log (SEL) and sends the
70 * *virt*: A read plugin that uses virtualization API *libvirt* to gather
71 statistics about virtualized guests on a system directly from the hypervisor,
72 without a need to install collectd instance on the guest.
74 **Plugins included in the Danube release:**
81 collectd capabilities and usage
82 ------------------------------------
83 .. Describe the specific capabilities and usage for <XYZ> feature.
84 .. Provide enough information that a user will be able to operate the feature on a deployed scenario.
86 .. note:: Plugins included in the OPNFV D release will be built-in to the fuel
87 plugin and available in the /opt/opnfv directory on the fuel master. You don't
88 need to clone the barometer/collectd repos to use these, but you can configure
89 them as shown in the examples below.
91 The collectd plugins in OPNFV are configured with reasonable defaults, but can
94 Building all Barometer upstreamed plugins from scratch
95 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
96 The plugins that have been merged to the collectd master branch can all be
97 built and configured through the barometer repository.
100 * sudo permissions are required to install collectd.
101 * These are instructions for Ubuntu 16.04
103 To build and install these dependencies, clone the barometer repo:
107 $ git clone https://gerrit.opnfv.org/gerrit/barometer
109 Install the build dependencies
113 $ ./src/install_build_deps.sh
115 To install collectd as a service and install all it's dependencies:
119 $ cd barometer/src && sudo make && sudo make install
121 This will install collectd as a service and the base install directory
122 will be /opt/collectd.
124 Sample configuration files can be found in '/opt/collectd/etc/collectd.conf.d'
127 - If you plan on using the Exec plugin, the plugin requires non-root
128 user to execute scripts. By default, `collectd_exec` user is used. Barometer
129 scripts do *not* create this user. It needs to be manually added or exec plugin
130 configuration has to be changed to use other, existing user before starting
133 - If you don't want to use one of the Barometer plugins, simply remove the
134 sample config file from '/opt/collectd/etc/collectd.conf.d'
136 - If you are using any Open vSwitch plugins you need to run:
140 $ sudo ovs-vsctl set-manager ptcp:6640
143 Below is the per plugin installation and configuration guide, if you only want
144 to install some/particular plugins.
148 Repo: https://github.com/collectd/collectd
152 Dependencies: DPDK (http://dpdk.org/)
154 .. note:: DPDK statistics plugin requires DPDK version 16.04 or later
156 To build and install DPDK to /usr please see:
157 https://github.com/collectd/collectd/blob/master/docs/BUILD.dpdkstat.md
159 Building and installing collectd:
163 $ git clone https://github.com/collectd/collectd.git
166 $ ./configure --enable-syslog --enable-logfile --enable-debug
170 .. note:: If DPDK was installed in a non standard location you will need to
171 specify paths to the header files and libraries using *LIBDPDK_CPPFLAGS* and
172 *LIBDPDK_LDFLAGS*. You will also need to add the DPDK library symbols to the
173 shared library path using *ldconfig*. Note that this update to the shared
174 library path is not persistant (i.e. it will not survive a reboot).
176 Example of specifying custom paths to DPDK headers and libraries:
180 $ ./configure LIBDPDK_CPPFLAGS="path to DPDK header files" LIBDPDK_LDFLAGS="path to DPDK libraries"
182 This will install collectd to /opt/collectd
183 The collectd configuration file can be found at /opt/collectd/etc
185 To configure the dpdkstats plugin you need to modify the configuration file to
195 ProcessType "secondary"
198 EnabledPortMask 0xffff
199 PortName "interface1"
200 PortName "interface2"
204 To configure the dpdkevents plugin you need to modify the configuration file to
209 LoadPlugin dpdkevents
210 <Plugin "dpdkevents">
215 ProcessType "secondary"
218 <Event "link_status">
219 SendEventsOnUpdate true
220 EnabledPortMask 0xffff
221 PortName "interface1"
222 PortName "interface2"
223 SendNotification false
226 SendEventsOnUpdate true
228 KeepAliveShmName "/dpdk_keepalive_shm_name"
229 SendNotification false
233 .. note:: Currently, the DPDK library doesn’t support API to de-initialize
234 the DPDK resources allocated on the initialization. It means, the collectd
235 plugin will not be able to release the allocated DPDK resources
236 (locks/memory/pci bindings etc.) correctly on collectd shutdown or reinitialize
237 the DPDK library if primary DPDK process is restarted. The only way to release
238 those resources is to terminate the process itself. For this reason, the plugin
239 forks off a separate collectd process. This child process becomes a secondary
240 DPDK process which can be run on specific CPU cores configured by user through
241 collectd configuration file (“Coremask” EAL configuration option, the
242 hexadecimal bitmask of the cores to run on).
244 For more information on the plugin parameters, please see:
245 https://github.com/collectd/collectd/blob/master/src/collectd.conf.pod
247 .. note:: dpdkstat plugin initialization time depends on read interval. It
248 requires 5 read cycles to set up internal buffers and states. During that time
249 no statistics are submitted. Also if plugin is running and the number of DPDK
250 ports is increased, internal buffers are resized. That requires 3 read cycles
251 and no port statistics are submitted in that time.
253 The Address-Space Layout Randomization (ASLR) security feature in Linux should be
254 disabled, in order for the same hugepage memory mappings to be present in all
255 DPDK multi-process applications.
261 $ sudo echo 0 > /proc/sys/kernel/randomize_va_space
263 To fully enable ASLR:
267 $ sudo echo 2 > /proc/sys/kernel/randomize_va_space
269 .. warning:: Disabling Address-Space Layout Randomization (ASLR) may have security
270 implications. It is recommended to be disabled only when absolutely necessary,
271 and only when all implications of this change have been understood.
273 For more information on multi-process support, please see:
274 http://dpdk.org/doc/guides/prog_guide/multi_proc_support.html
276 **DPDK stats plugin limitations:**
278 1. The DPDK primary process application should use the same version of DPDK
279 that collectd DPDK plugin is using;
281 2. L2 statistics are only supported;
283 3. The plugin has been tested on Intel NIC’s only.
285 **DPDK stats known issues:**
287 * DPDK port visibility
289 When network port controlled by Linux is bound to DPDK driver, the port
290 will not be available in the OS. It affects the SNMP write plugin as those
291 ports will not be present in standard IF-MIB. Thus addition work is
292 required to be done to support DPDK ports and statistics.
296 Repo: https://github.com/collectd/collectd
300 Dependencies: None, but assumes hugepages are configured.
302 To configure some hugepages:
306 sudo mkdir -p /mnt/huge
307 sudo mount -t hugetlbfs nodev /mnt/huge
308 sudo echo 14336 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
310 Building and installing collectd:
314 $ git clone https://github.com/collectd/collectd.git
317 $ ./configure --enable-syslog --enable-logfile --enable-hugepages --enable-debug
321 This will install collectd to /opt/collectd
322 The collectd configuration file can be found at /opt/collectd/etc
323 To configure the hugepages plugin you need to modify the configuration file to
334 ValuesPercentage false
337 For more information on the plugin parameters, please see:
338 https://github.com/collectd/collectd/blob/master/src/collectd.conf.pod
342 Repo: https://github.com/collectd/collectd
348 * PQoS/Intel RDT library https://github.com/01org/intel-cmt-cat.git
351 Building and installing PQoS/Intel RDT library:
355 $ git clone https://github.com/01org/intel-cmt-cat.git
358 $ make install PREFIX=/usr
360 You will need to insert the msr kernel module:
366 Building and installing collectd:
370 $ git clone https://github.com/collectd/collectd.git
373 $ ./configure --enable-syslog --enable-logfile --with-libpqos=/usr/ --enable-debug
377 This will install collectd to /opt/collectd
378 The collectd configuration file can be found at /opt/collectd/etc
379 To configure the RDT plugin you need to modify the configuration file to
384 <LoadPlugin intel_rdt>
391 For more information on the plugin parameters, please see:
392 https://github.com/collectd/collectd/blob/master/src/collectd.conf.pod
396 Repo: https://github.com/maryamtahhan/collectd
398 Branch: feat_ipmi_events, feat_ipmi_analog
400 Dependencies: OpenIPMI library (http://openipmi.sourceforge.net/)
402 The IPMI plugin is already implemented in the latest collectd and sensors
403 like temperature, voltage, fanspeed, current are already supported there.
404 The list of supported IPMI sensors has been extended and sensors like flow,
405 power are supported now. Also, a System Event Log (SEL) notification feature
408 * The feat_ipmi_events branch includes new SEL feature support in collectd
409 IPMI plugin. If this feature is enabled, the collectd IPMI plugin will
410 dispatch notifications about new events in System Event Log.
412 * The feat_ipmi_analog branch includes the support of extended IPMI sensors in
413 collectd IPMI plugin.
415 **Install dependencies**
417 On Ubuntu, the OpenIPMI library can be installed via apt package manager:
421 $ sudo apt-get install libopenipmi-dev
423 Anyway, it's recommended to use the latest version of the OpenIPMI library as
424 it includes fixes of known issues which aren't included in standard OpenIPMI
425 library package. The latest version of the library can be found at
426 https://sourceforge.net/p/openipmi/code/ci/master/tree/. Steps to install the
427 library from sources are described below.
429 Remove old version of OpenIPMI library:
433 $ sudo apt-get remove libopenipmi-dev
435 Download OpenIPMI library sources:
439 $ git clone https://git.code.sf.net/p/openipmi/code openipmi-code
442 Patch the OpenIPMI pkg-config file to provide correct compilation flags
443 for collectd IPMI plugin:
447 diff --git a/OpenIPMIpthread.pc.in b/OpenIPMIpthread.pc.in
448 index 59b52e5..fffa0d0 100644
449 --- a/OpenIPMIpthread.pc.in
450 +++ b/OpenIPMIpthread.pc.in
451 @@ -6,6 +6,6 @@ includedir=@includedir@
452 Name: OpenIPMIpthread
453 Description: Pthread OS handler for OpenIPMI
455 -Requires: OpenIPMI pthread
457 Libs: -L${libdir} -lOpenIPMIutils -lOpenIPMIpthread
458 -Cflags: -I${includedir}
459 +Cflags: -I${includedir} -pthread
461 Build and install OpenIPMI library:
465 $ autoreconf --install
466 $ ./configure --prefix=/usr
470 Enable IPMI support in the kernel:
474 $ sudo modprobe ipmi_devintf
475 $ sudo modprobe ipmi_si
477 **Note**: If HW supports IPMI, the ``/dev/ipmi0`` character device will be
480 Clone and install the collectd IPMI plugin:
484 $ git clone https://github.com/maryamtahhan/collectd
486 $ git checkout $BRANCH
488 $ ./configure --enable-syslog --enable-logfile --enable-debug
492 Where $BRANCH is feat_ipmi_events or feat_ipmi_analog.
494 This will install collectd to default folder ``/opt/collectd``. The collectd
495 configuration file (``collectd.conf``) can be found at ``/opt/collectd/etc``. To
496 configure the IPMI plugin you need to modify the file to include:
502 SELEnabled true # only feat_ipmi_events branch supports this
505 **Note**: By default, IPMI plugin will read all available analog sensor values,
506 dispatch the values to collectd and send SEL notifications.
508 For more information on the IPMI plugin parameters and SEL feature configuration,
510 https://github.com/maryamtahhan/collectd/blob/feat_ipmi_events/src/collectd.conf.pod
512 Extended analog sensors support doesn't require additional configuration. The usual
513 collectd IPMI documentation can be used:
515 - https://collectd.org/wiki/index.php/Plugin:IPMI
516 - https://collectd.org/documentation/manpages/collectd.conf.5.shtml#plugin_ipmi
520 - https://www.kernel.org/doc/Documentation/IPMI.txt
521 - http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-second-gen-interface-spec-v2-rev1-1.html
525 Repo: https://github.com/collectd/collectd
531 Start by installing mcelog. Note: The kernel has to have CONFIG_X86_MCE
532 enabled. For 32bit kernels you need at least a 2.6,30 kernel.
538 $ apt-get update && apt-get install mcelog
544 $ git clone git://git.kernel.org/pub/scm/utils/cpu/mce/mcelog.git
549 $ cp mcelog.service /etc/systemd/system/
550 $ systemctl enable mcelog.service
551 $ systemctl start mcelog.service
554 Verify you got a /dev/mcelog. You can verify the daemon is running completely
561 This should query the information in the running daemon. If it prints nothing
562 that is fine (no errors logged yet). More info @
563 http://www.mcelog.org/installation.html
565 Modify the mcelog configuration file "/etc/mcelog/mcelog.conf" to include or
570 socket-path = /var/run/mcelog-client
572 Clone and install the collectd mcelog plugin:
576 $ git clone https://github.com/maryamtahhan/collectd
578 $ git checkout feat_ras
580 $ ./configure --enable-syslog --enable-logfile --enable-debug
584 This will install collectd to /opt/collectd
585 The collectd configuration file can be found at /opt/collectd/etc
586 To configure the mcelog plugin you need to modify the configuration file to
595 McelogClientSocket "/var/run/mcelog-client"
598 For more information on the plugin parameters, please see:
599 https://github.com/maryamtahhan/collectd/blob/feat_ras/src/collectd.conf.pod
601 Simulating a Machine Check Exception can be done in one of 3 ways:
603 * Running $make test in the mcelog cloned directory - mcelog test suite
607 **mcelog test suite:**
609 It is always a good idea to test an error handling mechanism before it is
610 really needed. mcelog includes a test suite. The test suite relies on
611 mce-inject which needs to be installed and in $PATH.
613 You also need the mce-inject kernel module configured (with
614 CONFIG_X86_MCE_INJECT=y), compiled, installed and loaded:
618 $ modprobe mce-inject
620 Then you can run the mcelog test suite with
626 This will inject different classes of errors and check that the mcelog triggers
627 runs. There will be some kernel messages about page offlining attempts. The
628 test will also lose a few pages of memory in your system (not significant)
629 **Note this test will kill any running mcelog, which needs to be restarted
630 manually afterwards**.
633 A utility to inject corrected, uncorrected and fatal machine check exceptions
637 $ git clone https://git.kernel.org/pub/scm/utils/cpu/mce/mce-inject.git
640 $ modprobe mce-inject
642 Modify the test/corrected script to include the following:
647 STATUS 0xcc00008000010090
653 $ ./mce-inject < test/corrected
655 **Note: the uncorrected and fatal scripts under test will cause a platform reset.
656 Only the fatal script generates the memory errors**. In order to quickly
657 emulate uncorrected memory errors and avoid host reboot following test errors
658 from mce-test suite can be injected:
662 $ mce-inject mce-test/cases/coverage/soft-inj/recoverable_ucr/data/srao_mem_scrub
666 In addition an more in-depth test of the Linux kernel machine check facilities
667 can be done with the mce-test test suite. mce-test supports testing uncorrected
668 error handling, real error injection, handling of different soft offlining
669 cases, and other tests.
671 **Corrected memory error injection:**
673 To inject corrected memory errors:
675 * Remove sb_edac and edac_core kernel modules: rmmod sb_edac rmmod edac_core
676 * Insert einj module: modprobe einj param_extension=1
677 * Inject an error by specifying details (last command should be repeated at least two times):
681 $ APEI_IF=/sys/kernel/debug/apei/einj
682 $ echo 0x8 > $APEI_IF/error_type
683 $ echo 0x01f5591000 > $APEI_IF/param1
684 $ echo 0xfffffffffffff000 > $APEI_IF/param2
685 $ echo 1 > $APEI_IF/notrigger
686 $ echo 1 > $APEI_IF/error_inject
688 * Check the MCE statistic: mcelog --client. Check the mcelog log for injected error details: less /var/log/mcelog.
691 ^^^^^^^^^^^^^^^^^^^^^
692 OvS Plugins Repo: https://github.com/collectd/collectd
694 OvS Plugins Branch: master
696 OvS Events MIBs: The SNMP OVS interface link status is provided by standard
697 IF-MIB (http://www.net-snmp.org/docs/mibs/IF-MIB.txt)
699 Dependencies: Open vSwitch, Yet Another JSON Library (https://github.com/lloyd/yajl)
701 On Ubuntu, install the dependencies:
705 $ sudo apt-get install libyajl-dev openvswitch-switch
707 Start the Open vSwitch service:
711 $ sudo service openvswitch-switch start
713 configure the ovsdb-server manager:
717 $ sudo ovs-vsctl set-manager ptcp:6640
719 Clone and install the collectd ovs plugin:
725 $ git checkout master
727 $ ./configure --enable-syslog --enable-logfile --enable-debug
731 This will install collectd to /opt/collectd. The collectd configuration file
732 can be found at /opt/collectd/etc. To configure the OVS events plugin you
733 need to modify the configuration file to include:
737 <LoadPlugin ovs_events>
740 <Plugin "ovs_events">
742 Socket "/var/run/openvswitch/db.sock"
743 Interfaces "br0" "veth0"
744 SendNotification false
748 To configure the OVS stats plugin you need to modify the configuration file
753 <LoadPlugin ovs_stats>
759 Socket "/var/run/openvswitch/db.sock"
760 Bridges "br0" "br_ext"
763 For more information on the plugin parameters, please see:
764 https://github.com/collectd/collectd/blob/master/src/collectd.conf.pod
768 Repo: https://github.com/maryamtahhan/collectd/
772 Dependencies: NET-SNMP library
774 Start by installing net-snmp and dependencies.
780 $ apt-get install snmp snmp-mibs-downloader snmpd libsnmp-dev
781 $ systemctl start snmpd.service
785 Become root to install net-snmp dependencies
789 $ apt-get install libperl-dev
791 Clone and build net-snmp
795 $ git clone https://github.com/haad/net-snmp.git
797 $ ./configure --with-persistent-directory="/var/net-snmp" --with-systemd --enable-shared --prefix=/usr
806 Copy default configuration to persistent folder
810 $ cp EXAMPLE.conf /usr/share/snmp/snmpd.conf
812 Set library path and default MIB configuration
817 $ echo export LD_LIBRARY_PATH=/usr/lib >> .bashrc
818 $ net-snmp-config --default-mibdirs
819 $ net-snmp-config --snmpconfpath
821 Configure snmpd as a service
826 $ cp ./dist/snmpd.service /etc/systemd/system/
827 $ systemctl enable snmpd.service
828 $ systemctl start snmpd.service
830 Add the following line to snmpd.conf configuration file
831 "/usr/share/snmp/snmpd.conf" to make all OID tree visible for SNMP clients:
835 view systemonly included .1
837 To verify that SNMP is working you can get IF-MIB table using SNMP client
838 to view the list of Linux interfaces:
842 $ snmpwalk -v 2c -c public localhost IF-MIB::interfaces
844 Clone and install the collectd snmp_agent plugin:
848 $ git clone https://github.com/maryamtahhan/collectd
850 $ git checkout feat_snmp
852 $ ./configure --enable-syslog --enable-logfile --enable-debug --enable-snmp --with-libnetsnmp
856 This will install collectd to /opt/collectd
857 The collectd configuration file can be found at /opt/collectd/etc
858 **SNMP Agent plugin is a generic plugin and cannot work without configuration**.
859 To configure the snmp_agent plugin you need to modify the configuration file to
860 include OIDs mapped to collectd types. The following example maps scalar
861 memAvailReal OID to value represented as free memory type of memory plugin:
865 LoadPlugin snmp_agent
866 <Plugin "snmp_agent">
867 <Data "memAvailReal">
871 OIDs "1.3.6.1.4.1.2021.4.6.0"
875 For more information on the plugin parameters, please see:
876 https://github.com/maryamtahhan/collectd/blob/feat_snmp/src/collectd.conf.pod
878 For more details on AgentX subagent, please see:
879 http://www.net-snmp.org/tutorial/tutorial-5/toolkit/demon/
883 Repo: https://github.com/maryamtahhan/collectd
885 Branch: feat_libvirt_upstream
887 Dependencies: libvirt (https://libvirt.org/), libxml2
889 On Ubuntu, install the dependencies:
893 $ sudo apt-get install libxml2-dev
897 libvirt version in package manager might be quite old and offer only limited
898 functionality. Hence, building and installing libvirt from sources is recommended.
899 Detailed instructions can bet found at:
900 https://libvirt.org/compiling.html
902 Certain metrics provided by the plugin have a requirement on a minimal version of
903 the libvirt API. *File system information* statistics require a *Guest Agent (GA)*
904 to be installed and configured in a VM. User must make sure that installed GA
905 version supports retrieving file system information. Number of *Performance monitoring events*
906 metrics depends on running libvirt daemon version.
908 .. note:: Please keep in mind that RDT metrics (part of *Performance monitoring
909 events*) have to be supported by hardware. For more details on hardware support,
911 https://github.com/01org/intel-cmt-cat
913 Additionally perf metrics **cannot** be collected if *Intel RDT* plugin is enabled.
915 libvirt version can be checked with following commands:
922 .. table:: Extended statistics requirements
924 +-------------------------------+--------------------------+-------------+
925 | Statistic | Min. libvirt API version | Requires GA |
926 +===============================+==========================+=============+
927 | Domain reason | 0.9.2 | No |
928 +-------------------------------+--------------------------+-------------+
929 | Disk errors | 0.9.10 | No |
930 +-------------------------------+--------------------------+-------------+
931 | Job statistics | 1.2.9 | No |
932 +-------------------------------+--------------------------+-------------+
933 | File system information | 1.2.11 | Yes |
934 +-------------------------------+--------------------------+-------------+
935 | Performance monitoring events | 1.3.3 | No |
936 +-------------------------------+--------------------------+-------------+
938 Start libvirt daemon:
942 $ systemctl start libvirtd
944 Create domain (VM) XML configuration file. For more information on domain XML
945 format and examples, please see:
946 https://libvirt.org/formatdomain.html
948 .. note:: Installing additional hypervisor dependencies might be required before
949 deploying virtual machine.
951 Create domain, based on created XML file:
955 $ virsh define DOMAIN_CFG_FILE.xml
961 $ virsh start DOMAIN_NAME
963 Check if domain is running:
969 Check list of available *Performance monitoring events* and their settings:
973 $ virsh perf DOMAIN_NAME
975 Enable or disable *Performance monitoring events* for domain:
979 $ virsh perf DOMAIN_NAME [--enable | --disable] EVENT_NAME --live
981 Clone and install the collectd virt plugin:
987 $ git checkout $BRANCH
989 $ ./configure --enable-syslog --enable-logfile --enable-debug
993 Where ``$REPO`` and ``$BRANCH`` are equal to information provided above.
995 This will install collectd to ``/opt/collectd``. The collectd configuration file
996 ``collectd.conf`` can be found at ``/opt/collectd/etc``. To load the virt plugin
997 user needs to modify the configuration file to include:
1003 Additionally, user can specify plugin configuration parameters in this file,
1004 such as connection URI, domain name and much more. By default extended virt plugin
1005 statistics are disabled. They can be enabled with ``ExtraStats`` option.
1011 ExtraStats "cpu_util disk disk_err domain_state fs_info job_stats_background pcpu perf vcpupin"
1014 For more information on the plugin parameters, please see:
1015 https://github.com/maryamtahhan/collectd/blob/feat_libvirt_upstream/src/collectd.conf.pod
1017 Installing collectd as a service
1018 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1019 **NOTE**: In an OPNFV installation, collectd is installed and configured as a
1022 Collectd service scripts are available in the collectd/contrib directory.
1023 To install collectd as a service:
1027 $ sudo cp contrib/systemd.collectd.service /etc/systemd/system/
1028 $ cd /etc/systemd/system/
1029 $ sudo mv systemd.collectd.service collectd.service
1030 $ sudo chmod +x collectd.service
1032 Modify collectd.service
1037 ExecStart=/opt/collectd/sbin/collectd
1038 EnvironmentFile=-/opt/collectd/etc/
1039 EnvironmentFile=-/opt/collectd/etc/
1040 CapabilityBoundingSet=CAP_SETUID CAP_SETGID
1046 $ sudo systemctl daemon-reload
1047 $ sudo systemctl start collectd.service
1048 $ sudo systemctl status collectd.service should show success
1050 Additional useful plugins
1051 ^^^^^^^^^^^^^^^^^^^^^^^^^^
1053 * **Exec Plugin** : Can be used to show you when notifications are being
1054 generated by calling a bash script that dumps notifications to file. (handy
1055 for debug). Modify /opt/collectd/etc/collectd.conf:
1061 # Exec "user:group" "/path/to/exec"
1062 NotificationExec "user" "<path to barometer>/barometer/src/collectd/collectd_sample_configs/write_notification.sh"
1065 write_notification.sh (just writes the notification passed from exec through
1066 STDIN to a file (/tmp/notifications)):
1071 rm -f /tmp/notifications
1074 echo $x$y >> /tmp/notifications
1077 output to /tmp/notifications should look like:
1085 PluginInstance:br-ex
1087 TypeInstance:link_status
1088 uuid:f2aafeec-fa98-4e76-aec5-18ae9fc74589
1090 linkstate of "br-ex" interface has been changed to "DOWN"
1092 * **logfile plugin**: Can be used to log collectd activity. Modify
1093 /opt/collectd/etc/collectd.conf to include:
1100 File "/var/log/collectd.log"
1106 Monitoring Interfaces and Openstack Support
1107 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1108 .. Figure:: monitoring_interfaces.png
1110 Monitoring Interfaces and Openstack Support
1112 The figure above shows the DPDK L2 forwarding application running on a compute
1113 node, sending and receiving traffic. collectd is also running on this compute
1114 node retrieving the stats periodically from DPDK through the dpdkstat plugin
1115 and publishing the retrieved stats to Ceilometer through the ceilometer plugin.
1117 To see this demo in action please checkout: `Barometer OPNFV Summit demo`_
1121 .. [1] https://collectd.org/wiki/index.php/Naming_schema
1122 .. [2] https://github.com/collectd/collectd/blob/master/src/daemon/plugin.h
1123 .. [3] https://collectd.org/wiki/index.php/Value_list_t
1124 .. [4] https://collectd.org/wiki/index.php/Data_set
1125 .. [5] https://collectd.org/documentation/manpages/types.db.5.shtml
1126 .. [6] https://collectd.org/wiki/index.php/Data_source
1127 .. [7] https://collectd.org/wiki/index.php/Meta_Data_Interface
1129 .. _Barometer OPNFV Summit demo: https://prezi.com/kjv6o8ixs6se/software-fastpath-service-quality-metrics-demo/
1130 .. _ceilometer plugin: https://github.com/openstack/collectd-ceilometer-plugin/tree/stable/mitaka