惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
The Last Watchdog
The Last Watchdog
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
T
Troy Hunt's Blog
L
LINUX DO - 最新话题
C
Check Point Blog
T
Threat Research - Cisco Blogs
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
罗磊的独立博客
V
Vulnerabilities – Threatpost
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
J
Java Code Geeks
Apple Machine Learning Research
Apple Machine Learning Research
大猫的无限游戏
大猫的无限游戏
S
Security @ Cisco Blogs
IT之家
IT之家
T
The Exploit Database - CXSecurity.com
The GitHub Blog
The GitHub Blog
D
Docker
Engineering at Meta
Engineering at Meta
AWS News Blog
AWS News Blog
S
Security Affairs
U
Unit 42
P
Palo Alto Networks Blog
V
Visual Studio Blog
Y
Y Combinator Blog
D
DataBreaches.Net
Forbes - Security
Forbes - Security
阮一峰的网络日志
阮一峰的网络日志
美团技术团队
Security Latest
Security Latest
aimingoo的专栏
aimingoo的专栏
Simon Willison's Weblog
Simon Willison's Weblog
A
Arctic Wolf
博客园_首页
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
H
Hacker News: Front Page
博客园 - 司徒正美
博客园 - Franky
宝玉的分享
宝玉的分享
TaoSecurity Blog
TaoSecurity Blog
Latest news
Latest news
Scott Helme
Scott Helme
MongoDB | Blog
MongoDB | Blog
量子位
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
C
Cisco Blogs
P
Privacy International News Feed
Application and Cybersecurity Blog
Application and Cybersecurity Blog

Datadog | The Monitor blog

