X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=src%2Fcollectd.conf.pod;h=2566aa192804a27c9a09d94599815f7e49fb583a;hb=c99e3a4d169ada9299c73e20662d17debdc32e1f;hp=95c1b38778378f9fdf43c25656fca38bf26cf47d;hpb=08e419e462e8373538a7aef768bae0b2478e0e89;p=collectd.git diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index 95c1b387..2566aa19 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -2408,7 +2408,6 @@ B Coremask "0x1" MemoryChannels "4" - ProcessType "secondary" FilePrefix "rte" @@ -2431,7 +2430,7 @@ B =head3 The EAL block -=over 5 +=over 4 =item B I @@ -2439,10 +2438,6 @@ B Number of memory channels per processor socket. -=item B I - -The type of DPDK process instance. - =item B I The prefix text used for hugepage filenames. The filename will be set to @@ -2457,7 +2452,7 @@ single argument which specifies the name of the event. =head4 Link Status event -=over 5 +=over 4 =item B I @@ -2490,7 +2485,7 @@ value is false. =head4 Keep Alive event -=over 5 +=over 4 =item B I @@ -2526,7 +2521,6 @@ B Coremask "0x4" MemoryChannels "4" - ProcessType "secondary" FilePrefix "rte" SocketMemory "1024" @@ -2540,7 +2534,7 @@ B =head3 The EAL block -=over 5 +=over 4 =item B I @@ -2551,10 +2545,6 @@ core numbering can change between platforms and should be determined beforehand. A string containing a number of memory channels per processor socket. -=item B I - -A string containing the type of DPDK process instance. - =item B I The prefix text used for hugepage filenames. The filename will be set to @@ -2570,6 +2560,7 @@ sockets in MB. This is an optional value. =over 3 =item B I + A string containing the name of the shared memory object that should be used to share stats from the DPDK secondary process to the collectd dpdkstat plugin. Defaults to dpdk_collectd_stats if no other value is configured. @@ -3090,17 +3081,18 @@ Linux perf interface. All events are reported on a per core basis. B - HWCacheEvents true - KernelPMUEvents true - SWEvents true - HWSpecificEvents "L2_RQSTS.CODE_RD_HIT,L2_RQSTS.CODE_RD_MISS" + ReportHardwareCacheEvents true + ReportKernelPMUEvents true + ReportSoftwareEvents true + EventList "/var/cache/pmu/GenuineIntel-6-2D-core.json" + HardwareEvents "L2_RQSTS.CODE_RD_HIT,L2_RQSTS.CODE_RD_MISS" "L2_RQSTS.ALL_CODE_RD" B =over 4 -=item B B|B +=item B B|B Enable or disable measuring of hardware CPU cache events: - L1-dcache-loads @@ -3130,7 +3122,7 @@ Enable or disable measuring of hardware CPU cache events: - branch-loads - branch-load-misses -=item B B|B +=item B B|B Enable or disable measuring of the following events: - cpu-cycles @@ -3141,7 +3133,7 @@ Enable or disable measuring of the following events: - branch-misses - bus-cycles -=item B B|B +=item B B|B Enable or disable measuring of software events provided by kernel: - cpu-clock @@ -3154,11 +3146,16 @@ Enable or disable measuring of software events provided by kernel: - alignment-faults - emulation-faults -=item B I +=item B I + +JSON performance counter event list file name. To be able to monitor all Intel +CPU specific events JSON event list file should be downloaded. Use the pmu-tools +event_download.py script to download event list for current CPU. + +=item B I -This field is a list of comma separated event names. To be able to monitor all -Intel CPU specific events JSON event list file should be downloaded. -Use the pmu-tools event_download.py script for this. +This field is a list of event names or groups of comma separated event names. +This option requires B option to be configured. =back @@ -3233,7 +3230,7 @@ See F for details. =item B I|I -If no configuration if given, the B-plugin will collect data from +If no configuration is given, the B-plugin will collect data from all interfaces. This may not be practical, especially for loopback- and similar interfaces. Thus, you can use the B-option to pick the interfaces you're interested in. Sometimes, however, it's easier/preferred @@ -5380,6 +5377,11 @@ generate links like the one described above for ALL certs in a given folder. Example usage: C +=item B I + +The B option sets the connect timeout, in milliseconds. +By default, the configured B is used to set the timeout. + =back =head2 Plugin C @@ -5945,10 +5947,10 @@ multiple hosts. =item B I Sets the interval in which to send ICMP echo packets to the configured hosts. -This is B the interval in which statistics are queries from the plugin but -the interval in which the hosts are "pinged". Therefore, the setting here -should be smaller than or equal to the global B setting. Fractional -times, such as "1.24" are allowed. +This is B the interval in which metrics are read from the plugin but the +interval in which the hosts are "pinged". Therefore, the setting here should be +smaller than or equal to the global B setting. Fractional times, such +as "1.24" are allowed. Default: B<1.0> @@ -7041,14 +7043,20 @@ one (exclusive). When the C plugin uses a cache (by setting B, see below) it writes all values for a certain RRD-file if the oldest value is older than -(or equal to) the number of seconds specified. If some RRD-file is not updated +(or equal to) the number of seconds specified by B. +That check happens on new values arriwal. If some RRD-file is not updated anymore for some reason (the computer was shut down, the network is broken, -etc.) some values may still be in the cache. If B is set, then the -entire cache is searched for entries older than B seconds and -written to disk every I seconds. Since this is kind of expensive and -does nothing under normal circumstances, this value should not be too small. -900 seconds might be a good value, though setting this to 7200 seconds doesn't -normally do much harm either. +etc.) some values may still be in the cache. If B is set, then +every I seconds the entire cache is searched for entries older than +B + B seconds. The entries found are written to +disk. Since scanning the entire cache is kind of expensive and does nothing +under normal circumstances, this value should not be too small. 900 seconds +might be a good value, though setting this to 7200 seconds doesn't normally +do much harm either. + +Defaults to 10x B. +B must be larger than or equal to B, otherwise the +above default is used. =item B I @@ -7262,6 +7270,122 @@ Since the configuration of the C is a little more complicated than other plugins, its documentation has been moved to an own manpage, L. Please see there for details. +=head2 Plugin C + +The I plugin is an AgentX subagent that receives and handles queries +from SNMP master agent and returns the data collected by read plugins. +The I plugin handles requests only for OIDs specified in +configuration file. To handle SNMP queries the plugin gets data from collectd +and translates requested values from collectd's internal format to SNMP format. +This plugin is a generic plugin and cannot work without configuration. +For more details on AgentX subagent see + + +B + + + + Plugin "memory" + #PluginInstance "some" + Type "memory" + TypeInstance "free" + OIDs "1.3.6.1.4.1.2021.4.6.0" + + + IndexOID "IF-MIB::ifIndex" + SizeOID "IF-MIB::ifNumber" + + Instance true + Plugin "interface" + OIDs "IF-MIB::ifDescr" + + + Plugin "interface" + Type "if_octets" + TypeInstance "" + OIDs "IF-MIB::ifInOctets" "IF-MIB::ifOutOctets" + +
+ + +There are two types of blocks that can be contained in the +CPluginE snmp_agentE> block: B and B: + +=head3 The B block + +The B block defines a list OIDs that are to be handled. This block can +define scalar or table OIDs. If B block is defined inside of B
+block it reperesents table OIDs. +The following options can be set: + +=over 4 + +=item B I + +When B is set to B, the value for requested OID is copied from +plugin instance field of corresponding collectd value. If B block defines +scalar data type B has no effect and can be omitted. + +=item B I + +Read plugin name whose collected data will be mapped to specified OIDs. + +=item B I + +Read plugin instance whose collected data will be mapped to specified OIDs. +The field is optional and by default there is no plugin instance check. +Allowed only if B block defines scalar data type. + +=item B I + +Collectd's type that is to be used for specified OID, e.Eg. "if_octets" +for example. The types are read from the B (see L). + +=item B I + +Collectd's type-instance that is to be used for specified OID. + +=item B I [I ...] + +Configures the OIDs to be handled by I plugin. Values for these OIDs +are taken from collectd data type specified by B, B, +B, B fields of this B block. Number of the OIDs +configured should correspond to number of values in specified B. +For example two OIDs "IF-MIB::ifInOctets" "IF-MIB::ifOutOctets" can be mapped to +"rx" and "tx" values of "if_octets" type. + +=item B I + +The values taken from collectd are multiplied by I. The field is optional +and the default is B<1.0>. + +=item B I + +I is added to values from collectd after they have been multiplied by +B value. The field is optional and the default value is B<0.0>. + +=back + +=head3 The B
block + +The B
block defines a collection of B blocks that belong to one +snmp table. In addition to multiple B blocks the following options can be +set: + +=over 4 + +=item B I + +OID that is handled by the plugin and is mapped to numerical index value that is +generated by the plugin for each table record. + +=item B I + +OID that is handled by the plugin. Returned value is the number of records in +the table. The field is optional. + +=back + =head2 Plugin C The I listens to a UDP socket, reads "events" in the statsd