AutoPatrol
191
edits
Difference between revisions of "UM:Basic Concepts"
→DCI (Data Collection Items)
| Line 54: | Line 54: | ||
Every node can have many parameters, like CPU utilization | Every node can have many parameters, like CPU utilization, amount of free memory or disk space usage. The management server can collect these parameters, check them for threshold violations and store them in the database. In NetXMS, parameters configured for collection are called Data Collection Items or DCI for short. One DCI represents one node's parameter, and unlimited number of DCIs can be configured for any node. | ||
Each data collection item has various attributes controlling its handling: | Each data collection item has various attributes controlling its handling: | ||
{| class="wikitable" | {| class="wikitable" style="width: 70%" | ||
! Attribute || Description | |||
|- | |- | ||
| Description || A free-form text string describing DCI. It is not used by the server and is intended for better information understanding by operators. | | Description || A free-form text string describing DCI. It is not used by the server and is intended for better information understanding by operators. | ||
| Line 67: | Line 68: | ||
| Data Type || Data type for a parameter. Can be one of the following: Integer, Unsigned Integer, 64-bit Integer, 64-bit Unsigned Integer, Float (floating point number), or String. Selected data type affects processing of collected data — for example, you cannot use operations like ”less than” or ”greater than” on strings. | | Data Type || Data type for a parameter. Can be one of the following: Integer, Unsigned Integer, 64-bit Integer, 64-bit Unsigned Integer, Float (floating point number), or String. Selected data type affects processing of collected data — for example, you cannot use operations like ”less than” or ”greater than” on strings. | ||
|- | |- | ||
| Retention Time || This attribute specifies how long collected data | | Retention Time || This attribute specifies how long collected data must be kept in the database, in days. Minimum retention time is 1 day, and maximum is unlimited. However, keeping too many collected values for too long will lead to significant increase of your database size and possible performance degradation. | ||
|- | |- | ||
| Schedule Type || Type of the collection schedule used; can be either simple or advanced. In a simple mode, values are taken from target at fixed intervals. In an advanced mode, cron-like scheduling table can be used to specify the exact time for polling. This can be useful if, for example, you wish to check the file size every Monday and Friday at 7:00. | | Schedule Type || Type of the collection schedule used; can be either simple or advanced. In a simple mode, values are taken from target at fixed intervals. In an advanced mode, cron-like scheduling table can be used to specify the exact time for polling. This can be useful if, for example, you wish to check the file size every Monday and Friday at 7:00. | ||