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:

AttributesDescription
Metric ScopePartner- or client-Specific metric.
Adapter TypeExample: VMware, Cisco UCS, and XenServer.
NameUnique name associated with the metric.
Tag NameUser-defined name for filtering.
Display NameUnique metric display name.
DescriptionMetric description.
Data Point typeMetric data type.
CategorySelect the appropriate category for the metric.
UnitsMetric value unit.
Unit Multiplication FactorValue to multiply the metric by based on the specified **Units**.
Data Point ConversionMetric data conversion mechanism:
  • Value = Value used to convert the metric data point.
  • Enumerated Map = Map for indexing the metric data point value. Also specify the State Descriptions and Use formatted value in fields.
Metric ProcessingMetric processing specification:
  • Notification = Provide notification
  • Graph Specify handling criteria:
    • Warning if value = Warning-level alert threshold value.
    • Critical if value = Critical-level alert threshold value.
    • Subject = Metric subject. Populated by default and should not be changed.
    • Description = Metric description. Populated by default and should not be changed.
  • Graph and Notification Specify handling criteria:
    • Warning if value = Warning-level alert threshold value.
    • Critical if value = Critical-level alert threshold value.
    • Subject = Metric subject. Populated by default and should not be changed.
    • Description = Metric description. Populated by default and should not be changed.

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 valid
    system_cpu_usage is valid
  • A metric name can have a maximum of ten 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 255, including underscores.

Graphs with New Metrics data

PropertyExpected BehaviourWorkaround / Details
Graphs plotting frequency Vs Monitoring FrequencyThe graph shows raw samples based on default step value: 1min i..e the plotting frequency for graphs irrespective of configured monitoring frequency.
  • If metrics are collected every 5 minutes with a default step value of 1 minute ( i..e plotting with 60s frequency), the same value is plotted from T to T+5 minutes (e.g., 8:00 AM to 8:05 AM). This is the default behavior which will show the same value from 8:00 AM to 8:05 AM in plotter graph.
  • If the Availability/Agent status/Gateway Status/Interface Status/ or any metric triggers an alert indicating downtime and you want to see real gaps for monitoring frequency less than 5 minutes, refer to the section Visualize Real-time data.
Graphs plotting behavior
  • Default Plotting Frequency: The application plots the metric graphs at a default frequency of 1 minute.
  • Rendering Duration: The same metric value is displayed for up to 5 minutes.
  • Higher Frequency Monitoring: When the monitoring frequency is set to intervals greater than 5 minutes (e.g., 15, 30, or 60 minutes), gaps may appear in the graph.
  • Data Availability: For a 15-minute frequency, the next data point becomes available after 10 minutes, resulting in gaps where no new data is plotted.
    • This behavior ensures that the most recent data is visualized accurately, although it may lead to gaps when using longer monitoring intervals. Adjusting the monitoring frequency can help balance the need for real-time data visualization with the granularity of the data collected.
To avoid plotting gaps, ensure that the metric collection frequency matches the default graphing frequency or adjust the graphing frequency to match the metric collection intervals which is less than or equal to 5 minutes.

The recommend monitoring frequency for any metric should be <= 5 minutes

Visualize Real-time dataThe data points for new metric graph data are calculatedly plotted every 1 min except at the frequency time-interval.

In order to view real-time data, the metric graphs offer displaying the actual timestamps when the data was collected.Status and availability metrics need to show when data collection stopped, indicating a resource or service outage.

Graph > Expand Info section > shows “Real Time Data” option.
Metrics DetailsIn the new metrics system, templates that describe the relationship between different metrics are not available. User might see the legacy metrics name while detailing, which is expected behavior and these will be slowly transitioned to show in the new metric nomenclature.To view the relationships between template and metrics, navigate to the Monitors tab where detailed information is provided.
Default Time Period for GraphsDefault time-period has been set as 1 Hour from the existing 4 Hr windowDefault Time-period is now set 1H
Multiple metricsThe new metric visualization supports only a single metric graph data.The new metric visualization doesn’t support multiple metric graph data visualization due pagination and hence not available.