Operations | Monitoring | ITSM | DevOps | Cloud

How we use Insights to improve the agent behind Insights

Improving an AI agent means knowing which behaviors to change and where those changes will have the greatest impact. Insights in Datadog Agent Observability improves AI agents by analyzing agent traces to identify recurring cost and reliability problems. It then explains the causes of those problems, assesses their impact, and recommends fixes backed by evidence. At Datadog, we use Insights to improve the agent behind Insights.

Datadog Summit San Francisco, Workflows, Kafka Console, and more | This Month in Datadog

October’s This Month in Datadog comes to you from the Datadog Summit in San Francisco, where Jeremy shares a look inside the event, with our latest product updates. Plus, we cover how to: Build and manage Datadog Workflows using natural language, turning descriptions of automation tasks into workflows that teams can review before publishing Detect and investigate Kafka issues with Kafka Console, bringing health and performance data into one place Turn raw logs into structured fields with Datadog Tap, making logs easier to search and analyze.

Detect when your AI agent copies a self-replicating prompt injection

In September 2026, OpenAI reported finding self-replicating prompt injections. These attacks hide instructions in content an AI agent retrieves, directing it to take unauthorized actions and copy those instructions into emails, files, or messages. Copied instructions can then expose other agents or later sessions to the same attack, giving it the potential to spread like a computer worm.

Datadog named a Leader in the Forrester Wave: AIOps Platforms, Q4 2026

Datadog has been named a Leader in The Forrester Wave: AIOps Platforms, Q4 2026. We believe this placement reflects Datadog’s commitment to transforming observability into autonomous operations with a single integrated platform where AI agents detect, investigate, and remediate production issues, while engineers stay in control. Close dialog.

Trace voice agents with Datadog Agent Observability

A voice agent can return the right words and still deliver a poor experience. It might leave a caller in silence, speak over them, or stop midway through a response. A transcript may look correct even when the audio the user heard was delayed, incomplete, or different from the text on screen. These problems are difficult to diagnose from text traces alone. Voice conversations also involve more than a single request and response.

Default to serverless for AI agents, then let production data decide what moves

Serverless should be the first execution model teams evaluate for AI agent workloads. Many agents spend much of their lifetime waiting, and always-on compute forces teams to pay for every idle minute. In a study of more than 35,000 production coding-agent sessions, the median session ran LLM or tool calls for only 20% of its lifetime. The rest of the time, it sat idle between steps, with its sandbox still allocated.

Measuring What Matters in AI Applications

AI has become incredibly sophisticated and changed the way we build and power applications. But it has also introduced volatile complexity that challenges how we ensure reliability and protect user experiences. Join our panel of experts as they discuss the realities of building AI-powered applications. They’ll talk about how testing has evolved, share insights into how they do evals and experiments, and offer advice on how to get better visibility into how your AI is performing.

The Deconstructed Database at Datadog

As Datadog scaled to handle over a hundred trillion daily events, our engineering teams built their own custom query engines to keep things fast. While this helped teams move quickly, it also created silos that made it tough to analyze data across different products. To keep growing and support AI, we had to find a way to bring these engines together using open standards without slowing anyone down or risking reliability.

Match monitoring depth to workload needs with Infrastructure Basic

A back-office server that runs out of disk space can interrupt an important internal workflow. A process that stops on a staging host can delay development. Although workloads like these might not require application-level instrumentation, teams still need to know when the hosts that support them require attention. Without a monitoring solution tailored to these requirements, teams have to apply more monitoring than the workload needs, maintain a separate tool, or accept a gap in visibility.

Best practices for scaling A/B testing with experiment protocols

Running one A/B test well is manageable. Scaling A/B testing to hundreds of experiments across dozens of teams is harder, because teams may make different decisions about metrics, randomization, rollout, and analysis. Experiment protocols in Datadog Experiments turn an approved methodology into a reusable configuration, giving experiments of the same type a consistent starting point. In this post, you’ll learn how to.

Monitor Oracle AI Database across clouds with Datadog

Organizations can use Oracle AI Database@AWS, Oracle AI Database@Azure, and Oracle AI Database@Google Cloud to run Oracle databases co-located with the cloud applications they support rather than managing the databases on premises. However, running applications in a cloud provider’s environment while hosting databases on Oracle Cloud Infrastructure (OCI) can lead to visibility gaps. When application performance degrades, identifying the source of the problem can be difficult.

