Billing and usageUsage Insights dashboards

Usage Insights dashboards

Each Grafana Cloud Pro and Advanced stack has a Loki data source that collects logs across all of the stacks in your organization, as long as they’re in the same region. This data can be explored like any other Loki data source, and the information is displayed across three dashboards by default: Overview, Data sources, and Query Errors.

NOTE: Usage Insights dashboards are available to users with Grafana Cloud Pro and Advanced plans. If you’re self-hosting Grafana Enterprise, see Assess dashboard usage in the Grafana Enterprise documentation.

Usage Insights Loki data source

The Usage Insights Loki data source is named grafnacloud-<YOUR-SLUG>-usage-insights, where <YOUR-SLUG> is the first part of your stack URL. For example, if your stack URL is grafanadocs.grafana.net, the data source is called grafanacloud-docsgrafana-usage-insights.

To learn more about what is logged, see Export logs of usage insights in the Grafana Enterprise documentation.

Usage Insights dashboards

To find the Usage Insights dashboards:

  1. Click the Search (magnifying glass) icon in your Grafana stack.
  2. Search for the folder named GrafanaCloud in the GrafanaCloud folder.
  3. Select one of the following dashboards.
  • Overview This dashboard gives you a top-level view of how users are engaging with Grafana Cloud. You can see overall activity metrics, and per-stack metrics. Below the main graph, you can see a breakdown of events and errors by user, dashboard, and data source.

  • Data Sources Data Source Insights provides a view of data source usage and health. Here you can view your data sources by query count and error rate. Click on a data source name (or ID) to load further details. If you know the ID of a data source, you can also directly enter it in the text box.

  • Query Errors The Query Errors dashboard shows error logs and details. You can search the full log line text, and see an approximate categorization. Use it to identify unhealthy data sources, broken dashboards, and users that are running queries with errors.