Examples: Integration of CCMS Metrics into MAI

Note Note

This section is part of the Extend Monitoring and Alerting Infrastructure with CCMS Metrics process. This process shows how you can extend technical monitoring with additional, previously not monitored CCMS metrics.

End of the note.

As well as the general procedure, it presents four CCMS metrics, and their integration into the Monitoring and Alerting Infrastructure (MAI), in detail. The four examples require four different data collectors to specify the collection of data for each metric. Both the data collector and its input parameters depend on the attributes of the CCMS metric to be integrated.

The following CCMS metric attributes, above all, determine the data collector to be used:

Does the metric output a numerical value?
Is the metric instance-specific or system-wide?
Is the metric object name relevant to identify the metric uniquely in a context?

Note Note

For more information about these attributes, see Determining CCMS Metric Attributes.

End of the note.

To determine which of the example metrics in the table below is relevant to you, determine the attributes above for the CCMS metric which you want to integrate into MAI, and work through the example which is closest to the attributes of your CCMS metric.

Metric	Numerical value?	Instance-specific/system-wide	Object name relevant
Integrate CCMS Metrics into MAI: Spool Service Queue	Yes	Instance-specific	No
Integrate CCMS Metrics into MAI: Update Queue Waiting Time	Yes	Instance-specific	Yes
Integrate CCMS Metrics into MAI: Operation Type Status	No	System-wide	No
Integrate CCMS Metrics into MAI: System-Wide Job Queue Length	Yes	System-wide	No