A domain manager reports an infrastructure alert, which is a fault condition on a CI in CA SOI. All infrastructure alerts begin their CA SOI lifecycle as events. Events that have a severity greater than normal and come out of Event Management event policy filtering become infrastructure alerts.
CA SOI automatically associates infrastructure alerts with their corresponding CI and assigns to each alert condition a severity that determines the CI color on the Operations Console. One CI can have several alert conditions simultaneously, and the alert with the highest severity determines the impact on the CI and its color. When the alerted CI belongs to a service, CA SOI calculates the impact value from the seriousness of the fault condition and the importance of the CI to the services it supports.
Infrastructure alerts typically include a URL so that an operator can navigate in context from the Operations Console to the originating domain manager and can view the alert in its original context.
Infrastructure alerts belong to one of the following categories:
Indicates the level of excellence that consumers of a resource experience. For example, performance degradation detected by CA APM takes the form of a quality alert.
Indicates the likelihood of delivering the service quality that is required to support business objectives. For example, an alert specifying that a computer system has low disk space is a risk alert. If no category is defined, risk is the default category.
These categorizations help determine the quality, risk, and health value for any associated service.
Note: For more information about how alert quality and risk affect the service impact and health, see the Service Modeling Best Practices Guide.
Depending on their service association, infrastructure alerts can appear as the following types:
Infrastructure alerts are service impacting when they affect a CI that is part of a managed service. You can view these alerts when viewing the service in the Operations Console or other interfaces.
Infrastructure alerts are non-service impacting when they affect CIs that are not part of a managed service. These alerts appear under associated alert queues on the Alert Queues tab of the Operations Console. If the alert does not meet the criteria of any defined alert queues, it appears as a part of the Default queue. You can perform the same operations on non-service impacting alerts (assignment, escalation, and so on) as you can on service impacting alerts.
|
Copyright © 2013 CA.
All rights reserved.
|
|