LogDNA today unveiled Spike Protection to give companies more control over fluctuations in their data and spend. With these new capabilities, development and operations teams have the freedom to rapidly deploy applications with guardrails in place to know if their ingestion spikes as a result.
In cloud-native and microservices environments, developers have an increasingly difficult time managing the spikes of log data, which often leads to surprise overage costs. Legacy vendors present storage as the solution, but this requires a substantial investment and often increases complexity, creating additional cycles for debugging. LogDNA Spike Protection gives DevOps teams the necessary tools to understand and manage increases through Index Rate Alerting and Usage Quotas. This provides additional insight into anomalous data spikes, making it faster to pinpoint the root cause so that admins can choose to store or exclude contributing logs.
The LogDNA platform also delivers robust capabilities to help developers manage the increasing complexity in their cloud-native and microservices environments. In addition to Spike Protection, LogDNA today announced the release of its Agent 3.2 for Kubernetes and OpenShift, which introduces the configuration of log inclusion/exclusion rules, along with log redaction, using regex patterns. These enhancements give developers more control over what data leaves their system, and what data is ingested by LogDNA. Powerful Exclusion Rules let developers manage log volume by storing what’s important and excluding what’s not. Automatic Archiving lets LogDNA users forward logs to an AWS S3 bucket or any other object storage for compliance or later review. Role-Based Access Control lets teams limit access to sensitive logs and potentially destructive actions.