---
sourceDocument: Yokohama Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/impact

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Generate RCC report

# Generate RCC report {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Generate a detailed Root Cause Correlation report that can be used to identify and narrow down underlying issues in your instance that caused a performance degradation and related alert.

## Before you begin

Role required: admin

## Procedure

1. Navigate to ImpactPlatform HealthMonitorInstance Observer.
2. From the Performance menu, select Semaphores.  
3. Select the report options.  
   * Instance: Only production instances are supported with the RCC feature.
   * Metrics: Select from the available metrics for RCC report generation. Refer to the RCC symptom categories section in [Root Cause Correlation](https://servicenow-prod.fluidtopics.net/3R8AcCUX1A0zp51F2eHSCg "Root Cause Correlation (RCC) streamlines performing a root cause analysis by automatically correlating metrics, logs, and event information for supported symptoms on production instances for the last 24 hours.") for the supported metrics.
   * Date Range: Select a date range
   * Options: Select the type of alert. For RCC, Self Service Alerts is supported.
   * Select the Node type: Options are available in the list.
   {#generate-rcc-report__ul_gsf_nbh_d2c}
4. Select Get Snapshot to generate the RCC report.  
5. Select an alert icon from the report to review additional information about the issue.  
   Note:  
   Options available on Report and Charts:
   * Select a data point to view additional actions or remove the entry.
   * Right-click to isolate a data point.
   * Select and drag across the chart to drill down.
   * Download to PNG, SVG, or CSV files or view transactions on the instance.
   * Change the report type.
   {#generate-rcc-report__ul_wbt_p1h_3xb}  
   The information for the RCC alert is displayed with the option to generate the root cause of the alert.
6. Select Generate Root Cause.  
   A status message displays with RCC generation information.

## What to do next

Check the RCC History page to further investigate the issues that caused the alert to trigger. See [Utilizing RCC history to perform root cause analysis](https://servicenow-prod.fluidtopics.net/fETmnLsXWOGRwXSKQAZIxA "Check the RCC History page to further investigate the issues that caused an alert to trigger.") for more information.

*[\>]: and then