Cloud Resources dashboard

The Cloud Resources dashboard shows the aggregated view of all your cloud resources, their combined analytical views, and a visual summary and detail of all your cloud resources.

Important: The Cloud Resources dashboard has been replaced by the Cloud Resources explorer in the Cloud Discovery Workspace store application. For more information, see Cloud Resources Explorer.

Use cases

For examples of how someone in your organization could use this dashboard, see the use cases.

Data visualizations

Access the Cloud Resources dashboard

To access the Cloud Resources dashboard, navigate to Discovery > Cloud Resource Dashboard or Cloud Provisioning and Governance > Cloud Resource Dashboard.

Customize the Cloud Resources dashboard

Customize your dashboard In each cloud provider tab by filtering these attributes:

• Service Account: All the service accounts that are specific to the cloud provider tab selected are listed.
• Datacenters: The datacenters are populated based on the cloud provider.
• Resource Group: This filter is only applicable for Microsoft Azure and restricts objects and resources to the chosen resource group.

Use these database views with resource tags to create your own dashboard.

The below resources that are supported for GCP are populated by GCPResourcePopulateScheduledJob.

Scheduled jobs

Since a separate scheduled job is triggered every 30 minutes for each cloud provider, you can verify if the last job was successful. If the scheduled job was not successful, you can manually trigger the job by going to the System Definition > Scheduled Jobs. Select the job for the affected cloud provide and click Execute Now.

The refresh jobs run every 30 minutes to populate and update the date in the analytics tables. You can increase this frequency to get more updated data.

Synchronization is needed if:

• The Resource Status was updated from installed to another status (for example, retired or canceled).
• Any new resources were recently discovered.

Synchronization is not needed if:

• No resources were updated.
• There are new resources which were not recently discovered.

Important to note:

• Only one job can run at a time. For example, if an AWS job is already running, you cannot trigger another AWS job.
• If the LDC and service account fields of a CI resource is empty, the resource may not be associated with any LDC in the CI Relationship [cmdb_rel_ci] table or the resource is a generic cloud resource of IAM type and the fields are empty.
• Only the resources with installed status set to installed are counted and represented in the cloud resources dashboard widgets.
• If a new resource is discovered after the scheduled job run, then the next scheduled job adds the resource details in the analytical tables.
• If a job is marked as failed in the Cloud Dashboard Job Status [sn_disco_cd_cloud_dashboard_job_status] table, the reason for the failure is logged in the system logs. Filter the system log table by the job sys_id to fetch the error message.
• If IP-based discovery is used to discover the vCenter, the service account field of the VMware resource is left blank.
• The System Administrator should not delete the records from the analytics table since records deleted from the analytics table are not populated again by the scheduled job. Deletion of records leads to data inconsistency in the analytics table.
• To ensure complete refresh of the VMware records (including the service accounts) after changing the VMware resource discovery mechanism, delete the VMware records from the Cloud Dashboard Job Status [sn_disco_cd_cloud_dashboard_job_status] table and run the schedule job. In the Cloud Dashboard Job Status table, the provider field of all the VMware resources is set to vmware. You can use either vCenter IP discovery or service account discovery to discover the VMware resources.