Cloud vs Non-cloud insights dashboard in Service Graph Workspace
Summarize
Summary of Cloud vs Non-cloud insights dashboard in Service Graph Workspace
The Cloud vs Non-cloud insights dashboard in Service Graph Workspace provides visual charts and detailed breakdowns of IT resources hosted on cloud services versus those on non-cloud (local or other) environments. This distinction applies to key Configuration Item (CI) classes such as applications, databases, and datacenters. It helps organizations gain visibility into resource deployment across platforms like Microsoft Azure Cloud or internal infrastructure, which might otherwise be difficult to track.
Show less
Prerequisites and Configuration
- The Cloud Service Accounts [cmdbcicloudserviceaccount] table must exist in your system.
- The Logical Datacenter [cmdbcilogicaldatacenter] table requires at least one cloud datacenter record.
- The Datacenter Types [sncmdbwsdatacentertype] table must include at least one cloud storage-classified datacenter (e.g., Azure Datacenter).
- Charts only display data for cloud services that have corresponding records in the Datacenter Types table.
- Organizations can add or classify datacenters as cloud or non-cloud to refine dashboard accuracy.
Key Features
- CI Classes Bar Chart: Displays bars representing pairs of CI classes and storage types (cloud or non-cloud). Data is refreshed daily via scheduled jobs staggered to optimize system performance. Administrators can exclude irrelevant CI class/type pairs.
- Interactive Drill-down: Selecting bars opens detailed panes with two tabs:
- Cloud vs Non-cloud CIs: Bar charts and lists showing CIs by cloud or non-cloud status, with ability to access individual CI details.
- CI Classes by Cloud Providers: Pie charts breaking down cloud-hosted CIs by provider, enabling further drill-down into specific CIs.
- Latest Updates and Job Management: Users can view the status of scheduled jobs that generate chart data, with color-coded indicators for success or failure. Administrators can activate or deactivate individual or all jobs.
- Application Services Pie Chart: Uses the Service Configuration Item Associations table to classify application services as Cloud, Non-cloud, Hybrid, or Unknown based on their CI composition. This chart allows drill-down to list views and dependency maps for application services.
Operational Considerations
- Scheduled jobs have hard-coded limits: a 2-hour timeout and a maximum of 500,000 records collected. Jobs exceeding these limits stop automatically.
- Jobs failing to complete for 3 consecutive days (default) are automatically disabled to prevent resource drain.
- Administrators can adjust this failure threshold via a system property and can manually resume disabled jobs.
Benefits for ServiceNow Customers
This dashboard enables ServiceNow customers to effectively monitor and analyze their resource distribution across cloud and non-cloud environments. By providing clear visualizations and drill-down capabilities, it helps optimize infrastructure management, supports strategic cloud adoption decisions, and improves operational transparency. The built-in job management features ensure reliable data updates while protecting system performance.
Charts showing counts and details for resources that are hosted on various cloud services versus those resources that aren't, with breakdown by key CI classes such as applications, databases, and datacenters.
Resources can be deployed on cloud services such as the Microsoft Azure Cloud, or on the local instance or other non-cloud solutions. For some ongoing operations in the organization, it might be necessary to have those details that can be difficult to obtain.
- The table Cloud Service Accounts [cmdb_ci_cloud_service_account] must exist.
- The Logical Datacenter [cmdb_ci_logical_datacenter] table must contain at least one record for a cloud datacenter.
-
The Datacenter Types [sn_cmdb_ws_datacenter_type] table must contain at least one record for a datacenter that is classified as cloud storage in the organization. In the base system, this table is pre-populated with several records for common cloud services such as the Azure Datacenter [cmdb_ci_azure_datacenter] class. The chart calculates and shows data only for cloud services for which there's a record in the Datacenter Types [sn_cmdb_ws_datacenter_type] table.
For details about adding datacenters in your organization, with the cloud or non-cloud classification, see Configure datacenters for Cloud vs Non-cloud resources in Service Graph Workspace.
- CI classes bar chart:
Each bar in the CI classes chart represents a pair of a CI class and a storage type (cloud, non-cloud), such as the bar for Applications/Cloud. For each bar, there's a scheduled job that runs every 24 hours to collect and calculate the data for the bar. The running time depends on the amount and complexity of the data that a job collects, which can be different for each scheduled job. Also, the schedules of the jobs are staggered so that they don't all run at the same time and exhaust resources. For details about the class-specific criteria used for the chart calculations, see Class criteria in Cloud vs Non-cloud resources chart in Service Graph Workspace.
If there’s a CI class/type pair that isn't important in the organization, you can exclude that pair from the CI classes chart. For more details, see Configure classes for Cloud vs Non-cloud resources in Service Graph Workspace.
On the CI classes chart, you can:-
Select a bar to open the Cloud vs Non-cloud resources pane. Then, select either of the following tabs to drill down into further details for the bar:
- Cloud vs Non-cloud CIs
- Shows a bar chart for CIs stored on a cloud service and those CIs that aren't, per CI class. For each CI class, select the cloud or the non-cloud bar to show the CIs that are associated with the selected bar, in a list view. You can then select a CI from the list to further drill down to the CI details pane.
- CI Classes by Cloud Providers
- Pie charts per CI class with more granular details for those CIs that are hosted on cloud providers. Pie slices have randomly-selected colors, and they show a breakdown by cloud providers for various CI classes. For each pie, select a slice to show the CIs that are associated with the pie slice, in a list view. You can then select a CI from the list to further drill down to the CI details pane.
-
Select Latest updates to see updated status for the scheduled jobs that produce the data for the chart. Status is color-coded to indicate whether the job has completed successfully (green), or failed to complete (red).
-
- Application Services pie chart:The Application Services pie chart uses the Service Configuration Item Associations [svc_ci_assoc] table and checks the cloud/non-cloud status of application service CIs in the CI classes chart. Application services in the Application Services pie chart are classified as follows:
- Cloud: All of the CIs in the application service have been determined to be hosted on a cloud service.
- Non-cloud: All of the CIs in the application service have been determined not to be hosted on a cloud service.
- Hybrid: The application service contains a mixture of CIs where some are hosted and some aren't hosted on cloud services.
- Unknown: The cloud/non-cloud classification couldn't be determined because some of the application service CIs aren't classified as cloud or non-cloud CIs.
Note:Because classification of Application Services depends on the classification of CIs in the CI classes chart, there might be some discrepancy between the two charts. This can occur if an application service CI changed its cloud/non-cloud status, and the Application Services chart hasn't refreshed yet to reflect that change.Select the Application Services chart to access the list views of the associated application services, grouped by cloud/non-cloud classifications. From those list views, you can drill down to the Dependency Views map for application services.
The scheduled jobs associated with the charts are set up with several hard-coded limits that if exceeded, result in failure conditions that are reflected in the job status. Timing out is set to two hours and the maximum number of records to collect is set to 500,000. If a job exceeds any of those limits, it's automatically stopped.
- Modify the default number of consecutive days that are counted by adding the sn_cmdb_ws.insight.category.disable_after_failure system property to the System Properties [sys_properties] table and then setting its value. For more details, see Add a system property.
- Resume a disabled Cloud vs Non-cloud resources scheduled job.