LaunchDarkly unveiled key new AI capabilities and integrations that let developers ship software at even higher velocity while keeping risks at bay.
These updates further the company’s vision for Self-Healing Software that allows engineers to focus on delivering amazing user experiences instead of anxiously awaiting late-night calls to fix bugs and outages.
The new observability updates provide closed-loop automation for de-bugging and quality control that transform how companies approach software quality and reliability.
The updates include:
- Live view of feature performance: Adding session replay, error monitoring and APM data directly into the rollout surface gives developers a live view into how changes are performing without needing to wait on legacy alerts or hunt across APM dashboards. This closes the loop between code change and customer impact, dramatically reducing mean time to repair and building confidence to ship more often.
- Regression attribution to metrics: Guarded Releases connect the dots between what changed (your feature flag) and what broke (your metric). No more guesswork, blame-pong, or digging through dashboards at 2 a.m. When a metric regresses, LaunchDarkly shows you the exact flag change that caused it and lets you roll it back with one click.
- Session replay: provides full context into how a release impacts real users right down to clicks, rage-scrolls, and form abandons. You can finally pair telemetry data with human-readable truth. It's the fastest way to diagnose what actually happens when a release behaves badly, especially when the bug doesn’t trigger an alert.
- Upcoming AI-Powered Diagnostics: The upcoming Vega AI agent will help eliminate the traditional "needle in a haystack" debugging process. Vega analyzes logs, traces, metrics, and session replays to identify root causes, generate timelines of what broke and why, and surface recommended code changes—turning noisy production data into actionable insights.
“While iterating quickly on products is paramount, organizations are becoming terrified of their own speed — they can find themselves flying blind on how their software is performing as they ship,” said Jay Khatri, Head of Observability at LaunchDarkly. “One bad release during peak season can cost millions in revenue and customer trust, which is why we’re so focused on moving from reactive damage control to proactive confidence.”
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 ...