---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/impact

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure Root cause correlation alerts

# Configure Root cause correlation alerts {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Configure Root Cause Correlation (RCC) alerts to start receiving the Root Cause Analysis (RCA) reports for these alerts. Configure Root Cause Correlation (RCC) alerts based on a root cause analysis performed by Instance Observer RCC.

## Vorbereitungen

Role required: admin

## Prozedur

1. Navigate to ImpactPlatform HealthMonitorInstance Observer.
2. From the Alerts menu, select Alerts Console.
3. Select a production instance.
4. Select Get Snapshot.  
   Information about the alerts is listed in the table.
5. Select the reporting options:  
   * Instance
   * Date range
   * Metrics
   * Options:
     * Self-Service Alerts
     * Diagnostic Events
     {#configure-rcc-alerts__ul_r2l_n25_byb}
   * Add-ons
   {#configure-rcc-alerts__ul_mfv_fd5_byb}
6. Fine tune the alerts using the listed options.  
   For example
   * Set a threshold that triggers an alert if the transaction count anomalies persist for more than 10 minutes, or exceeds a certain number of standard deviations from the mean continuously for more than 10 minutes above or below the range, respectively. Job anomalies target the top X % of anomalous jobs based on the execution time and track the details of those jobs.
   * Test and fine tune the alerting by simulating persistence time, choose the window of an anomaly 5, 10, 15 minutes, and so on, or select the top 5, 10, or 15 percentage of jobs and verify that alerts are triggered correctly. Adjust the alert threshold, if necessary, to verify that the system provides meaningful and actionable alerts.
   * Choose the appropriate method for sending alerts based on your requirements, either email notifications, SMS messages, or integration.
   * Continuously monitor the alerts generated by the system. Regularly review the anomalies detected to understand the underlying causes and take appropriate actions, such as investigating potential issues or performing further analysis.
   {#configure-rcc-alerts__ul_fnd_lt5_2yb}
{#configure-rcc-alerts__steps_ebj_pyv_2yb}