X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=src%2Fcollectd.conf.pod;h=f7531cd8805ae575f140c82eabd6ecfd3fb8d54e;hb=6f4e737d0e88e41e94d422f54509f12cac365be6;hp=b8cc36ea603dedee0962fe27094a289398d6fc4d;hpb=235e731905fc81a379ba7ba0717dd96a69ac2737;p=collectd.git diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index b8cc36ea..f7531cd8 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -1644,330 +1644,453 @@ or SQL threads are not running. =back - Plugin "netapp" - The netapp plugin can collect various performance and capacity - informations from a netapp filer using the NetApp API. +=head2 Plugin C + +The netapp plugin can collect various performance and capacity informations +from a NetApp filer using the NetApp API. + +To collect these data collectd will log in to the NetApp via HTTP(S) and HTTP +basic authentication. + +B Create a special collectd user with just +the minimum of capabilities needed. The user only needs the "login-http-admin" +capability as well as a few more depending on which data will be collected. +Required capabilities are documented below. + +=head3 Synopsis + + + + Protocol "https" + Address "10.0.0.1" + Port 443 + User "username" + Password "aef4Aebe" + Interval 30 + + + Interval 30 + GetNameCache true + GetDirCache true + GetBufferCache true + GetInodeCache true + + + + Interval 30 + GetBusy true + + + + Interval 30 + GetIO "volume0" + IgnoreSelectedIO false + GetOps "volume0" + IgnoreSelectedOps false + GetLatency "volume0" + IgnoreSelectedLatency false + + + + Interval 30 + GetCapacity "vol0" + GetCapacity "vol1" + IgnoreSelectedCapacity false + GetSnapshot "vol1" + GetSnapshot "vol3" + IgnoreSelectedSnapshot false + + + + Interval 30 + GetCPULoad true + GetInterfaces true + GetDiskOps true + GetDiskIO true + + + + +The netapp plugin accepts the following configuration options: + +=over 4 + +=item B I + +A host block defines one NetApp filer. It will appear in collectd with the name +you specify here which does not have to be its real name nor its hostname. + +=item B B|B + +The protocol collectd will use to query this host. + +Optional + +Type: string + +Default: https + +Valid options: http, https + +=item B
I
+ +The hostname or IP address of the host. + +Optional + +Type: string + +Default: The "host" block's name. + +=item B I + +The TCP port to connect to on the host. + +Optional + +Type: integer + +Default: 80 for protocol "http", 443 for protocol "https" + +=item B I + +=item B I + +The username and password to use to login to the NetApp. + +Mandatory + +Type: string + +=item B I + +B + +=back + +The following options decide what kind of data will be collected. You can +either use them as a block and fine tune various parameters inside this block, +use them as a single statement to just accept all default values, or omit it to +not collect any data. + +The following options are valid inside all blocks: + +=over 4 + +=item B I + +Collect the respective statistics every I seconds. Defaults to the +host specific setting. + +=back + +=head3 The System block + +This will collect various performance data about the whole system. + +B To get this data the collectd user needs the +"api-perf-object-get-instances" capability. + +=over 4 + +=item B I + +Collect disk statistics every I seconds. + +=item B B|B + +If you set this option to true the current CPU usage will be read. This will be +the average usage between all CPUs in your NetApp without any information about +individual CPUs. + +B These are the same values that the NetApp CLI command "sysstat" +returns in the "CPU" field. + +Optional + +Type: boolean + +Default: true + +Result: Two value lists of type "cpu", and type instances "idle" and "system". + +=item B B|B - To collect these data collectd will log in to the netapp via http(s) - and basic http auth. +If you set this option to true the current traffic of the network interfaces +will be read. This will be the total traffic over all interfaces of your NetApp +without any information about individual interfaces. - !Do not use a regular user for this! Create a special collectd user - with just the minimum of capabilities needed. The user only needs - the "login-http-admin" capability as well as a few more depending on - which data will be collected. +B This is the same values that the NetApp CLI command "sysstat" returns +in the "Net kB/s" field. - Synopsis: +B - - - Protocol https - Address 10.0.0.1 - Port 443 - Login "username" "password" - Interval 30 - - - - - - - - - - - - +Optional - The netapp plugin accepts the following configuration options: +Type: boolean - Host Name - A host block defines one netapp filer. It will appear in collectd - with the name you specify here which does not have to be its real - name nor its hostname. +Default: true - Protocol - The protocol collectd will use to query this host. +Result: One value list of type "if_octects". - Optional - Type: string - Default: https - Valid options: http, https +=item B B|B - Address - The hostname or IP address of the host. +If you set this option to true the current IO throughput will be read. This +will be the total IO of your NetApp without any information about individual +disks, volumes or aggregates. - Optional - Type: string - Default: The hostblock's name. +B This is the same values that the NetApp CLI command "sysstat" returns +in the "DiskEkB/s" field. - Port - The TCP port to connect to on the host. +Optional - Optional - Type: integer - Default: 80 for protocol http, 443 for protocol https +Type: boolean - Login - The username and password to use to login to the netapp. +Default: true - Mandatory - Type: 2 strings +Result: One value list of type "disk_octets". - Interval - TODO +=item B B|B +If you set this option to true the current number of HTTP, NFS, CIFS, FCP, +iSCSI, etc. operations will be read. This will be the total number of +operations on your NetApp without any information about individual volumes or +aggregates. - The following options decide what kind of data will be collected. You - can either use them as a block and finetune various parameters inside - this block, use them as a single statement to just accept all default - values, or obmit it to not collect any data. +B These are the same values that the NetApp CLI command "sysstat" +returns in the "NFS", "CIFS", "HTTP", "FCP" and "iSCSI" fields. - The following options are valid inside all blocks: +Optional - Multiplier - The host specific interval between data collections is multiplied - by this value for collecting these data. +Type: boolean - Optional - Type: integer - Default: 1 +Default: true +Result: A variable number of value lists of type "disk_ops_complex". Each type +of operation will result in one value list with the name of the operation as +type instance. - The GetSystemPerfData Block: +=back + +=head3 The WAFL block + +This will collect various performance data about the WAFL file system. At the +moment this just means cache performance. - This will collect various performance data about the whole system. +B To get this data the collectd user needs the +"api-perf-object-get-instances" capability. - Note: To get this data the collectd user needs the - "api-perf-object-get-instances" capability. +B The interface to get these values is classified as "Diagnostics" by +NetApp. This means that it is not guaranteed to be stable even between minor +releases. - GetCPULoad - If you set this option to true the currect CPU usage will be - read. This will be the average usage between all CPUs in your - netapp without any information about individual CPUs. +=over 4 - Note: These are the same values that the netapp CLI command - "sysstat" returns in the "CPU" field. +=item B I - Optional - Type: boolean - Default: true +Collect disk statistics every I seconds. - Result: Two data sources of type "cpu", and type instances - "idle" and "system". +=item B B|B - GetInterfaces - If you set this option to true the currect traffic of the - network interfaces will be read. This will be the total traffic - over all interfaces of your netapp without any information - about individual interfaces. +Optional - Note: This is the same values that the netapp CLI command - "sysstat" returns in the "Net kB/s" field. - Or is it? +Type: boolean - Optional - Type: boolean - Default: true +Default: true - Result: One data source of type "if_octects". +Result: One value list of type "cache_ratio" and type instance +"name_cache_hit". - GetDiskIO - If you set this option to true the currect IO throughput will be - read. This will be the total IO of your netapp without any - information about individual disks, volumes or aggregates. +=item B B|B - Note: This is the same values that the netapp CLI command - "sysstat" returns in the "Disk kB/s" field. +Optional - Optional - Type: boolean - Default: true +Type: boolean - Result: One data source of type "disk_octets". +Default: true - GetDiskOps - If you set this option to true the currect number of http, nfs, - cifs, fcp, iscsi, ... operations will be read. This will be the - total number of operations on your netapp without any information - about individual volumes or aggregates. +Result: One value list of type "cache_ratio" and type instance "find_dir_hit". +=item B B|B - Note: These are the same values that the netapp CLI command - "sysstat" returns in the "NFS", "CIFS", "HTTP", "FCP" and - "iSCSI" fields. +Optional - Optional - Type: boolean - Default: true +Type: boolean - Result: A variable number of data sources of type - "disk_ops_complex". Each type of operation will result in - one data source with the name of the operation as type - instance. +Default: true +Result: One value list of type "cache_ratio" and type instance +"inode_cache_hit". - The GetWaflPerfData block: +=item B B|B - This will collect various performance data about the WAFL file - system. At the moment this just means cache performance. +B This is the same value that the NetApp CLI command "sysstat" returns +in the "Cache hit" field. - Note: To get this data the collectd user needs the - "api-perf-object-get-instances" capability. +Optional - Note: The interface to get these values is classified as - "Diagnostics" by netapp. This means that it is not guaranteed - to be stable even between minor releases. +Type: boolean - GetNameCache - Optional - Type: boolean - Default: true +Default: true - Result: One data source of type "cache_ratio" and type instance - "name_cache_hit". +Result: One value list of type "cache_ratio" and type instance "buf_hash_hit". - GetDirCache - Optional - Type: boolean - Default: true +=back - Result: One data source of type "cache_ratio" and type instance - "find_dir_hit". +=head3 The Disks block - GetInodeCache - Optional - Type: boolean - Default: true +This will collect performance data about the individual disks in the NetApp. - Result: One data source of type "cache_ratio" and type instance - "inode_cache_hit". +B To get this data the collectd user needs the +"api-perf-object-get-instances" capability. - GetBufCache - Note: This is the same value that the netapp CLI command - "sysstat" returns in the "Cache hit" field. +=over 4 - Optional - Type: boolean - Default: true +=item B I - Result: One data source of type "cache_ratio" and type instance - "buf_hash_hit". +Collect disk statistics every I seconds. +=item B B|B - The GetDiskPerfData block: +If you set this option to true the busy time of all disks will be calculated +and the value of the busiest disk in the system will be written. - This will collect performance data about the individual disks in the - netapp. +B This is the same values that the NetApp CLI command "sysstat" returns +in the "Disk util" field. Probably. - Note: To get this data the collectd user needs the - "api-perf-object-get-instances" capability. +Optional - GetBusy - If you set this option to true the busy time of all disks will be - calculated and the value of the busiest disk in the system will - be written. +Type: boolean - Note: This is the same values that the netapp CLI command - "sysstat" returns in the "Disk util" field. Probably. +Default: true - Optional - Type: boolean - Default: true +Result: One value list of type "percent" and type instance "disk_busy". - Result: One data source of type "percent" and type instance - "disk_busy". +=back +=head3 The VolumePerf block - The GetVolumePerfData block: +This will collect various performance data about the individual volumes. - This will collect various performance data about the individual - volumes. +You can select which data to collect about which volume using the following +options. They follow the standard ignorelist semantic. - All of these options take a list of volumes as parameters. In this - case "volume" meas just the name of the volume, without the "/vol/" - prefix or anything like that. - The special values "-" and "+" are supported. "-" means "don't - collect values for any volumes". "+" means "collect values for all - volumes, even volumes that are created after collectd was started." - Additionally you can prefix a volume name with a "-" sign to exclude - this one volume. Eg '"+" "-vol0"' collectes values for all volumes - except vol0. - The order of the parameters is important. '"-vol0" "+"' doesn't make - sense because the "+" overrides the earlier "-vol0". +B To get this data the collectd user needs the +I capability. - Note: To get this data the collectd user needs the - "api-perf-object-get-instances" capability. +=over 4 - GetIO - The currect IO throughput will be read for every volume specified - here. +=item B I - Optional - Type: list of strings - Default: "+" +Collect volume performance data every I seconds. - Result: Data sources of type "disk_octets" and the name of the - volume as plugin_instance. +=item B I - GetOps - The currect number of operation will be read for every volume - specified here. +=item B I - Optional - Type: list of strings - Default: "+" +=item B I - Result: Data sources of type "disk_ops" and the name of the - volume as plugin_instance. +Select the given volume for IO, operations or latency statistics collection. +The argument is the name of the volume without the C prefix. - GetLatency - The currect latency for volume access in microseconds will be - read for every volume specified here. +Since the standard ignorelist functionality is used here, you can use a string +starting and ending with a slash to specify regular expression matching: To +match the volumes "vol0", "vol2" and "vol7", you can use this regular +expression: - Optional - Type: list of strings - Default: "+" + GetIO "/^vol[027]$/" - Result: Data sources of type "disk_latency" and the name of the - volume as plugin_instance. +If no regular expression is specified, an exact match is required. Both, +regular and exact matching are case sensitive. +If no volume was specified at all for either of the three options, that data +will be collected for all available volumes. - The GetVolumeData block: +=item B B|B - This will collect capacity data about the individual volumes. +=item B B|B - All of these options take a list of volumes as parameters, just like - GetVolumePerfData options. +=item B B|B - Note: To get this data the collectd user needs the - "api-volume-list-info" capability. +When set to B, the volumes selected for IO, operations or latency +statistics collection will be ignored and the data will be collected for all +other volumes. - GetDiskUtil - The current capacity of the volume will be collected. This will - result in two to four data sources, depending on the - configuration of the volume. All data sources are of type - "df_complex" with the name of the volume as plugin_instance. +When set to B, data will only be collected for the specified volumes and +all other volumes will be ignored. - There will be type_instances "used" and "free" for the number - of used and available bytes on the volume. - If the volume has some space reserved for snapshots, a - type_instance "snap_reserved" will be available. - If the volume has SIS enabled, a type_instance "sis_saved" will - be available. This is the number of bytes saved by the SIS - feature. +If no volumes have been specified with the above B options, all volumes +will be collected regardless of the B option. - Note: The current NetApp API has a bug that results in this value - being reported as a 32 bit number. This plugin tries to - guess the correct number which works most of the time. - If you see strange values here, bug NetApp support to fix - this. +Defaults to B - Optional - Type: list of strings - Default: "+" +=back - GetSnapData - TODO +=head3 The VolumeUsage block + +This will collect capacity data about the individual volumes. + +B To get this data the collectd user needs the I +capability. + +=over 4 + +=item B I + +Collect volume usage statistics every I seconds. + +=item B I + +The current capacity of the volume will be collected. This will result in two +to four value lists, depending on the configuration of the volume. All data +sources are of type "df_complex" with the name of the volume as +plugin_instance. + +There will be type_instances "used" and "free" for the number of used and +available bytes on the volume. If the volume has some space reserved for +snapshots, a type_instance "snap_reserved" will be available. If the volume +has SIS enabled, a type_instance "sis_saved" will be available. This is the +number of bytes saved by the SIS feature. + +B The current NetApp API has a bug that results in this value being +reported as a 32Ebit number. This plugin tries to guess the correct +number which works most of the time. If you see strange values here, bug +NetApp support to fix this. + +Repeat this option to specify multiple volumes. + +=item B B|B + +Specify whether to collect only the volumes selected by the B +option or to ignore those volumes. B defaults to +B. However, if no B option is specified at all, all +capacities will be selected anyway. + +=item B I + +Select volumes from which to collect snapshot information. + +Usually, the space used for snapshots is included in the space reported as +"used". If snapshot information is collected as well, the space used for +snapshots is subtracted from the used space. + +To make things even more interesting, it is possible to reserve space to be +used for snapshots. If the space required for snapshots is less than that +reserved space, there is "reserved free" and "reserved used" space in addition +to "free" and "used". If the space required for snapshots exceeds the reserved +space, that part allocated in the normal space is subtracted from the "used" +space again. + +Repeat this option to specify multiple volumes. + +=item B + +Specify whether to collect only the volumes selected by the B +option or to ignore those volumes. B defaults to +B. However, if no B option is specified at all, all +capacities will be selected anyway. + +=back =head2 Plugin C