---
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


---

# Root cause correlation

# Root cause correlation {#ariaid-title1}

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

Root Cause Correlation (RCC) finds a root cause by automatically correlating metrics, logs, and event information for supported symptoms on production instances for the last 24 hours.

## RCC symptom categories {#root-cause-correlation__section_kwv_1sf_d2c}

The RCC feature is available for self-service alerts and Critical or Warning performance symptom categories:

* Memory
* Longest running sessions
* Slow transactions
* Cache flush
* Database locks
* Database impacts
{#root-cause-correlation__ul_scc_qwf_d2c}
The table describes the symptom categories and the corresponding alerts that the RCC engine detects.  
{#root-cause-correlation__table_jpp_xtf_d2c__entry__3}

| Symptoms​ categories | Description | Corresponding alert |
|-|-|-|
| Database Impact​ | Helps you to identify and address extended SQL queries impacting database performance, tied to high execution time, or increased volumes. The query patterns give snapshots of 30-minute and 60-minute durations from the time that the impact is observed on query execution times.​ | Database response time |
| Cache Flush​ | Cache flushes and node restarts are detected, as well as high service saturation levels that may have occurred around the time a performance alert was triggered.​ | Default semaphore mean |
| Longest Running Session​ | * Searches for the top long-running sessions in mean time to recover (MTTR) logs * Identifies the top transaction pattern hash with the highest processing times and then the transaction IDs. {#root-cause-correlation__ul_ink_ff3_mhc} | Default semaphore mean |
| Slow Transactions ​ | * Identifies the top long-running transactions using the total duration, including ACL time, SQL time, CPU time, processing time, BR time, and script time. * Returns the transaction IDs, the pattern hash, and these metrics to help you identify the specific causes of long-running transactions. {#root-cause-correlation__ul_wjz_1zf_d2c}​ | Default semaphore mean​ |
| Memory​ | * Pinpoints the three nodes most impacted by garbage collection pauses, determined by the aggregate duration of the pauses. * Identifies any transactions or worker threads on these nodes that exceed 200 seconds. Hinweis: Users are advised to review these long-running or frequently recurring threads. {#root-cause-correlation__ul_eck_lyf_d2c} | Node Garbage Collection Time |
| DB locks​ | The RCC engine monitors innodb_row_lock_waits and threads_running to detect anomalous database lock events that occur when a database operation requires exclusive access.​ | Threads running​ |
[Tabelle : 1. Targeted symptoms categories and corresponding alerts]

{#root-cause-correlation__table_jpp_xtf_d2c}  
Hinweis:  
As soon as any of the aforementioned alerts or Critical or Warning performance are identified, the system automatically generates an RCA report after waiting for a maximum of 10 minutes, depending on the conditions.

## RCC report statuses {#root-cause-correlation__section_njd_z2h_d2c}

RCC report statuses can be:

* RCC In progress: The RCC report generation is being generated.
* RCC generated: The report has been successfully generated.
* No RCC found: When there isn't enough information to generate the report.
* RCC failed: Returned when there's a technical issue, generally remedied to regenerate the report.
{#root-cause-correlation__ul_tqy_1fh_d2c}