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


---

# Use the Root cause analysis history

# Use the Root cause analysis history {#ariaid-title1}

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

Check the Root cause analysis (RCA) History page to investigate the issues that caused an alert to trigger or performance to degrade to Critical or Warning.

## Vorbereitungen

Role required: admin

## Prozedur

1. Navigate to ImpactPlatform HealthMonitorInstance Observer.
2. From the Alerts menu, select Root Cause Analysis History to display the history of reports for all users in a selected instance for the last seven days.  
3. Select an RCA entry to drill further into the issue that caused the alert.
4. From the RCA reports page, select an entry with the icon of Self-Service alert generated (RCC generated).  
   Directly link to the issue that caused the alert from the table to further investigate the issue and to rectify the issue.  
   Hinweis:  
   The RCA report may also be generated from the Alerts Console.

   You can also access the RCA reports using the Self-service alert icon on the performance pages.
5. **Wahlweise:** Navigate to ImpactPlatform HealthMonitorInstance Observer.
6. From the Alerts menu, select Alerts Console.
7. Select a production instance.
8. Select Get Snapshot.  
   The table contains information on the alerts.
{#utilizing-rcc-reports-perform-root-cause-analysis__steps_pbs_zh3_d2c}