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

Fixes and Problem Resolutions #2018

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

RenJiangZhou2163
Copy link

  1. Grafana Storage Mount and Volume Adjustment

    • Removed the ./log - analyser/grafana:/var/lib/grafana mount. Instead, a named volume grafana - storage:/var/log/grafana was added to store Grafana data. Leveraging Docker's named volume approach enhances isolation and data persistence.
    • Resolved Error:
      grafana-1  | GF_PATHS_DATA='/var/lib/grafana' is not writable.
      grafana-1  | You may have issues with file permissions, more information here: http://docs.grafana.org/installation/docker/#migrate-to-v51-or-later
      grafana-1  | mkdir: can't create directory '/var/lib/grafana/plugins': Permission denied
      
      The previous mount led to permission - related write issues in the /var/lib/grafana directory. By switching to a named volume, these permission problems are effectively resolved.
  2. Grafana Datasource Provisioning Mount Addition

    • Added the mount ./log - analyser/grafana - provisioning/datasources/:/etc/grafana/provisioning/datasources/. This enables the automatic loading of Grafana data source configurations during startup.
    • Resolved Error:
      Datasource xxx was not found
      
      Without this mount, Grafana was unable to locate the specified data source configurations. The new mount ensures that the necessary configurations are available and can be loaded properly.
  3. Loki Datasource isDefault Attribute Update

    • In the Loki datasource configuration, the isDefault attribute has been modified from true to false, meaning Loki is no longer set as the default datasource.
    • Resolved Error:
      Error: ✗ Datasource provisioning error: datasource.yaml config is invalid. Only one datasource per organization can be marked as default
      
      The previous setting where multiple data sources might have been marked as default (or conflicting default settings) caused the configuration to be invalid. Changing Loki's isDefault attribute to false resolves this conflict and ensures the validity of the datasource.yaml configuration.

Copy link
Member

@saghul saghul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM at a glance. Can someone else also PTAL? @aaronkvanmeerten maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants