no data points" in Grafana after datasource upgrade: what to check

TL;DR

"No data points" after an upgrade is usually a query or auth incompatibility, not data loss: the new datasource version sends queries differently, requires different auth, or changed default settings. Check the datasource's changelog for breaking changes first, then compare the actual query sent before and after. The data is fine; the question changed.

The query

"no data points" in Grafana after datasource upgrade: what to check

Use this when

• Dashboards break after a datasource plugin upgrade
• Queries work in the native UI but not Grafana
• Version incompatibilities are suspected
• After Grafana itself is upgraded

Not for when

• New datasource setup (different task)
• Actually missing data (verify in the native UI)
• Permission changes (different error usually)

Steps

Step 1: Verify the data exists natively

Query the backend directly (its own UI or API) for the same time range. If the data is there, the problem is the Grafana-to-backend path, not the data. Expected output: data confirmed present, isolating the issue to Grafana's query path.

Step 2: Check the upgrade changelog for breaking changes

Read the datasource plugin's changelog for the upgraded versions. Breaking changes to query format, auth, or defaults are documented; the fix is usually a config adjustment the changelog describes. Expected output: the breaking change identified, or the changelog cleared.

Step 3: Compare the queries sent before and after

Inspect the actual query Grafana now sends (query inspector) against what the old version sent. Differences in time macros, interval variables, or request format explain the empty results. Expected output: the query difference spotted.

Step 4: Re-save and re-test the datasource

Open the datasource config, verify all fields survived the upgrade (some upgrades drop or migrate settings), and use Save and Test. Re-authenticate if the auth model changed. Expected output: the datasource testing green with correct settings.

Step 5: Roll back the plugin if needed

If the new version is broken for your use case, pin the previous working version and report the issue. Upgrades should not be one-way doors during an incident. Expected output: working dashboards restored; the upgrade retried deliberately later.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vq4h-QwaBAq3XXUkW4YJtg