scaleway · nerda-codes · Feb 6, 2025 · Feb 3, 2025 · Feb 6, 2025 · Feb 6, 2025
diff --git a/menu/navigation.json b/menu/navigation.json
@@ -3643,6 +3643,10 @@
               },
               {
                 "items": [
+                  {
+                    "label": "Fixing Grafana data synchronization issues",
+                    "slug": "synchronize-grafana-data-sources"
+                  },
                   {
                     "label": "Resetting a Grafana password",
                     "slug": "resetting-grafana-password-via-the-api"

@@ -6,7 +6,7 @@ meta:
   paragraph: Reset your Grafana user password using the Scaleway API. Retrieve your Grafana user ID and reset the password with a simple curl command.
 tags: grafana password credentials
 dates:
-  validation: 2024-12-26
+  validation: 2025-02-03
   posted: 2023-04-03
 categories:
   - observability
@@ -18,7 +18,6 @@ This page shows you how to reset your Grafana user's password through the Scalew
 
   - A Scaleway account logged into the [console](https://console.scaleway.com)
   - [Created](/iam/how-to/create-api-keys/) an API key with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page
-  - [Installed](https://curl.se/download.html) curl
 
 
 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays.

@@ -0,0 +1,49 @@
+---
+meta:
+  title: Fixing Grafana data synchronization issues
+  description: Fix Grafana data synchronization issues and ensure data appears on Cockpit dashboards with this troubleshooting guide.
+  h1: Fixing Grafana data synchronization issues
+  paragraph: Fix Grafana data synchronization issues and ensure data appears on Cockpit dashboards with this troubleshooting guide.
+tags: grafana data-sources synchronization sync
+dates:
+  validation: 2025-02-06
+  posted: 2025-02-06
+categories:
+  - observability
+---
+
+This page shows you how to resolve synchronization problems using the `SyncGrafanaDataSources` [endpoint](https://www.scaleway.com/en/developers/api/cockpit/v1/global-api/#path-grafana-synchronize-grafana-data-sources) of the [Cockpit Global API](https://www.scaleway.com/en/developers/api/cockpit/v1/global-api/#path-grafana-synchronize-grafana-data-sources).
+
+<Message type="important">
+ The [Cockpit Global API](https://www.scaleway.com/en/developers/api/cockpit/v1/global-api/#path-grafana-synchronize-grafana-data-sources) contains deprecated information that is being updated, you should  not use it for nay other purpose than the one described on this page.
+</Message>
+
+<Macro id="requirements" />
+
+  - A Scaleway account logged into the [console](https://console.scaleway.com)
+  - [Created](/iam/how-to/create-api-keys/) an API key with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page
+  - [Installed](https://curl.se/download.html) curl
+
+
+## Problem
+
+Many Cockpit users often encounter issues with Grafana data sources not synchronizing properly, leading to missing data on dashboards when data should be available.
+
+When users open their Grafana dashboards, they see a `No data` message along with an error banner stating: `Failed to upgrade legacy queries datasource was not found`.
+
+<Lightbox src="scaleway_cpt_grafana_datasources_troubleshooting.webp" alt="Grafana dashboard showing error messages and warning signs of no data found for the user's datasources" />
+
+This error banner only appears for users who have previously created data but can no longer see it on their dashboards. Users who have never created data do not see this banner.
+
+
+## Solution
+
+Open a terminal and run the following command to trigger the synchronization of your data sources:
+    ```bash
+    curl -X POST \
+    -H "X-Auth-Token: $SCW_SECRET_KEY" \
+    -H "Content-Type: application/json" \
+    -d '{"project_id":"$SCALEWAY_PROJECT_ID"}' \
+    "https://api.scaleway.com/cockpit/v1/grafana/sync-data-sources"
+
+Make sure that you replace `$SCW_SECRET_KEY` with your API secret key and `$SCALEWAY_PROJECT_ID` with the ID of the Scaleway Project affected by the issue.