Previous Topic: Adapter Translation and NormalizationNext Topic: Resources and their Management


Metric Registration

In order for the Correlation engine to know what data may be requested, the Metric must register its presence and requirements with the Correlation engine.

Metric registration is the request by a Metric to receive Events, and only those that need to be included in its calculation. This request is done by the state of the Event identifier's Event type and Resource.

Registration can be done on the basis of a single Resource or a group of Resources.

Example:

For the following informational metric: "Number of down-times of Server X" and on the assumption that the data source provides a notification when a server goes up or down, and that the notification indicates whether it is up or down at a particular time, then the Registration is:

Event Type: Server Up/Down Event

Resource: Server X

Based on the above registration, what happens is that the engine filters out all Events that have up/down definitions in their Event type field in addition to having Server X in the Resource field.

Once a Contract is activated in the CA Business Service Insight system, all the Metrics register the relevant Events necessary for their calculations. Based on these requests, the correlation engine marks the Events relevant to each Business Logic. Once calculations begin, the relevant Events are sent to each Metric for calculation.