Incident-detection rules


Incident-detection rules determine how the system detects, analyzes, and notifies you about problems (incidents) in your web traffic.

The BMC Real End User Experience Monitoring provides the following types of incident-detection rules:

Incident-detection rule types

Type

Description

ico_performance.pngPerformance

ico_performance.png

Performance rules cause the system to declare incidents when it detects an abnormal number of pages violating service level thresholds (SLTs).

Performance rules can be configured only for page Watchpoints.

ico_availability.pngAvailability

ico_availability.png

Availability rules cause the system to declare incidents when it detects an abnormally high percentage of requests with errors.

You can specify which errors the system monitors for incidents.

ico_ts_volume.pngVolume

ico_volume.png

Volume rules cause the system to declare incidents when it detects an abnormally high number of requests.

The Incident detection page of the Real User Analyzer component (on the Administration tab, point to Threshold and problem detection and click Incident detection) shows how many incident-detection rules of each type are configured for every Watchpoint.

Incident detection overview

inc-det.png

For every Watchpoint, you can specify the following information:

  • How the system identifies normal and abnormal behavior in your web traffic
  • When the system declares an incident
  • When the system notifies you that a critical incident has occurred (does not apply to regular incidents)
  • How the system correlates incident data with traffic properties to identify the root cause of an incident

Only 100 incidents can be active at a time in one account.

Related topics

Adding-an-incident-detection-rule
Detecting-incidents

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*