The Event connector creates CIs based on alert information that you can add to service models, or associates the alert with an appropriate existing CI. You can control the granularity of this CI creation and association in the connector to match the granularity of your modeled services and ensure that all alerts from the connector are considered appropriately in service impact analysis. The Event connector can create CIs or associate alerts with existing CIs at one of the following levels:
Creates CIs based on the alert's top-level device. For example, if an alert is associated with a specific process or memory usage, the connector creates an associated CI for the server that contains the process or memory. This is the default CI granularity.
Creates CIs based on the specific objects with which alerts are associated. This more granular method creates CIs based on the specific class association of the alert's subdevice. For example, the connector would create a CI for a CPU for an alert associated with high CPU usage.
Properly configuring the CI granularity level is vital to ensure that Event connector alerts are accurately evaluated in CA SOI. For example, if your service models in CA SOI contain only high-level CIs such as servers and network devices and the Event connector is configured to associate alerts at the subdevice level, alerts for specific CIs (such as services or users) within those high-level CIs will be associated with the specific CIs and not be considered as impacting the service. Conversely, if your services are granularly modeled in CA SOI but the Event connector is configured to associate alerts at the device level, alerts associated with specific CIs will be associated with device-level CIs, making it more difficult to discover the root cause of service degradation.
Follow these steps:
The View Policies page displays.
The Policy Configuration: SAMAdapter page displays.
Click Save.
The policy is configured.
The change takes effect.
|
Copyright © 2013 CA.
All rights reserved.
|
|