Ready-to-use Observability Grafana Dashboard

Few months ago there was a request in the Community for a ready-to-use io.Insights Dashboard for Grafana. So we’ve put together such a template built on top of io.Insights default metrics that you can import into your own Grafana instance and start visualising your io.Connect environment easily. It has a bunch of metrics, so it’s up to you to use all of them, trim or combine them in several dashboards.

Resources:

Grafana_Demo_Dashboard_Import_Ready_final.json - This is the JSON file of the dashboard which is used when importing a dashboard in Grafana.

Grafana Demo Platform Observability Dashboard.pdf - This is a PDF export file of the dashboard, you can see it before importing.

Before you start

The dashboard pulls metrics from three data sources - Prometheus, Loki, and Tempo. Before importing anything, you need to make sure these are configured in your Grafana instance under Connections → Data sources.

The important thing here is the name. Each datasource must be named exactly as follows in order for the dashboard to load the data.

  • prometheus - for all metrics and KPI panels

  • loki - for the logs panel (optional)

  • tempo - for the distributed traces panel (optional)

If you already have these data sources set up under a different name, simply click into each one and rename it. The URL and authentication settings don’t need to change - just the display name.

Importing the dashboard

Once your data sources are in order, the actual import takes under a minute:

  1. In Grafana, navigate to Dashboards → Import

  2. Click Upload dashboard JSON file and select the file you received

  3. Click Load, review the dashboard name and destination folder, then hit Import

That’s it. The dashboard will open with all panels live.

Something not loading?

If panels are showing “No data”, here are the two most common culprits:

  • Datasource name mismatch - names are case-sensitive, so Prometheus and prometheus are treated as different data sources. Double-check the names match exactly.

  • Missing labels - the filter dropdowns rely on specific Prometheus labels (user, machine, application, platformVersion, layout) being present in your metrics. If your scrape config doesn’t emit these labels, the dropdowns will be empty and panels won’t return data.

If everything looks correct but panels are still empty, check that your Prometheus scrape interval falls within the time range selected on the dashboard.