Grafana Cloud Launches Adaptive Logs Drop Rules to Eliminate Noisy Log Lines and Cut Costs
Breaking: Grafana Cloud Introduces Real-Time Log Drop Rules
Grafana Cloud has released a public preview of drop rules for its Adaptive Logs feature, allowing platform and observability teams to automatically discard low-value logs before they are ingested. The move promises immediate cost savings and reduced noise by letting users define custom rules based on log labels, levels, or content.
“This feature puts control back into the hands of platform teams,” said Jane Chen, Product Manager at Grafana Labs. “No more chasing down individual teams to change logging configurations or wrestling with infrastructure changes. You write one rule and it applies everywhere.”
How Drop Rules Work
With each drop rule, users create logic using any combination of log labels, detected log levels, or line content. Logs matching the rule are dropped before they are written to Grafana Cloud Logs, eliminating noise and reducing storage costs.
Key examples include:
- Drop logs by level: Instantly remove noisy DEBUG logs that consume the logging budget.
- Sample chatty, repetitive logs: Specify a drop percentage—say 90%—to keep a representative sample while discarding the rest.
- Target a specific noisy producer: Use label selectors combined with log level or text strings to catch a single service that suddenly emits high-volume, low-value logs.
The same capability—custom inputs to drop data—has been available for Adaptive Metrics and Adaptive Traces, and is now extended to logs.
Background: The Noise Problem
Most platform and observability teams contend with logs they know are noise: throwaway health checks, forgotten DEBUG statements, or verbose INFO lines from seldom-used services. These inflate cloud bills and distract from meaningful signals.
Centralized teams have long struggled to block these logs without complex infrastructure change management. “Until now, there wasn’t a simple way to drop them in Grafana Cloud,” said Chen. “Drop rules solve that.”
How Drop Rules Fit Into Adaptive Logs
Drop rules are one of three mechanisms Adaptive Logs uses to manage log volume. When a log line arrives in Grafana Cloud, it is evaluated in this order:
- Exemptions: Protected logs pass through untouched. If a log matches an exemption, no sampling is applied.
- Drop rules: Evaluated in priority order. The first matching rule applies its drop rate.
- Patterns: Optimization recommendations are applied to remaining logs not exempted or filtered.
This three-step system ensures that critical logs are preserved while known noise is eliminated and remaining volume is optimally sampled.
Drop Rules, Recommendations, and Exemptions: A Complete System
Each mechanism serves a distinct purpose:
- Drop rules eliminate known noise. A single rule with 100% drop rate enforces that health check logs never reach storage, without requiring individual teams to change configurations.
- Sampling via drop rules applies to specific workloads. A batch processing job generating repetitive logs can be targeted with a stream selector and a 90% drop rate, keeping only a representative sample.
- Exemptions ensure mission-critical logs are never dropped.
“This gives teams a complete toolkit to control log costs without sacrificing visibility,” added Chen.
What This Means for Observability Teams
The introduction of drop rules enables immediate cost reduction. By dropping low-value logs before ingestion, teams can lower their monthly cloud bill without touching application code or infrastructure.
Noise reduction also improves signal-to-noise ratio, making dashboards and alerts more actionable. Centralized platform teams no longer need to coordinate with dozens of service owners to adjust log levels—they can enforce standards centrally.
The feature is in public preview now. Grafana Cloud users can start creating drop rules via the documentation. Early adopters report up to 40% reduction in log volume from health checks alone.
“We’re already seeing teams free up budget for high-value observability data,” said Chen. “Drop rules are a game-changer for log cost management.”
— Breaking news desk, Grafana Cloud