Optimize AI costs with Agent Observability

AI agent costs accumulate along more dimensions than a model-call count. Spend is a product of both which models you call and how the agent is architected: how many turns the loop runs, how many tools it invokes, how much retrieved context it carries, and how much of that context is re-sent on every turn. Provider bills tell you how much you spent, but they’re keyed to API keys and models instead of the applications and workflow steps that generated the calls.

Automate Slack Support with Datadog Workflow Automation + Bits AI

Automate Slack support questions with Datadog Workflow Automation and Bits AI Agent Builder. Datadog Workflow Automation can now trigger directly from messages posted in Slack. In this quick demo, Yuta Yoshida, Product Manager at Datadog, shows how to build an automated support workflow that: → Detects new support questions in a Slack channel→ Sends questions to a custom agent built with Bits AI Agent Builder→ Replies directly in the Slack thread with an answer and relevant documentation.

Build better SLOs with RUM and synthetic SLIs

Well-designed service level objectives (SLOs) help you track the benchmarks your app needs to meet to deliver a successful user experience (UX). To track performance against these SLOs, many SRE teams are turning to real user monitoring (RUM) and synthetic monitoring for their service level indicators (SLIs), as these forms of data provide more direct measurements of UX than backend performance metrics.

Modal scales the next generation of AI with unified observability from Datadog

Modal is an AI infrastructure company rebuilding the cloud for AI, giving developers easy access to the compute needed to build and scale AI applications without managing the underlying complexity. Operating across more than 20 cloud providers and launching approximately 26 million containers daily, Modal relies on Datadog to unify observability across its infrastructure, applications, networking, and CI—helping its engineers detect 99% of incidents within five minutes, resolve 96% of issues before customer impact, and confidently scale one of the world’s most complex AI platforms.

Introducing Scout 1.0: A new SRE model powering Bits AI with frontier performance at a fraction of the cost

Today, we’re introducing Scout 1.0, Datadog’s first AI model specialized for investigating production issues. Scout powers Bits Investigation, our AI SRE. We trained Scout to reduce inference cost so that investigations are cheap enough to run an order of magnitude more often and earlier in an incident’s lifecycle. Key highlights include: Close dialog.

Monitor the performance of critical steps in user journeys with RUM operations

Frontend and mobile applications depend on technical steps that users expect to work in every user journey: loading search results, signing in, saving a payment method, or processing a payment. Datadog Real User Monitoring (RUM) captures detailed events about these interactions, including views, actions, resources, and errors. But examining those events individually does not always provide a direct answer to more fundamental questions: Did a critical application step work, and how long did it take?

How Kubernetes DRA can improve GPU utilization and cut costs

Organizations are spending more on GPUs as they move AI workloads into production, and improving GPU utilization is a key priority. But Kubernetes’s legacy device plugin model can limit those improvements because it constrains how workloads request and consume GPU resources. Teams must configure GPU partitioning before workloads are scheduled. Resource requests cannot distinguish GPUs by capability, and a workload can reserve an entire GPU while using only part of its capacity.

Dismantling Datadog's Monolith with Agentic AI - Developer Track

AI can write code, but how does it do with a large, organically built codebase with years of development? Datadog’s monolithic webapp had significant scale and support challenges, so we knew the time had come to break it up. But when the code has been written, revised and tweaked so many times (as we keep adding new features and capabilities), by so many teams, that becomes much harder.

How Datadog defines service criticality at scale

Datadog runs thousands of internal services and has been increasing global footprint year after year. For most of that growth, we treated services uniformly when making deployment and reliability decisions. At our current scale, that approach became expensive. A change destined for production rolls out to data centers sequentially, so deployment time grows with every data center we add.

Accelerating Resolution with Autonomous Incident Response v1

Incident response often spans a patchwork of tools, handoffs, and manual steps. An engineer gets paged, a team investigates the issue, the incident commander coordinates the response, SREs document decisions, and somebody (anybody!) writes the postmortem. Every handoff introduces more context switching, increasing the risk of critical information loss, and ultimately slowing resolution.

