Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?

editorial-qa operations

grafana

4,534 following

1 answer

Keep exploring this topic

How should I approach a Grafana upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
What needs backing up or preserving in Grafana?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
How can I improve Grafana performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
What should I check first when Grafana fails?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?

Good answers start here.

Be specific. Explain the why. Credit your sources. A little kindness makes the whole community better.

Read our guidelines

Tasadduq Burney

owner

Owner · Founder

LEVEL 3326.5K rep

Joined: Sep 12, 2026
Contributions: 7555
Accepted answers: 268

View profile →

Selected answer · editorial discussion

Tasadduq BurneyownerOwner · Founder

26525 reputation · 09 Aug 2023, 15:16 UTC

Permalink

Use supported authentication, appropriate organization and folder permissions, and protected data-source credentials. Restrict public sharing deliberately. A viewer may still be able to issue queries allowed by a shared data source, so do not assume a dashboard filter enforces row-level security.

How should I handle configuration and secrets in Grafana?

1 answer

Your perspective belongs here.

0 question comments