Grafana Cloud Unveils Adaptive Logs Drop Rules: Instantly Eliminate Noisy Log Lines
Breaking: Adaptive Logs Drop Rules Now in Public Preview
Grafana Cloud has launched a new feature that lets platform teams define custom rules to drop low-value logs before they are written to storage, slashing noise and costs immediately. The drop rules capability, part of the Adaptive Logs suite, is now available in public preview.
“For years, teams have struggled with logs that are clearly noise—health checks, debug output, or verbose INFO messages from rarely used services,” said a product manager at Grafana Labs. “With drop rules, they can finally eliminate that waste without cumbersome infrastructure changes.”
How Drop Rules Work
Drop rules enable users to create logic based on any combination of log labels, detected log levels, or line content. The rules are evaluated in priority order, and the first matching rule applies its drop rate—from 0% to 100%.
- Drop by level: Remove all DEBUG logs that consume your logging budget.
- Sample repetitive logs: Specify a drop percentage to keep only a representative sample of chatty, repetitive logs you don’t want to fully discard.
- Target specific producers: Use a label selector combined with log level or text string to drop high-volume, low-value logs from a particular service.
Background
Most observability and platform teams have long known that a significant portion of their log volume is noise. These logs—health check pings, forgotten debug statements, verbose INFO from low-traffic services—drive up costs without delivering value.
Until now, centralized teams had to navigate toilsome infrastructure change management to stop ingestion. There was no simple, self-service mechanism within Grafana Cloud to drop logs before they were written. The new drop rules fill that gap.
Part of a Complete Log Cost Management System
Drop rules are one of three mechanisms in Adaptive Logs. When a log line arrives, it is evaluated in this order:
- Exemptions: Protected logs pass through untouched—no sampling applied.
- Drop rules: Evaluated in priority order. The first matching rule applies its drop percentage.
- Patterns: Optimization recommendations (from Adaptive Logs) can be applied to remaining lines not exempted or filtered by drop rules.
“Drop rules, exemptions, and recommendations work together as a complete system,” the product manager explained. “Your platform team can enforce organization-wide standards—like dropping all health check logs—without any developer action.”
What This Means
For platform and observability teams, the new drop rules translate directly into reduced log volume and lower bills. A single rule can enforce a 100% drop rate for known noise that should never be stored.
Teams can also sample chatty workloads rather than discard them entirely. For example, a batch processing job generating repetitive output can be targeted with a stream selector and a 90% drop rate, keeping a representative sample for debugging while cutting costs.
“This is a game-changer for log cost management,” said an industry analyst following Grafana Labs. “It gives centralized teams the control they’ve been asking for—simple, immediate, and without requiring every developer to change their logging configuration.”
Adaptive Logs drop rules are now in public preview for all Grafana Cloud customers. For detailed instructions, refer to the official documentation.
Related Articles
- Beyond Ozempic: 9 Key Developments Shaping the Weight-Loss Drug Market Revolution
- 5 Critical Insights into the Shared Vulnerability of Polio and Common Cold Viruses
- Understanding PFAS in Baby Formula: Expert Answers to Parent Concerns
- Ozempic and Wegovy: Untapped Mental Health Benefits Revealed in Decade-Long Study
- How to Harness Heat Exposure to Reduce Alzheimer’s Risk: Lessons from Doug Whitney's Story
- PFAS in Baby Formula: FDA Findings Explained – A Q&A Guide
- From the Track to the Screen: Apple's Strategic Play in Formula 1 Racing
- How to Implement Single-Vesicle Profiling for Next-Generation Liquid Biopsies