ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #grafana
Data Processing Trade-offs When managing high-cardinality time-series data in Grafana (v10+), there is an architectural choice between performing complex calculations directly via SQL queries or using the built-in Transformations tab to process result sets after the query returns. Executing logic via SQL pushes the computational load to the database engine,
Grafana Alerting routes notifications through a Prometheus-compatible Alertmanager that groups alerts by shared labels before delivery. The Group Wait interval buffers alerts of the same group before the first notification, while Group Interval and Repeat Interval control subsequent sends. When multiple silence rules overlap a group, the intended behavior is
Validating integrations without production secrets Teams need to confirm that a Grafana data source integration works before promoting it to production, ideally without using production credentials. The built-in Save & test button runs a lightweight health check against the configured endpoint, but its depth varies by plugin. Where the green check can mi
Cache Key Composition and Fragmentation Grafana's query cache stores responses keyed by query text, time range, and template variables. With a default 10-second TTL and 10 MB per-data-source limit, high-cardinality labels like request_id or session_id generate numerous unique cache entries, causing fragmentation. Eviction Policy Limitations The LRU eviction
When configuring a Stat panel in Grafana to display the most recent metric value, there is a choice between utilizing an Instant query or a Range query with a specific calculation applied. Instant queries are designed to return the latest value for each series at a specific timestamp, which minimizes the data payload sent to the browser. Conversely, Range qu
I'm planning a migration of a small Grafana instance (single node, Grafana 10.x assumed) to a new back-end data source endpoint, and the goal is to keep all dashboards queryable throughout the switch with no restart and no visible gap for viewers. Two documented approaches seem viable, and I'm unsure which fits this constraint better. File-based provisioning
Migrating a small application’s monitoring to a config-driven Grafana setup using file provisioning for datasources and dashboards. The goal is a cutover with no visible interruption to viewers and preserved access. Provisioning of dashboards and datasources is documented for config-driven installs. The operational uncertainty is the ordering and atomicity b
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
When configuring a Loki-based alert rule in Grafana, the max_lines parameter limits the number of log lines returned for evaluation. The goal is to determine which subset of lines is kept when the actual result set exceeds this limit, as this decides whether critical error messages are included in the alert condition. The truncation strategy—whether Grafana
prometheus