---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Use Cloud Root Cause Analysis reports

# Use Cloud Root Cause Analysis reports {#ariaid-title1}

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

Root Cause Analysis reports help you troubleshoot issues with Cloud Provisioning and Governance. Use the reports to view details about the Cloud Orchestration Trail and the Cloud API Trail.

## Before you begin

Role required: sn_cmp.cloud_operator or sn_cmp.cloud_admin

## Procedure

1. In the Cloud Admin Portal, navigate to OperateRoot Cause Analysis Dashboard.  
   The Root Cause Analysis dashboard appears, with the Cloud Root Cause Analysis Dashboard displayed by default. This gives you a graphical summary of the Cloud Orchestration Trail with trail records under the reports. These charts group records by different attributes:
   * Trails: groups data by the template, which is the component, such as a resource block or blueprint, on which a Cloud Provisioning and Governance action was applied.
   * Stages: groups data by the stage, which identifies when the transaction took place.
   * Components: groups data by the component in the system that was involved in the transaction.
   * Steps: groups data by the step, which is the descriptive step associated with a stage and component.

   {#use-cloud-root-call-analysis__ul_l21_wqj_4z}See [The Cloud Orchestration Trail](https://servicenow-prod.fluidtopics.net/Pv2euABZyLwAxQ9l_vDM8w "The Cloud Orchestration Trail is an activity log for all cloud resource activity on the instance.") for a list of possible steps.

   Requests are also broken down by requester in the bar chart below. Stacks are broken down by datacenters.  
   Figure 1. The Cloud Root Cause Analysis dashboard
2. Select an option to obtain the tag data that you want on the report.

   | Goal | Do this |
   | Filter the data | Select from the options, such as the Level, Date, and the Request Item. |
   | See updated data | Point to the top of any of the charts until the refresh icon (![Refresh icon]()) appears, and then click the icon. |
   | Save an image of a chart | Point to any of the charts until the options icon (![Options icon]()) appears, and then select Save as PNG or Save as JPEG. |
   |-|-|

   {#use-cloud-root-call-analysis__choicetable_mjh_3zh_4z}
3. Click any Cloud Orchestration API Number to view that specific record.  
   See [The Cloud Orchestration Trail](https://servicenow-prod.fluidtopics.net/Pv2euABZyLwAxQ9l_vDM8w "The Cloud Orchestration Trail is an activity log for all cloud resource activity on the instance.") for field descriptions.
4. To view reports about the Cloud API Trail, click the Cloud API Dashboard tab.  
   This dashboard shows you several reports for the Cloud API Trail grouped by provider, status, and connectors. You can also see information the methods that were invoked and the API invocations today.  
   Note:  
   Starting with Yokohama the Cloud API dashboard will be hidden and no longer activated on new instances but will continue to be supported. The Cloud Services Catalog application provides this functionality
   now. The application is being prepared for future deprecation.  
   Figure 2. The Cloud API dashboard {#use-cloud-root-call-analysis__cloud-api-dashboard}
{#use-cloud-root-call-analysis__cloud-api-dashboard}
5. Click any the data in the graphs to open the matching Cloud API Trail records.  
   See [The Cloud API Trail](https://servicenow-prod.fluidtopics.net/RyujrE0aSFNK_AH7BTZvdQ#cloud-api-trail "The Cloud API Trail is an activity log for all activity that uses the Cloud API and goes through the MID Server.") for descriptions of the Cloud API Trail form fields.
{#use-cloud-root-call-analysis__steps_i4q_cqj_4z}

*[\>]: and then