Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/platform/security-and-account-management/account-management/cloud-stacks/grafana-dbcfg-app.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/platform/security-and-account-management/account-management/cloud-stacks/grafana-dbcfg-app/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Note
Self-serve configuration is not available for free tier or Bring Your Own Cloud (BYOC) customers.
Database configuration
The Database configuration app is a single place in Grafana Cloud where you can self-serve manage settings for the databases behind your stack, instead of opening a support ticket for every change.
Access the Database configuration app
You need the Admin role on the stack to access the app.
To open the Database configuration app:
- In your Grafana Cloud stack, in the main menu, expand Administration.
- Select Database configurations.
The landing page shows a card for each database technology behind your stack:
- Logs (Loki) - available today. Select Configure to manage log ingestion limits such as retention, OTLP label mappings, and line truncation. Refer to Configure Loki settings.
- Traces (Tempo) - manage the Tempo metrics generator, which produces span metrics and service graph metrics from your traces. Refer to Configure Tempo traces metrics.
- Metrics (Mimir) and Profiles (Pyroscope) - shown as Coming soon. These aren’t configurable through the app yet.
How configuration changes are handled
Each database’s configuration page works a little differently, so check the specific topic for details before you make a change:
- Logs (Loki) uses a change-request model. When you submit a change, our engineering team manually reviews it before it takes effect - this can take up to two business days. The current configuration shows a
pending,applied, orrejectedstatus while your request is reviewed. Refer to Configure Loki settings for details. - Traces (Tempo) uses a direct-save model. When you save a change, it applies to your live configuration immediately, and a badge shows whether the change has finished rolling out (
Reconciling new configurationorReconciled). There’s no manual review step. Refer to Configure Tempo traces metrics for details.
Next steps
Was this page helpful?
Related resources from Grafana Labs


