Skip to content
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.

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

Resolve Grafana dashboard configuration datasource issue #442

Closed
3 tasks done
placek opened this issue Mar 11, 2024 · 4 comments · Fixed by #443
Closed
3 tasks done

Resolve Grafana dashboard configuration datasource issue #442

placek opened this issue Mar 11, 2024 · 4 comments · Fixed by #443
Assignees
Labels
🐛 Bug Something isn't working 🏗 Infrastructure

Comments

@placek
Copy link
Contributor

placek commented Mar 11, 2024

As a Grafana user,

I want to connect the panels on my dashboard with the correct datasource specified in the configuration

to avoid warnings about non-existing datasources.

Summary:

The Grafana dashboard is displaying warnings about non-existing datasources because the UIDs of the datasources in the configuration do not match the expected values. To resolve this issue, the configuration needs to be corrected to connect the panels with the appropriate datasource.

Acceptance criteria:

  • Identify the datasource with the correct UID in the configuration.
  • Update the datasource UID in the configuration to align with the expected value.
  • Test the dashboard to ensure that the warning about non-existing datasources is resolved.
@placek placek self-assigned this Mar 11, 2024
@placek placek added 🏗 Infrastructure 🐛 Bug Something isn't working labels Mar 11, 2024
@placek
Copy link
Contributor Author

placek commented Mar 11, 2024

Unblocks #427.

placek added a commit that referenced this issue Mar 11, 2024
This commit updates the datasource UID in the Grafana provisioning
configuration files to align it with the UID specified in the panel
configuration. By changing the UID in both the dashboard and the
datasource configuration files, consistency is maintained between the
two, ensuring proper functionality.

Changes:
- Updated UID for the Loki datasource in
  grafana-provisioning/dashboards/govtool.json to
  "a698987a-0cba-42a9-86aa-3ba65104ef72".
- Updated UID for the Loki datasource in
  grafana-provisioning/datasources/datasource.yml to
  "a698987a-0cba-42a9-86aa-3ba65104ef72".
placek added a commit that referenced this issue Mar 11, 2024
…configuration

Resolve the issue causing warnings about non-existing datasources in the
Grafana dashboard by ensuring that the UIDs in the datasource
definitions match the UIDs specified in the panel configurations. This
commit updates the UID values in the Grafana configuration files to
align them correctly and eliminate the warnings.

Changes:
- Update the UID value for the Loki datasource in the datasource.yml
  file to "a698987a-0cba-42a9-86aa-3ba65104ef72".
- Update the UID values for the Loki datasource in the govtool.json file
  to "a698987a-0cba-42a9-86aa-3ba65104ef72" to match the expected value.
placek added a commit that referenced this issue Mar 11, 2024
The basicAuth field was unnecessary and redundant under the datasources
section in datasource.yml. Removing this field ensures the configuration
to always parse and be loaded and establishes a cleaner and more concise
configuration file for datasource provisioning in Grafana.

Changes:
- Removed the basicAuth field that was previously present in the
  datasources section of datasource.yml. This field was not needed and
  did not serve any functional purpose. This removal simplifies the
  configuration file and eliminates redundancy.
placek added a commit that referenced this issue Mar 12, 2024
…hboard-configuration-datasource-issue

[#442] Resolve grafana dashboard configuration datasource issue
@pmbinapps
Copy link

Related to:
#427

No break on test-sancho - Read for Stage.

@bosko-m
Copy link
Contributor

bosko-m commented May 22, 2024

@MSzalowski Is this really blocked or it should go to In Staging status?

@MSzalowski
Copy link
Contributor

Not blocked anymore, moving to staging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working 🏗 Infrastructure
Projects
Status: In staging
Development

Successfully merging a pull request may close this issue.

4 participants