Introducing our open source AI-native SAST Instrument and monitor Boomi integration flows with OpenTelemetry and Datadog Not all index scans are equal: How we cut query latency by over 99% Platform engineering metrics: What to measure and what to ignore Integrate Recorded Future threat intelligence with Datadog Cloud SIEM CI/CD security: threat modeling using a MITRE-style threat matrix CI/CD security: How to secure your GitHub ecosystem Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API Operating agentic AI with Amazon Bedrock AgentCore and Datadog LLM Observability: Lessons from NTT DATA Introducing the Datadog Code Security MCP Capture and analyze custom heatmaps in Session Replay Understand session replays faster with AI summaries and smart chapters Monitor ClickHouse query performance with Datadog Database Monitoring How we designed empathetic alert sounds for on-call engineers Search and act across Datadog to resolve issues faster with Bits Assistant Measure the business impact of every product change with Datadog Experiments Analyzing round trip query latency Configuring JavaScript caches for better performance Introducing Bits AI Dev Agent for Code Security Datadog achieves ISO 42001 certification for responsible AI Monitor Nutanix clusters, hosts, and VMs with Datadog Monitor Juniper Mist in Datadog A new Host Map for modern infrastructure Annotate traces to improve LLM quality with Datadog LLM Observability What’s new in Cloud SIEM: AI-powered investigations, enhanced threat intelligence, and scalable security operations Explore Kubernetes with native OpenTelemetry data Monitor Oracle Fusion Cloud Applications with Datadog Announcing the Datadog Terraform provider v4.0.0 Scaling Kubernetes workloads on custom metrics How to design cloud environments for AI-powered threat analysis Monitor Aruba Central in Datadog How we centralize and remediate risks with Datadog Case Management Accelerate incident response with Datadog and ServiceNow Monitor your application and network load balancer logs Understanding Karpenter architecture for Kubernetes autoscaling Tools for collecting metrics and logs from Karpenter Monitor Karpenter with Datadog What your product data is actually saying Key metrics for monitoring Karpenter Securing Datadog’s platform in the AI age: The role of observability data Four ways engineering teams use the Datadog MCP Server to power AI agents Approaching your observability migration with the right mindset Meet the new Bits AI SRE: Deeper reasoning, twice as fast Key learnings from the 2026 State of DevSecOps study Use plain English to query your multi-cloud infrastructure in Resource Catalog Simplifying troubleshooting across the user journey with Datadog Synthetic Monitoring Protect your OCI resources with Datadog Cloud Security This Month in Datadog - February 2026 Amazon EC2 security: How misconfigured and public AMIs expand your cloud attack surface Enable end-to-end visibility into your Java apps with a single command Measure and improve mobile app startup performance with Datadog RUM Evaluating our AI Guard application to improve quality and control cost Identify untested code across every level of your codebase Make use of guardrail metrics and stop babysitting your releases Monitor Versa Networks SD-WAN performance in Datadog Improve performance and reliability with APM Recommendations Remediate transitive vulnerabilities faster with Datadog Software Composition Analysis Generate audit-ready vulnerability and compliance reports with Datadog Sheets Monitor Fortinet FortiManager performance in Datadog Improve test coverage across codebases with Datadog Code Coverage Move fast, don’t break things: Consistent testing standards at scale Enrich logs with ServiceNow CMDB context before routing to any SIEM or logging tool Monitor Lustre with Datadog Make faster, better product decisions with Datadog Product Analytics Surface and remediate runtime posture issues with Workload Protection Findings Protect agentic AI applications with Datadog AI Guard How to optimize JavaScript code with CSS Trace Google Pub/Sub workloads in Cloud Run with Datadog Detect human names in logs with ML in Sensitive Data Scanner How we cut our NLQ agent debugging time from hours to minutes with LLM Observability Debug PostgreSQL query latency faster with EXPLAIN ANALYZE in Datadog Database Monitoring Datadog acquires Propolis Unify and correlate frontend and backend data with retention filters Scale compliance across global frameworks with Datadog Cloud Security Monitor Arista VeloCloud SD-WAN performance with Datadog Building reliable dashboard agents with Datadog LLM Observability Simplify log collection and aggregation for MSSPs with Datadog Observability Pipelines Mitigation for Node.js denial-of-service vulnerability affecting Datadog APM Automate flaky test fixes with the Bits AI Dev Agent and Test Optimization How we built an AI SRE agent that investigates like a team of engineers Datadog integrations 2025 recap: Observability for AI, security, and hybrid cloud Design effective executive dashboards with Datadog Implement dbt data quality checks with dbt-expectations Bring faster visibility into AWS Lambda functions with remote instrumentation Troubleshoot faster with the GitLab Source Code integration in Datadog How Cambia Health Solutions saved $30,000 monthly with Cloud Cost Management and the Datadog Resource Catalog Normalize any logs for Cloud SIEM with Datadog's OCSF processor Optimizing Datadog at scale: Cost-efficient observability at Zendesk Detect, diagnose, and resolve network issues easily with CNM Network Health Connect engineering errors to user impact in early-stage products Cilium configuration for Kubernetes operations at scale Designing feedback loops for progressive delivery Ship features faster and safer with Datadog Feature Flags Choosing the right OpenTelemetry Collector distribution Route your monitor alerts with Datadog monitor notification rules Automate Cloud SIEM investigations with Bits AI Security Analyst Cloud threat detection: How to identify risky activity across control and data planes Collecting Kafka performance metrics Monitoring Kafka with Datadog Monitoring Kafka performance metrics
Monitor Claude Code adoption in your organization with Datadog’s AI Agents Console
2025-12-01 · via Datadog | The Monitor blog
Ali Al-Rady

Ali Al-Rady

Shri Subramanian

Shri Subramanian

Will Potts

Will Potts

AI coding assistants are quickly becoming a core part of software engineering workflows, helping developers write, refactor, and review code faster. But without effective monitoring, it can be difficult to know whether these tools are performing reliably and proving useful to engineers. As organizations scale their use of tools like Claude Code, key questions emerge:

  • Who’s using these tools, and how much?
  • Are tools performing reliably?
  • What’s the estimated cost and return on investment (ROI)?

To help teams answer these questions, we’re excited to introduce Claude Code Monitoring within Datadog’s AI Agents Console, available now in Preview. The AI Agents Console provides a unified view of your organization’s AI agents and coding assistants, extending the same observability you already rely on for your applications and infrastructure. By monitoring Claude Code with the AI Agents Console, you can track usage and adoption across your organization, analyze performance and reliability trends, and understand total, user, and model-level spend and ROI all in one place.

In this post, we’ll explore how the AI Agents Console enables you to evaluate Claude Code performance in your environment and ensure adoption remains efficient, reliable, and cost-effective.

Get a real-time overview of Claude Code activity

As AI coding assistants become integral to development workflows, platform and engineering leaders need immediate insight into Claude Code usage, spend, and performance. Once your organization enables telemetry for Claude Code, you can view real-time telemetry from Claude Code sessions in the AI Agents Console. The Summary tab provides a high-level snapshot of Claude Code usage and performance across your organization. Here, you can quickly see:

  • Total spend and token usage across all users
  • User activity trends over time
  • Error rates and latency patterns to assess stability
  • Git commits and PRs associated with Claude Code activity
