Built-in dashboards
Monitor services and identify patterns and outliers using built-in dashboards in Splunk Observability Cloud. Learn how to clone or export dashboards.
Splunk Observability Cloud provides built-in dashboards that give you immediate visibility into the technologies and services being used in your environment.
Built-in dashboards and the charts they contain are read-only. They are automatically created in your organization when you deploy any of the supported integrations. To view built-in dashboards:
-
In the Splunk Observability Cloud main menu, select Dashboards. Use the search bar to search for a dashboard, or select the chiclet for the dashboard under the Built-in dashboard groups section.
-
Navigate to the detail view of a navigator in Infrastructure Monitoring.
Built-in dashboards are optimized for monitoring populations as well as individual nodes. For each technology or service, Splunk Observability Cloud uses aggregations, percentiles, or Top N analytics functions to let you see patterns and identify outliers, and also provide individual metrics for insight into the functioning of single nodes.
Logs in built-in dashboards
Logs powering built-in dashboards come from the indexes that the user can access. Splunk Observability Cloud automatically triggers entity-index mapping generation for only the indexes that the user has permissions to access. The system identifies a user's accessible indexes based on their access token. Automatic entity-index generation occurs on demand when users access logs experiences in built-in dashboards, Related Content, or the APM service-centric view. For more information, see Entity-index mappings.
Clone a built-in dashboard
Built-in dashboards are read‑only, so you can’t directly save filters or time ranges to the dashboard, or make any changes to the charts on the dashboard. You need to clone the original dashboard and modify the cloned dashboard.
From the Dashboards page
To clone a built-in dashboard from the Dashboards page, follow these steps:
-
In the Splunk Observability Cloud main menu, select Dashboards.
-
In the Built-in dashboard groups section, expand the dashboard group that contains the dashboard you want to clone.
-
Select the dashboard you want to clone.
-
Select the Dashboard actions menu.
-
Select Save dashboard as….
-
In the Dashboard name field, specify a name for the cloned dashboard. Use a different name from the original dashboard to avoid multiple dashboards with the same name.
-
From the Dashboard permissions drop-down menu, configure permission settings for the cloned dashboard.
-
From the Dashboard group menu, find and select a dashboard group to save the cloned dashboard.
To learn more about dashboard permissions, see Read and write permissions in Splunk Infrastructure Monitoring.
Export a built-in dashboard
From the Dashboards page
To clone a built-in dashboard from the Dashboards page, follow these steps:
-
In the Splunk Observability Cloud main menu, select Dashboards.
-
In the Built-in dashboard groups section, expand the dashboard group that contains the dashboard you want to export.
-
Select the dashboard you want to export.
-
Select the Dashboard actions menu.
-
Select Export.
-
Select Download.
Clone a chart in a built-in dashboard to make changes
To clone a chart in a built-in dashboard, follow these steps:
-
Select the name of the chart you want to clone on the built-in dashboard. The chart opens in the Chart Builder view.
-
Make any changes you want in the Chart Builder view.
-
Select Save as... to save the cloned chart to another dashboard of your choice.
Filter built-in dashboards
In addition, you can use dimensions or properties to filter built-in dashboards and hone in on a specific slice of your environment. You can also use the Time Range selector to specify the time range for which you want to view the metrics. See Time range in Specify settings for all charts in a dashboard.
Use dashboard filters in logs chart queries
Use tokens in a logs chart SPL query to apply dashboard filter values when the chart runs.
Dashboard filters can pass selected values to a logs chart query. Add a token where you want a filter value to be inserted, then add a dashboard filter with a matching key.
The chart query uses the selected filter values. For example, if a user selects checkout, service=$service$ behaves like service="checkout".
If the filter is missing or has no selected value, the token does not narrow the query. For example, host=$host$ behaves like host=*. A dashboard filter that is not referenced by a token does not affect the chart.
Query examples
Use the following patterns in a logs chart SPL query:
-
Filter one field:
index=main host=$host$ -
Filter several fields:
index=main host=$host$ service=$service$ env=$environment$ -
Use a token in a pipeline:
index=main service=$service$ | stats count by host -
Use a dotted field name:
index=main k8s.node.name=$node$. If needed, quote the field name:"host.name"=$host$. -
Use the same token more than once in a query.
A single selected value, such as checkout, makes service=$service$ behave like service="checkout". Multiple selected values make it behave like service IN ("checkout","payments","cart").
For an exclude filter, env=$env$ behaves like env!="dev" for one excluded value. For multiple excluded values, it behaves like NOT env IN ("dev","test").
If the chart does not respond to a filter, check that:
-
The token name exactly matches the dashboard filter key.
-
The token uses the format
fieldName=$filterKey$. -
The token is in the SPL query for that logs chart.
-
The filter is on the same dashboard as the chart.
-
The SPL field on the left side of the equals sign is the field you want to filter.