This product is not supported for your selected
Datadog site. (
).
Preview
Agent Console is available to all Datadog customers in Preview.
To set up Agent Console, connect the AI tools you want to monitor, optionally connect productivity tools, and map user identities across tools. The Setup page in Agent Console Settings tracks your progress through each step.
Permissions
Agent Console access is controlled by the following role permissions. Assign them to roles in Organization Settings > Roles.
| Permission | Description |
|---|
agent_console_read | View Agent Console, including Overview, My Usage, Usage, and Settings. Users without this permission can’t open Agent Console. |
agent_console_write | Change Agent Console configuration, such as identity mapping and integration setup. |
Select the AI tools to connect from the Set up your AI tools page, which appears the first time you open Agent Console. Connect at least one tool to start seeing data. You can add more tools later.
Anthropic products
To monitor Claude Code, Claude Chat, Claude Cowork, and Claude Design, set up the Anthropic Usage and Costs integration. The integration collects daily spend and user analytics for each Claude product.
The Anthropic Usage and Costs integration doesn’t support Claude Team plans. If your organization uses a Team plan, send Claude Code telemetry to Datadog with OpenTelemetry instead.
Claude Code with OpenTelemetry
Use OpenTelemetry (OTLP) to send Claude Code telemetry directly to Datadog. Data collected this way appears on the Claude Code (OTel) card in Agent Console.
To set up Agent Console for Claude Code across your organization, your IT team can use a Mobile Device Management (MDM) system or server-managed settings to distribute the Claude Code settings file across all managed devices.
Make sure that your Logs configuration includes a catch-all index, or an index that covers service:claude-code.
Generate a Datadog API key.
Set the following environment variables in your Claude Code settings file (for example, ~/.claude/settings.json):
{
"env": {
"CLAUDE_CODE_ENABLE_TELEMETRY": "1",
"OTEL_LOGS_EXPORTER": "otlp",
"OTEL_EXPORTER_OTLP_LOGS_PROTOCOL": "http/protobuf",
"OTEL_EXPORTER_OTLP_LOGS_ENDPOINT": "<span class="js-region-param region-param" data-region-param="otlp_logs_endpoint"></span>",
"OTEL_METRICS_EXPORTER": "otlp",
"OTEL_EXPORTER_OTLP_METRICS_PROTOCOL": "http/protobuf",
"OTEL_EXPORTER_OTLP_METRICS_ENDPOINT": "<span class="js-region-param region-param" data-region-param="otlp_metrics_endpoint"></span>",
"OTEL_EXPORTER_OTLP_HEADERS": "dd-api-key=<DATADOG_API_KEY>"
}
}
Replace <DATADOG_API_KEY> with your Datadog API key.
Restart Claude Code.
- Make sure that your Logs configuration includes a catch-all index, or an index that covers
service:claude-code. - Install the Datadog Agent.
- Configure your Datadog Agent to enable the OpenTelemetry Collector:
otlp_config:
receiver:
protocols:
grpc:
endpoint: 0.0.0.0:4317
logs:
enabled: true
otelCollector:
enabled: true
- Set the following environment variables in your Claude Code settings file (for example,
~/.claude/settings.json):{
"env": {
"CLAUDE_CODE_ENABLE_TELEMETRY": "1",
"OTEL_METRICS_EXPORTER": "otlp",
"OTEL_LOGS_EXPORTER": "otlp",
"OTEL_EXPORTER_OTLP_ENDPOINT": "http://127.0.0.1:4317",
"OTEL_EXPORTER_OTLP_PROTOCOL": "grpc",
"OTEL_METRIC_EXPORT_INTERVAL": "10000"
}
}
- Restart Claude Code.
After you restart Claude Code, metrics (usage, cost, latency, errors) appear in Agent Console within a few minutes.
Codex
To monitor Codex, set up the OpenAI Codex integration. The integration collects daily usage, credits, code attribution, and review analytics.
ChatGPT Work
To monitor ChatGPT Work, set up the OpenAI integration. The integration collects activity, token, and estimated cost analytics.
Cursor
To monitor Cursor, set up the Cursor integration using the Datadog Extension for Cursor. The integration collects spend metrics and user analytics once a day.
GitHub Copilot
To monitor GitHub Copilot, set up the GitHub Copilot integration. The integration collects spend metrics and user analytics once a day.
Microsoft Copilot 365
Preview
Microsoft Copilot 365 support is in Preview. To request access, contact your Datadog account team.
The Microsoft Copilot integration collects daily Microsoft 365 Copilot adoption data and metadata-only interaction analytics.
Other coding and desktop agents with Trajectory
Trajectory is an open source tool that captures sessions from more than 30 coding and desktop agents, such as Claude Code, Claude Desktop, Codex CLI, Cursor, Cline, Windsurf, and Zed, and sends them to Datadog. For the full list and version requirements, see Supported Clients.
Trajectory session data powers the Tasks, Skills, Tools, and Sessions views in Agent Console.
Run the installer to install Trajectory for the current user:
bash <(curl -fsSL https://raw.githubusercontent.com/datadog-labs/trajectory/main/install.sh)
The installer downloads the latest Trajectory release for your platform, runs trajectory setup, and connects the coding agents it finds. When prompted, enter a Datadog API key to send data to Datadog.
To configure the Datadog destination later, run:
trajectory publish destination configure
To upgrade Trajectory, rerun the installer.
To deploy Trajectory to developer computers with an MDM or UEM product such as Jamf Pro or Microsoft Intune, follow the Managed Endpoint Administrator Guide. The guide covers package preparation, policy deployment, coding agent selection, and verification.
Request an integration
If the tool you want to monitor isn’t listed, click Request an Integration on the Set up your AI tools page.
Optionally, connect productivity tools so Agent Console can show merged pull requests, time to merge, cost per pull request, and resolved issues alongside AI spend.
- GitHub: Set up the GitHub integration to collect pull request data.
- Jira: Set up the Jira integration to collect issue data.
Map identities
Each AI tool identifies users differently, for example by email address, GitHub login, or Microsoft user principal name (UPN). Upload an identity mapping table so that usage and spend from every tool are attributed to the right person.
In Agent Console, go to Settings > Identity Mapping.
Prepare a CSV file with one row per person and the following columns:
| Column | Requirement |
|---|
email | Required |
github_login | Required if you use GitHub |
microsoft_upn | Optional |
jira_account_id | Optional |
datadog_handle | Optional |
Separate multiple email aliases, GitHub logins, or Jira account IDs with semicolons. The first email is the canonical email.
Choose any column with unique values, such as email, as the primary identifier. You can also add your own column for this purpose, such as an employee ID.
Upload the CSV file (maximum 10 MiB), preview the mapping, and save it.
Validate your data
After you connect your tools, open the Agent Console and check that each connected integration shows as active on the Overview tab. Most integrations collect data once a day, so data can take up to 24 hours to appear.
Further reading
Additional helpful documentation, links, and articles: