Configuring custom monitors
This section describes how to create and configure custom monitors for monitoring network devices. The custom monitors are created for monitoring network devices based on SNMP.
Configuring custom monitors video
Configuration details
In the Add Monitor Types dialog box, with the Monitoring Profile set to SNMP, and the Monitor Type set to Custom monitor, provide the following details:
Field | Description | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Custom monitor Creation | |||||||||||||||||||||
Custom monitor details | |||||||||||||||||||||
Monitor name | Enter the monitor display name. Note The PATROL Agent will restart automatically if you modify or delete a monitor. | ||||||||||||||||||||
Monitor category | Select one of the following monitor category:
| ||||||||||||||||||||
Monitor counters | |||||||||||||||||||||
Counter details | |||||||||||||||||||||
Counter name | Enter the counter name to poll from the system. | ||||||||||||||||||||
OID/Formula | Enter the OID or a formula to poll from the system. It can be a single OID or multiple OIDs defined with a valid formula. The OID should begin with a period (.). OIDs used for monitoring are expected to return numerical or enumerated values. While the values can be of any range, TrueSight itself is limited to use values up to 2,147,483,647. It is possible that the OID, or the used formulate may return a value larger than this upper bound limit. In that case, the parameter assigned to is set to 2,147,483,647. However, to reduce the parameter value, use the scaling feature of the KM. For example, you can use a scaling factor of 0.001 to bring a value within the TrueSight limit. For more information about scaling, see scaling. For example:
| ||||||||||||||||||||
Unit | Select one of the following units:
| ||||||||||||||||||||
Custom unit | (Optional) Enter the unit of the counter. This option can be used if none of the pre-defined units can serve as the counter unit. | ||||||||||||||||||||
Metadata | |||||||||||||||||||||
Graph by default | Enable this option to plot the counter type value on the graph by default when the Show Graph is selected on the BMC ProactiveNet user interface. | ||||||||||||||||||||
KPI | Enable this option for the counter type to be a Key Performance Indicator. | ||||||||||||||||||||
Availability | Enable this option to monitor the availability of the counter type. | ||||||||||||||||||||
Statistical | Enable this option indicate performance data. By default, this option is enabled. | ||||||||||||||||||||
Response time | Enable this option to monitor the response time of an action or operation. | ||||||||||||||||||||
Delta | Enable this option for delta counter type. | ||||||||||||||||||||
Calculation | |||||||||||||||||||||
Measure as | Select one of the following for measuring the counter:
Delta and Rate are calculated based on OIDs, and not on the formula final result. | ||||||||||||||||||||
Scale | Enter a number to scale on the counter. TrueSight console monitors the attributes based on the values returned per OID. Sometimes the values may be too big, too small, or just inadequate for monitoring. Scale definition within the policy allows you to normalize the values before you use them for monitoring. Once scale is defined, counter value will be calculated according to the following formula: Counter value*scale Scale can be any decimal number. For example; 0.1, 0.0001, 32, 1024. Example: In the below table, the value of attribute Inbound Bytes exceeded the TrueSight console limit. Hence the value is scaled down to see the actual value. However, the unit of the attribute changes from bytes to Gigabytes.
| ||||||||||||||||||||
Monitor OBJECT-TYPE(s) | |||||||||||||||||||||
OBJECT-TYPE details | |||||||||||||||||||||
Name | Enter the name of the object type that groups all child instances. | ||||||||||||||||||||
Discovery key | Enter the OID to poll in order to discover all of the instances for this object type. The Instance name is produced based on the OID's defined for discovery. The first one is used as is followed by the rest enclosed with (...). Example: Using .1.3.6.1.2.1.2.2.1.2, .1.3.6.1.2.1.2.2.1.1 will generate instances named using ifDescr(ifIndex). You can define multiple OIDs separated by a comma. Leave this field blank if this object type is having only counters without discovery objects. | ||||||||||||||||||||
OBJECT-TYPE counters | |||||||||||||||||||||
Counter name | Counter name to poll from the system. | ||||||||||||||||||||
OID/Formula | Enter the OID or a formula to poll from the system. It can be a single OID or multiple OIDs defined with a valid formula. The OID should begin with a period (.). | ||||||||||||||||||||
Unit | Select one of the following units:
| ||||||||||||||||||||
Custom Unit | (Optional) If none of the predefined units can serve as the counter unit, then enter the unit of the counter. | ||||||||||||||||||||
Metadata | |||||||||||||||||||||
Graph by default | Enable this option to plot the counter type value on the graph by default when the Show Graph is selected on the BMC ProactiveNet user interface. | ||||||||||||||||||||
KPI | Enable this option for the counter type to be a Key Performance Indicator. | ||||||||||||||||||||
Availability | Enable this option to monitor the availability of the counter type. | ||||||||||||||||||||
Statistical | Enable this option indicate performance data. By default, this option is enabled. | ||||||||||||||||||||
Response time | Enable this option to monitor the response time of an action or operation. | ||||||||||||||||||||
Delta | Enable this option for delta counter type. | ||||||||||||||||||||
Calculation | |||||||||||||||||||||
Measure as | Select one of the following for measuring the counter:
Delta and Rate are calculated based on OIDs, and not on the formula final result. The default measure is Raw. | ||||||||||||||||||||
Scale | Enter a number to scale on the counter. Once scale is defined, counter value will be calculated according to the following formula: Counter value*scale Scale can be any decimal number. For example; 0.1, 0.0001, 32, 1024. |
After entering all the required details, click OK and Close button and save the policy.
Comments
Log in or register to comment.