BlogsDatadogAI Agent Observability Interface (MCP)

AI Agent Observability Interface (MCP)

AI Agent Observability Interface (MCP)

2
posts
2024–2026

Datadog's MCP (Model Context Protocol) server has evolved significantly to provide an observability interface specifically designed for AI agents. Initial versions were simple API wrappers, but the system has been re-architected to address agent constraints like context window efficiency, data retrieval limitations, and tool management. Key developments include optimizing data formats (CSV, YAML over JSON), implementing token-budget-based pagination, introducing query languages (SQL) for data analysis, and enhancing the system to facilitate writing postmortems by integrating structured metadata from Datadog's Incident Management app with unstructured discussions from related Slack channels. This integration uses an ensemble of LLM models to generate postmortem first drafts, with a focus on limiting hallucinations, increasing accuracy, and generating output more quickly through refined LLM instructions and an experimentation framework. Safeguarding mechanisms include prioritizing information based on context, lowering model temperature, and adjusting LLM parameters. An adjacent project for LLM-generated incident summaries also informed this work.

2026

Designing MCP tools for agents: Lessons from building Datadog’s MCP server | Datadog

3/4/2026

This post details the evolution of Datadog's MCP (Model Context Protocol) server, an observability interface for AI agents. It highlights key technical challenges and solutions: 1. Context Efficiency: Optimized data formats (CSV, YAML) and trimmed fields to reduce token usage by up to 5x. Introduced token-budget-based pagination instead of record-count pagination. 2. Querying Capabilities: Enabled agents to query data using SQL, allowing for efficient aggregation and filtering, reducing token usage and costs. 3. Tool Management: Strategies to manage tool count include flexible tools serving multiple use cases, opt-in toolsets for specialized needs, and layering for chaining tool calls. 4. Agent Guidance: Improved error messages for actionable feedback and integrated a `search_datadog_docs` tool for discoverable documentation. Tool results can now include contextual guidance.

2024

How we optimized LLM use for cost, quality, and safety to facilitate writing postmortems | Datadog

9/23/2024

This post details the optimization of LLM usage for writing postmortems, focusing on cost, quality, and safety. It describes the integration of structured metadata from Datadog's Incident Management app with unstructured Slack discussions, fed into an ensemble of LLM models to generate postmortem drafts. Key challenges addressed include data quality and hallucinations, cost/speed/quality trade-offs, and trust/privacy. Solutions involved refining LLM instructions with both structured and unstructured data, establishing an experimentation framework with a custom API for data extraction and structuring, and implementing safeguarding mechanisms like prioritizing information, lowering model temperature, and adjusting LLM parameters to reduce hallucinations and improve reliability. The post also mentions an adjacent project for LLM-generated incident summaries that informed this work.