Building an AI Assistant That Actually Understands Your Incidents

When production breaks, the clues are everywhere but the story is scattered. RUM sessions, APM traces, metrics, and logs allow Datadog to tell you part of the story. What’s missing is your service ownership quirks, your team's conventions, or the three-year-old workaround buried in a comment that explains why a certain endpoint behaves the way it does.

Democratizing Incident Response with AI at Riot Games - SRE Track

Senior engineers are the pillars of SRE programs—not only do they have the leadership to manage incidents well, they also have the tribal knowledge to understand the technical causes of tricky issues. But when the know-how is confined to a few individuals, it greatly limits the effectiveness of your SRE team.

How Do You Review 10x the Code? You Don't - Developer Track

AI is generating code at 10x human speed, but we’re not shipping software 10x faster. Agents have a quality problem, and we still can’t trust their output without validation. Breaking the code review model didn’t help. So what would it take to autonomously ship code that’s actually trustworthy? Join us to explore what an agentic harness looks like when the SDLC is the harness, a validation system that spans intent, CI, staging, and production, with context flowing bidirectionally between all stages.

Datadog San Francisco Summit: Keynote

Datadog has always been driven by a broader vision of helping teams understand and operate complex systems. In this session, you'll hear from Michael Whetten, Senior Vice President of Product Management, and Cansu Berkem, Director of Product Management, as they share the latest updates across the Datadog product suite and discuss how that vision continues to shape the platform's evolution and support the next generation of AI-driven applications.

Unify data across Datadog BYOC with cross-cluster queries for teams and AI agents

Organizations may need to keep data in specific regions or infrastructure they control, whether because of data residency requirements, internal policies, or transfer costs. Datadog Bring Your Own Cloud (BYOC) extends the Datadog platform into those environments. Each BYOC deployment runs as a Kubernetes cluster with its own object storage, keeping data close to its source.

Define user actions on your web app with visual labeling in Product Analytics

Adding or renaming a product event has traditionally meant creating an engineering ticket. Datadog Product Analytics uses the same SDKs and configuration as Real User Monitoring (RUM), and those SDKs autocapture actions such as clicks and taps. But an automatically generated action name describes the element rather than the user intent behind it.

Run incident response in your FedRAMP High environment

Earlier this year, Datadog for Government achieved FedRAMP High certification, extending our GovCloud environment (US1-FED) to the federal government’s most sensitive civilian workloads. That certification now covers Datadog Incident Response, bringing paging, incident coordination, automation, and postmortem workflows into US1-FED. When a government system goes down, responders need to reach the right people, coordinate a fix, and keep stakeholders informed.

Ship faster, improve reliability, and control CI costs with Datadog CI/CD Optimization

AI-assisted development can increase the rate at which teams produce code, but teams only realize those velocity gains if CI can keep pace. More pull requests (PRs) mean more builds, tests, and pipeline executions. Slow jobs leave developers and coding agents waiting for feedback, flaky failures consume time in reruns and investigations, and unnecessary test execution increases runner demand as delivery volume grows.

Monitor Databricks with Datadog

Earlier in this series, we covered key metrics for monitoring performance in Databricks and discussed Databricks’ native resources for accessing those metrics and other key observability data, such as logs and data lineage. In this post, we’ll cover using the Databricks integration to bring that data into Datadog and monitor your Databricks analytics and AI/ML workloads alongside the rest of your end-to-end data pipelines and distributed infrastructure. We’ll show you how to.

Databricks' native monitoring resources

In the first part of this series, we cataloged key metrics for Databricks data engineering, analytics, and Model Serving workloads. In this post, we’ll discuss how to collect those metrics and other telemetry data from Databricks and Apache Spark, which powers Databricks under the hood. We’ll cover collecting and querying telemetry data via system tables, as well as the other primary sources of visibility into.

Monitor warehouse data quality beyond pipeline health

You get a Slack message from the VP of Sales: They have asked an AI agent connected to Snowflake for the past quarter’s revenue and the numbers look wrong. First, you verify the agent’s query and, when that looks fine, check the pipelines that populate the underlying table. All jobs completed, the data is recently refreshed. Then it’s time to check the logs for errors. Nothing.