Zabbix Documentation 2.2

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:discovery:low_level_discovery

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:discovery:low_level_discovery [2018/10/30 06:16]
martins-v merging similar information and linking to it from the overview
manual:discovery:low_level_discovery [2019/03/06 12:10] (current)
martins-v formatting change
Line 49: Line 49:
 |//​Type// ​ |The type of check to perform discovery; should be //Zabbix agent// or //Zabbix agent (active)// for file system discovery. ​ | |//​Type// ​ |The type of check to perform discovery; should be //Zabbix agent// or //Zabbix agent (active)// for file system discovery. ​ |
 |//​Key// ​ |An item with "​vfs.fs.discovery"​ key is built into the Zabbix agent on many platforms (see [[manual:​appendix:​items:​supported_by_platform|supported item key list]] for details), and will return a JSON with the list of file systems present on the computer and their types. ​ | |//​Key// ​ |An item with "​vfs.fs.discovery"​ key is built into the Zabbix agent on many platforms (see [[manual:​appendix:​items:​supported_by_platform|supported item key list]] for details), and will return a JSON with the list of file systems present on the computer and their types. ​ |
-|//Update interval (in sec)// ​ |This field specifies how often Zabbix performs discovery. In the beginning, when you are just setting up file system discovery, you might wish to set it to a small interval, but once you know it works you can set it to 30 minutes or more, because file systems usually do not change very often.\\ //Note//: If set to '0', the item will not be polled. However, if a flexible interval also exists with a non-zero value, the item will be polled during the flexible interval duration. ​ | +|//Update interval (in sec)// ​ |This field specifies how often Zabbix performs discovery. In the beginning, when you are just setting up file system discovery, you might wish to set it to a small interval, but once you know it works you can set it to 30 minutes or more, because file systems usually do not change very often.\\ //Note//: If set to %%"%%0%%"%%, the item will not be polled. However, if a flexible interval also exists with a non-zero value, the item will be polled during the flexible interval duration. ​ | 
-|//Flexible intervals// ​ |You can create exceptions to //Update interval//. For example:\\ Interval: **0**, Period: **6-7,​00:​00-24:​00** - will disable the polling at the weekend. Otherwise default update interval will be used.\\ Up to seven flexible intervals can be defined.\\ If multiple flexible intervals overlap, the smallest //​Interval//​ value is used for the overlapping period.\\ See [[manual:​appendix:​time_period|Time period specification]] page for description of the //Period// format.\\ //Note//: If set to '0', the item will not be polled during the flexible interval duration and will resume polling according to the //Update interval// once the flexible interval period is over.  | +|//Flexible intervals// ​ |You can create exceptions to //Update interval//. For example:\\ Interval: **0**, Period: **6-7,​00:​00-24:​00** - will disable the polling at the weekend. Otherwise default update interval will be used.\\ Up to seven flexible intervals can be defined.\\ If multiple flexible intervals overlap, the smallest //​Interval//​ value is used for the overlapping period.\\ See [[manual:​appendix:​time_period|Time period specification]] page for description of the //Period// format.\\ //Note//: If set to %%"%%0%%"%%, the item will not be polled during the flexible interval duration and will resume polling according to the //Update interval// once the flexible interval period is over.  | 
-|//Keep lost resources period (in days)// ​ |This field allows you to specify for how many days the discovered entity will be retained (won't be deleted) once its discovery status becomes "Not discovered anymore"​ (max 3650 days). \\ //Note:// If set to "​0",​ entities will be deleted immediately. Using "​0"​ is not recommended,​ since just wrongly editing the filter may end up in the entity being deleted with all the historical data.   |+|//Keep lost resources period (in days)// ​ |This field allows you to specify for how many days the discovered entity will be retained (won't be deleted) once its discovery status becomes "Not discovered anymore"​ (max 3650 days). \\ //Note:// If set to %%"%%0%%"%%, entities will be deleted immediately. Using %%"%%0%%"%% is not recommended,​ since just wrongly editing the filter may end up in the entity being deleted with all the historical data.   |
 |//​Filter// ​ |The filter can be used to only generate real items, triggers, and graphs for certain file systems. It expects [[manual:​regular_expressions|POSIX Extended Regular Expression]]. For instance, if you are only interested in C:, D:, and E: file systems, you could put {#FSNAME} into "​Macro"​ and <​nowiki>"​^C|^D|^E"</​nowiki>​ regular expression into "​Regexp"​ text fields. Filtering is also possible by file system types using {#FSTYPE} macro (e. g. <​nowiki>"​^ext|^reiserfs"</​nowiki>​).\\ You can enter a regular expression or reference a global [[manual:​regular_expressions|regular expression]] in "​Regexp"​ field.\\ In order to test the regular expression you can use "grep -E", for example: <code bash>for f in ext2 nfs reiserfs smbfs; do echo $f | grep -E '​^ext|^reiserfs'​ || echo "SKIP: $f"; done</​code>​Note that if some macro from the filter is missing in the response, the found entity will be ignored. ​ | |//​Filter// ​ |The filter can be used to only generate real items, triggers, and graphs for certain file systems. It expects [[manual:​regular_expressions|POSIX Extended Regular Expression]]. For instance, if you are only interested in C:, D:, and E: file systems, you could put {#FSNAME} into "​Macro"​ and <​nowiki>"​^C|^D|^E"</​nowiki>​ regular expression into "​Regexp"​ text fields. Filtering is also possible by file system types using {#FSTYPE} macro (e. g. <​nowiki>"​^ext|^reiserfs"</​nowiki>​).\\ You can enter a regular expression or reference a global [[manual:​regular_expressions|regular expression]] in "​Regexp"​ field.\\ In order to test the regular expression you can use "grep -E", for example: <code bash>for f in ext2 nfs reiserfs smbfs; do echo $f | grep -E '​^ext|^reiserfs'​ || echo "SKIP: $f"; done</​code>​Note that if some macro from the filter is missing in the response, the found entity will be ignored. ​ |
 |//​Description// ​ |Enter a description. ​ | |//​Description// ​ |Enter a description. ​ |