The Claude Code Overview shows real-time telemetry from Claude Code sessions in a consolidated view.

These metrics give platform and engineering leaders an instant understanding of adoption, stability, and cost in a unified view—you can use this view to spot anomalies at a glance for further investigation. For instance, you might identify elevated spend week-over-week without a correlated increase in user activity, indicating that new, expensive usage has occurred that you may need to audit.

Monitor Claude Code responsiveness and reliability

When AI coding assistants lag or return errors, developer productivity stalls. But identifying whether slow responses stem from model latency, network bottlenecks, misconfigurations, or rate limiting can be difficult without real-time visibility into agent performance metrics. The AI Agents Console aggregates key Claude Code performance metrics to surface latency percentiles, error rate trends, top failed bash commands, and success rates—and also surfaces requests by repository, giving you project-level insight into where issues are occurring and how different codebases are engaging with Claude Code.

Claude Code performance metrics in the AI Agents Console.

When you observe elevated error counts or latency from this view, you can immediately pivot to related logs for additional context and troubleshooting. Claude Code’s error logs can tell you more about the types of errors being thrown, helping you plan remediation. For example, the following screenshot shows a correlated 429 “Rate limit exceeded” error log. The user’s authentication and session metadata is included in this log so you can trace the issue further.

Correlated error log helping with Claude Code metrics investigation in the AI Agents Console.

Track Claude Code spend and measure ROI

AI-assisted development introduces new cost dynamics. Without clear attribution of spend by user or model, it’s nearly impossible to understand where your budget is going—or how much value these tools actually deliver. Teams need transparent cost and usage data to evaluate ROI and guide responsible AI adoption. The AI Agents Console’s “Cost & Value” tab helps you measure Claude Code’s financial impact and optimize your usage. You can use this tab to view estimated total and per-user spend, model-specific cost trends (such as Sonnet vs. Opus vs. Haiku), and cumulative cost trends over time—all alongside performance metrics.

Claude Code cost metrics in the AI Agents Console.

These insights make it easier to ensure AI adoption remains aligned with organizational budgets and priorities. For instance, your team might notice that usage of the Claude Code Opus model has grown three times faster than Haiku over the past month, even though most requests don’t require the higher-priced model. With this insight, you adjust the default configuration for routine code reviews to use Haiku, reserving Opus only for complex refactoring tasks. This reduces costs without affecting developer experience.

Understand how teams are engaging with Claude Code

Platform and engineering leaders need engagement data to ensure the consistent, effective use of coding assistants across their organizations. Without insight into usage trends, session durations, and code change activity, it’s hard to tell whether these assistants are truly improving development velocity or just sitting idle. The “Usage & Adoption” section highlights how Claude Code is being used day-to-day across your organization. You can track active users, sessions, and lines of code changed, along with commits and pull requests linked to Claude Code activity. The console also shows session duration, top users and common commands, and sessions by repository, helping you understand how developers are engaging across projects.

Claude Code usage metrics in the AI Agents Console.

Additionally, the console surfaces client details—including the editors, CLIs, versions, and platforms where Claude Code is used—to give you a clearer picture of your organization’s AI coding landscape. This data helps teams evaluate productivity impact, identify opportunities for enablement, and ensure Claude Code is being used effectively across the development lifecycle.

For instance, let’s say you discover that most Claude Code sessions are initiated from VS Code extensions, but only a handful come from JetBrains IDEs. At the same time, repositories linked to mobile projects show almost no activity. By examining session metadata in the “Usage & Adoption” view, you identify that the JetBrains plugin is out of date and not configured for token authentication. This suggests that configuration issues were limiting adoption.

Get started with the Claude Code Monitoring Preview

AI coding assistants like Claude Code are transforming software development workflows, but teams often lack visibility into how these tools are used, how reliably they perform, and what they cost. Datadog Claude Code Monitoring addresses these challenges by surfacing real-time insights into adoption, performance, and spend, all within the AI Agents Console.

By providing a unified view of Claude Code activity, Datadog helps teams evaluate reliability, track ROI, and ensure AI adoption remains cost-effective and impactful. To get started, check out our Claude Code Monitoring documentation or sign up for the Preview.

If you don’t already have a Datadog account, you can sign up for a free trial.