MetricsView: Linux (Collectd) Custom Collector Task Setup

Device Type: MetricsView Platform

Glossary Entry:  Linux Custom Collector

Setting up and Installing a Linux Custom Collector

How to Edit a Linux Custom Collector Task

Wizard Interface

Task Name: Enter a name that describes the function of the task. For example “Server 2 CPU % in use”.

Task UID:  The UID is a unique ID that is generated for each task.  This ID is used to interface with the task in the API.

Collector:  Select the collector from which to retrieve the data for the task.

Custom Counterpath: reflects the relative path to the counter in the source system
for example : ..\cpu\0\cpu-idle
[local or remote machine]\[category]\[instance ]\[counter type] The Counterpath is generated automatically based on the values you select in the dropdown menus below.

Hostname:  The name or IP address of the target machine.

Legacy Advanced Interface

Once you have created a device, installed the Linux Agent and are adding or editing a custom collector task, you will be prompted to adjust the following settings:

MetricsView Collector dropdown shows a list a of all registered custom collectors. The Linux Collector will appear in this list after installation is completed.

Counterpath reflects the relative path to the counter in the source system
for example : ..\cpu\0\cpu-idle
[local or remote machine]\[category]\[instance ]\[counter type] The Counterpath is generated automatically based on the values you select in the dropdown menus below.

Both Interfaces

Category/Instance/Counter dropdowns will be filled with values automatically

Error Thresholds

Aggregate – All received data will be aggregated on a regular basis, according to the adjusted device frequency.

Maximum – the highest value from the array will be taken.

Average – the value is calculated as an average of all collected values.

Minimum – the lowest value from the array will be taken.

Min Threshold  – Results below this value will result in an error being triggered.

Max Threshold – Results exceeding this value will result in an error being triggered.

Ignore Errors if counter is not available – Each time during “Agent” <–>”Server” interaction the Agent asks if there are any new counters to check. In case there are instructions to gather stats on new counters the Agent will begin to gather them.

NO is selected – each failure to gather counter data will be reflected as an error in reports.

YES is selected – failures will be ignored.

Counter descriptions (in process):

CPU
interface
df (space usage)
disk (Disk I/O)
memory