Articles

Fix Grafana "Dashboard Not Found" After Import or Rename (2026)

April 18, 2026 5 min read

Grafana is failing to load dashboards because the underlying data source configuration for the dashboard has become corrupted or is missing, preventing Grafana from querying the metadata it needs to render the dashboard.

Common Causes and Fixes

  1. Data Source Name Mismatch: The most frequent culprit is a mismatch between the data source name referenced in the imported/renamed dashboard’s JSON and the actual data source name configured in Grafana.

    • Diagnosis:

      1. Go to "Configuration" > "Data Sources".
      2. Note the exact names of your data sources.
      3. Export the problematic dashboard JSON (click the dashboard settings cog, then "JSON model").
      4. Search within the JSON for "datasource": "YourDataSourceName" or "datasource": null (if it’s pointing to "Global").
      5. Compare this name against your actual data source names.

    • Fix:

      1. In the dashboard JSON, find all instances of "datasource": "OldDataSourceName" or "datasource": null and replace "OldDataSourceName" with the exact name of your intended data source (e.g., "datasource": "Prometheus"). If the dashboard was intended to use the default "Global" data source, ensure it’s explicitly set to "datasource": "-".
      2. Alternatively, if you are editing a dashboard that is already in Grafana, you can go to the dashboard settings, click on "General," and under "Data source," select the correct data source from the dropdown.
      3. Save the dashboard.

    • Why it works: Grafana uses the datasource field in the dashboard’s JSON model to know which data source to query for panels. If this name is incorrect or points to a non-existent data source, Grafana can’t fetch the panel data, leading to a "Dashboard Not Found" or broken panel error.

  2. Corrupted Data Source Configuration: The data source itself might be misconfigured or have stale credentials, even if the name matches.

    • Diagnosis:

      1. Navigate to "Configuration" > "Data Sources".
      2. Click on the data source that your dashboard is supposed to use.
      3. Click the "Save & Test" button.

    • Fix:

      1. If "Save & Test" fails, review the data source settings (URL, authentication, etc.) and correct any errors.
      2. If it passes, still try re-saving the data source configuration. Sometimes just re-applying the settings clears up internal inconsistencies.
      3. Ensure the data source is enabled and not paused.

    • Why it works: A broken data source means Grafana cannot communicate with the backend system (like Prometheus, InfluxDB, etc.) to retrieve metrics, making the dashboard panels fail to render.

  3. UID Collision After Import: If you import a dashboard that has the same UID as an existing dashboard, Grafana might create a duplicate with a slightly modified UID, or the import process might fail silently, leaving the dashboard in an unrenderable state.

    • Diagnosis:

      1. Go to "Dashboards" > "Browse".
      2. Look for duplicate dashboard names or dashboards with similar-looking titles.
      3. Check the URL of the broken dashboard. If it contains a long alphanumeric string (the UID), compare it to the UIDs of other dashboards.
      4. Manually check the JSON model for the suspected duplicate dashboards to see if their UIDs match.

    • Fix:

      1. Delete the older or duplicate dashboard that shares the UID.
      2. Re-import the dashboard. Grafana will assign a new, unique UID.
      3. Alternatively, if you have administrator access, you can use the Grafana API to manually update the UID of the dashboard.

    • Why it works: Each dashboard in Grafana has a unique identifier (UID). If two dashboards share the same UID, Grafana gets confused about which one to load or update, especially after import operations.

  4. Permissions Issues: The user trying to view the dashboard or the Grafana service account itself might not have the necessary permissions to access the data source or the dashboard folder.

    • Diagnosis:

      1. Check the "Permissions" tab for the dashboard folder.
      2. Check the "Permissions" tab for the specific data source.
      3. If you are using Grafana Cloud or a multi-tenant setup, ensure the organizational permissions are correct.
      4. Check Grafana’s server logs (/var/log/grafana/grafana.log or similar) for permission denied errors.

    • Fix:

      1. Grant the appropriate roles (e.g., "Viewer," "Editor") to the user or team for the dashboard folder.
      2. Ensure the data source has permissions set for the relevant organization/users.
      3. If the Grafana service account is restricted, ensure it has read access to the data source.

    • Why it works: Grafana enforces access control. If a user or the system lacks the required permissions, it will prevent access to resources, including dashboards and their underlying data sources.

  5. Browser Cache or Stale Session: Sometimes, the browser holds onto old information, preventing the new dashboard configuration from loading correctly.

    • Diagnosis:

      1. Try accessing the dashboard in an incognito/private browsing window.
      2. Try accessing the dashboard from a different browser.
      3. Check if other dashboards are loading correctly.

    • Fix:

      1. Clear your browser’s cache and cookies for the Grafana domain.
      2. Log out of Grafana and log back in.
      3. Restart the Grafana server process.

    • Why it works: A corrupted cache or an expired session can lead to Grafana serving outdated or incomplete dashboard metadata to your browser, causing rendering issues.

  6. Incorrect Dashboard JSON Structure or Missing Fields: The imported JSON might be malformed or missing critical fields required by the Grafana version you are running.

    • Diagnosis:

      1. Validate the imported JSON against a known good dashboard JSON from your Grafana version.
      2. Check the Grafana server logs for JSON parsing errors during import or dashboard loading.

    • Fix:

      1. Manually edit the JSON to correct syntax errors or add missing required fields (e.g., uid, version, title, panels).
      2. If the JSON was generated by an external tool, try regenerating it or using a different export source.
      3. Ensure you are using a JSON schema compatible with your Grafana version.

    • Why it works: Grafana expects a specific JSON structure to define dashboards. Any deviation can prevent it from correctly parsing and rendering the dashboard definition.

After fixing these issues, the next error you might encounter is a "Data source is not available" error if the data source itself is truly offline or misconfigured at the backend level, even if Grafana can reference it.

Want structured learning?

Take the full Grafana course →