Skip to main content

LogDNA Introduces Variable Retention

LogDNA announced early access for Variable Retention.

This new capability allows companies to better control spend by storing different types or sources of logs for different lengths of time.

Modern infrastructure and applications generate massive amounts of data—sometimes petabytes worth of log data in a single day. Many teams need access to this data to gain critical insights into their services, but logging can get expensive, fast, and companies are forced to make difficult trade-offs that reduce observability and heighten risk. As a result, teams may not have the granular log data needed to form a complete picture during an incident or troubleshooting workflow. Variable Retention gives users the flexibility to save logs within the platform only for the amount of time that they're relevant, ensuring teams get access to the data they need, when they need it, while keeping costs in check.

“Different organizational and business functions need varying amounts and periods of data, but cost concerns drive sacrifices on what to keep and force dollar-driven decisions that diminish the value of all that data,” said Tucker Callaway, CEO, LogDNA. “Variable Retention gives LogDNA users control, removing friction that impacts how autonomous teams use log and other machine data to be more efficient and secure. Now, teams don’t have to choose between a reasonable logging bill and comprehensive observability data.”

Within the LogDNA user interface, customers select a subset of logs to store for different retention periods based on their needs—for instance, 30 days for security logs but only seven days for quality assurance and testing logs. When these rules are in place, users can monitor how their logging volume is distributed across different tiers in their usage dashboard to ensure the appropriate logs are being put in their respective retention tiers.

This new capability is one of many built by LogDNA to give users more control over how teams can route and store their log data. Earlier this year, the company released Spike Protection to give organizations more control over fluctuations of log data. And the recently announced LogDNA Streaming enables enterprises to ingest all of their log data to a single platform, and then route it for any enterprise use case.

Available retention tiers are three days, seven days, 14 days, and 30 days. LogDNA customers on an enterprise plan can sign up for the private beta program.

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

LogDNA Introduces Variable Retention

LogDNA announced early access for Variable Retention.

This new capability allows companies to better control spend by storing different types or sources of logs for different lengths of time.

Modern infrastructure and applications generate massive amounts of data—sometimes petabytes worth of log data in a single day. Many teams need access to this data to gain critical insights into their services, but logging can get expensive, fast, and companies are forced to make difficult trade-offs that reduce observability and heighten risk. As a result, teams may not have the granular log data needed to form a complete picture during an incident or troubleshooting workflow. Variable Retention gives users the flexibility to save logs within the platform only for the amount of time that they're relevant, ensuring teams get access to the data they need, when they need it, while keeping costs in check.

“Different organizational and business functions need varying amounts and periods of data, but cost concerns drive sacrifices on what to keep and force dollar-driven decisions that diminish the value of all that data,” said Tucker Callaway, CEO, LogDNA. “Variable Retention gives LogDNA users control, removing friction that impacts how autonomous teams use log and other machine data to be more efficient and secure. Now, teams don’t have to choose between a reasonable logging bill and comprehensive observability data.”

Within the LogDNA user interface, customers select a subset of logs to store for different retention periods based on their needs—for instance, 30 days for security logs but only seven days for quality assurance and testing logs. When these rules are in place, users can monitor how their logging volume is distributed across different tiers in their usage dashboard to ensure the appropriate logs are being put in their respective retention tiers.

This new capability is one of many built by LogDNA to give users more control over how teams can route and store their log data. Earlier this year, the company released Spike Protection to give organizations more control over fluctuations of log data. And the recently announced LogDNA Streaming enables enterprises to ingest all of their log data to a single platform, and then route it for any enterprise use case.

Available retention tiers are three days, seven days, 14 days, and 30 days. LogDNA customers on an enterprise plan can sign up for the private beta program.

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...