The agent and gateway monitor resource metric data, which can raise an alert when metric value exceeds a specified threshold. After you create a metric, create a monitor of the same collector type.
To create a metric, configure the following parameters on the CREATE METRIC page:
Attributes | Description |
---|---|
Metric Scope | Partner- or client-Specific metric. |
Adaptor Type | Example: VMware, Cisco UCS, and XenServer. |
Name | Unique name associated with the metric. |
Tag | User-defined name for filtering. |
Display Name | Unique metric display name. |
Description | Metric description. |
Data Point type | Metric data type. |
Units | Metric value unit. |
Unit Multiplication Factor | Value to multiply the metric by based on the specified **Units**. |
Data Point Conversion | Metric data conversion mechanism:
|
Metric Processing | Metric processing specification:
|
Metric name format
The following are acceptable formats for a metric name:
- Metric names should not contain a dot (.), instead use an underscore (_) between the words.
system.cpu.usage
is not validsystem_cpu_usage
is valid - A metric name can have a maximum of five underscores “_”. A metric name cannot start or end with an underscore.
- A metric name can contain numeric values (0-9), but cannot start with a numeric value.
- A metric name should be case-insensitive.
- The length of the metric name should be less than or equal to 100, including underscores.