TEC1382954: How do the incident age-out rules work in CEM?

Document created by strgu01 Employee on Jun 16, 2016Last modified by SamCreek on Jun 16, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC1382954
Last Modified Date:  6/8/2016
Authored By: strgu01

  • Products
    • CA Application Performance Management
  • Releases
    • CA Application Performance Management:Release:10.0
    • CA Application Performance Management:Release:10.1
    • CA Application Performance Management:Release:10.2
    • CA Application Performance Management:Release:CA APM 9.6
    • CA Application Performance Management:Release:CA APM 9.5
    • CA Application Performance Management:Release:CA APM 9.7
  • Components
    • WILY CEM

Introduction:

 

This describes the incident age-out rules in CEM.

 

Question:

 

How do the incident age-out rules work in CEM?

 

Environment: 

 

Introscope from 9.1x to 10.x

 

Answer:

 

Suppose you set the age out incident rule to 1440 minutes (which is one day; 60 * 24 = 1440) since the last defect was received. You expect the incident will automatically close after 24 hours after the last defect was received. However, you notice incidents are still open even after 24 hours have passed.

Incident age-out rules only work for the incidents in Pending status.

  Pending incidents are defect events that have occurred, but have not reached the impact threshold and are therefore not yet reported as incidents in CEM. Once an incident reaches Open status, that incident will never automatically age out. You must manually close incidents in Open status.

You can adjust this by configuring how long an incident can be in Pending status by changing the Impact Settings. When the Business Impact reaches the Moderate level, the incident changes to Open status.

 

Search the Entire CA APM Knowledge Base

Attachments

    Outcomes