LogDNA introduced the Control API Suite, making it even easier for users to control their log data.
With four new APIs, teams can set up rules with their deployment workflows that will streamline how data is used throughout the organization.
As IT complexity grows, the volume of data generated across various sources — such as Kubernetes, cloud, and DevOps tools — surges at exponential rates. Companies are challenged to ingest, process, route, and store this data to maximize the value without skyrocketing costs. LogDNA’s new Control API Suite puts control over log data in the hands of its users, giving teams the ability to programmatically configure and execute key workflows across multiple teams in LogDNA. As a result, teams can operate more efficiently and maximize the value of their data, whether it’s from the command line or within the LogDNA UI.
“Observability data, especially log data, is immensely valuable for modern business. We feel it should be easy to control, but too often, we hear from customers that scale, complexity, the wide variety of data consumers, and runaway costs make it impossible for them to get value out of all of their machine data,” said Tucker Callaway, CEO, LogDNA. “These updates are yet another step toward putting control into the hands of LogDNA users, and delivering a comprehensive platform that enables anyone to ingest, process, route, analyze, and store all of their log data in a way that makes sense for them.”
The LogDNA Control and Usage API Suite includes:
- Exclusion Rules API & Terraform Support: Customers can now programmatically configure exclusion rules via the Terraform Provider to exclude certain logs from being saved by LogDNA’s underlying datastore. This helps control cost and filter out noise for more focused debugging and troubleshooting. The API endpoints can be called to create, update, read, and delete exclusion rules while the Terraform Provider now recognizes exclusion rules as a configurable resource.
- Start/Stop Ingestion API: When incidents happen, it creates a surge in log data over a short period of time, and this flood of logs in Live Tail can cause chaos, confusion, and cost overages. During these situations, developers can now start and stop the ingestion of all logs as needed, so that they can access the data necessary to debug the issue without battling an influx of duplicated logs.
- Usage API: Users can programmatically query for which services are creating the most logs and automatically monitor their usage to better understand how their logs change over time. This capability — in addition to existing data views that show ingestion by apps, sources and tags — provides a better understanding of broad log trends over time, pinpointing specific applications that are contributing to the highest volume of logs.
- Archiving API and Terraform Support: When logs reach the end of their retention period, LogDNA customers can set up archiving to a third-party storage provider like an Amazon S3 bucket or IBM Cloud Object Storage. This new API allows users to programmatically configure their archiving integrations as well as use Terraform to manage their archiving instances as resources.
The LogDNA Control API Suite builds on recent innovations to further strengthen the foundation that companies need to meet today’s critical scale, storage, and routing requirements. Recently added capabilities, including LogDNA Streaming and Variable Retention, capitalize on LogDNA’s unparalleled ability to quickly ingest massive amounts of structured and unstructured data, normalize it, and provide granular control over storage to control costs and meet compliance needs. With LogDNA, enterprise teams no longer have to make difficult choices about how to use all of their machine data while controlling skyrocketing costs. The comprehensive platform enables anyone to maximize the value of their observability data.
The Latest
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...