Skip to content

cockpit(add): add clarification in troubleshooting #5795

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 13, 2025
Merged

cockpit(add): add clarification in troubleshooting #5795

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion pages/cockpit/troubleshooting/synchronize-grafana-data-sources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: No data showing up on Grafana dashboards
description: Fix Grafana data synchronization issues and ensure data appears on Cockpit dashboards with this troubleshooting guide.
tags: no-data-sources no-data cockpit-unavailable dashboard datasource-not-found missing-data cannot-view access-cockpit
dates:
validation: 2025-09-03
validation: 2025-11-13
posted: 2025-02-06
---
import Requirements from '@macros/iam/requirements.mdx'
Expand Down Expand Up @@ -42,6 +42,14 @@ This page shows you how to visualize your data again when it does not display on

These issues often occur due to synchronization failures between Cockpit and Grafana, preventing dashboards from displaying the latest logs and metrics as expected.

<Message type="tip">
Sometimes, what looks like a synchronization issue may simply be due to the asynchronous nature of the synchronization between Grafana and your data sources.
If you have logged into Grafana while the synchronization was still in progress, your data might not appear right away.

Try refreshing your browser page first. If the problem persists, the synchronization may have failed but you can trigger a new one manually using the procedure below.
</Message>


## Solution

### Using the Scaleway API
Expand Down