Utilizing RCC history to perform root cause analysis

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read

    • Check the RCC History page to further investigate the issues that caused an alert to trigger.

    Before you begin

    Role required: admin

    Procedure

    1. Navigate to Impact > Platform Health > Monitor > Instance Observer.
    2. From the Alerts menu, select Root Cause Correlation History to display the history of reports for all users in a selected instance for the last seven days.
      RCC history log.
    3. Select an RCC entry to drill further into the issue that caused the alert.
    4. From the RCC 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.
      Note:
      The RCC report may also be generated from the Alerts Console.
    5. Optional: Navigate to Impact > Platform Health > Monitor > Instance Observer.
    6. From the Alerts menu, select Alerts Console.
    7. Select a production instance.
    8. Select Get Snapshot.
      Information for the alerts are listed in the table.