Use the following guidelines for defining registrations:
For example, where calculating overall average response times of application servers, the Response Time Event needs to be reported only when it is associated with one of these application servers (that is, where the Resource Type of the Resource associated with the event is 'Application Server'). In such a case, the system may have other types of Resources such as sites or routers using the same Event Type to send data, so to distinguish between them. The Resource Type to be reported on ('Application Server') should be added to the registration command as the 3rd parameter.
The reason for this is that when a Resource change occurs, the Engine marks the Metrics associated with this Resource as 'requiring a recalculation'. In a case where the Metric registers only by Event type, the Engine views the Metric as registered to all Resources and therefore marks it for recalculation upon activation of each Resource. To avoid this, you must use the 'optional' 3rd parameter of the resource type.
Note: Registrations can also be handled by the Registration tab within each Metric. This interface provides a wizard which guides you through the process for the selected metric.
|
Copyright © 2013 CA.
All rights reserved.
|
|