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

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hacker News: Front Page
P
Palo Alto Networks Blog
T
ThreatConnect
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
T
True Tiger Recordings
P
Privacy & Cybersecurity Law Blog
B
Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
F
Full Disclosure
Hacker News: Ask HN
Hacker News: Ask HN
C
Comments on: Blog
Microsoft Azure Blog
Microsoft Azure Blog
C
Cybersecurity and Infrastructure Security Agency CISA
Microsoft Security Blog
Microsoft Security Blog
博客园 - 【当耐特】
N
News and Events Feed by Topic
NISL@THU
NISL@THU
腾讯CDC
雷峰网
雷峰网
Security Latest
Security Latest
李成银的技术随笔
M
Microsoft Research Blog - Microsoft Research
L
LangChain Blog
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Check Point Blog
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
博客园 - Franky
N
News | PayPal Newsroom
V
V2EX
A
About on SuperTechFans
The Register - Security
The Register - Security
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google Online Security Blog
Google Online Security Blog
MyScale Blog
MyScale Blog
Cisco Talos Blog
Cisco Talos Blog
Vercel News
Vercel News
WordPress大学
WordPress大学
C
Cyber Attacks, Cyber Crime and Cyber Security
The Hacker News
The Hacker News
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
爱范儿
爱范儿
A
Arctic Wolf
L
LINUX DO - 最新话题
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Datadog | The Monitor blog

Reduce CVE noise with OpenVEX assessments in Datadog How we made a SQL query optimization agent 59% more accurate using autoresearch and LLM Observability How to audit and clean up monitors effectively Diagnose slow PostgreSQL queries faster with explain plan correlation Explore Datadog metrics with Natural Language Queries Toto 2.0: Time series forecasting enters the scaling era Simplify micro-frontend observability with Datadog RUM Attribute AI costs across providers with Datadog Cloud Cost Management Diagnose and resolve database performance issues faster with Database Investigator Datadog for Government achieves FedRAMP® High certification Analyze cloud costs with flexible spreadsheets in Datadog Sheets Inside Datadog’s AI Research Lab: Meet two PhD candidates behind Toto Connect triage and investigation in a single workflow with Datadog Cloud SIEM This Month in Datadog - April 2026 Monitor and optimize Supabase query performance with Datadog Database Monitoring Add dynamically updating context to logs with Reference Tables and Observability Pipelines Introducing ARFBench: A time series question-answering benchmark based on real incidents The product signal latency gap slowing your growth Test network paths with TCP, UDP, and ICMP in Datadog Turn developer feedback into operational insight with Datadog Forms and Sheets How to investigate cloud credential compromise with Bits AI Security Analyst Evaluate, optimize, and secure your Google Cloud AI stack with Datadog Bringing observability data hosting to the UK on AWS Identify and fix code issues faster with Datadog’s Azure DevOps Source Code integration Steganography at scale: Embedding share URLs in Datadog widget screenshots Every team should be A/B testing Centralize observability management with Datadog Governance Console Spotting CI/CD misconfigurations before the bots do: Securing GitHub Actions with Datadog IaC Security Route OTel data from AI apps to ClickHouse and Datadog using Observability Pipelines Manage service tracing across hosts with Single Step Instrumentation rules Offline evaluation for AI agents: Best practices Detect runtime threats in Python Lambda functions with Datadog AAP 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 How we built a real-world evaluation platform for autonomous SRE agents at scale 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 When upserts don't update but still write: Debugging Postgres performance at scale 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 Closing the verification loop: Observability-driven harnesses for building with agents When an AI agent came knocking: Catching malicious contributions in Datadog’s open source repos Closing the verification loop, Part 2: Fully autonomous optimization 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 Designing MCP tools for agents: Lessons from building Datadog's MCP server 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 Fine-tune Toto for turbocharged forecasts 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 How we reduced the size of our Agent Go binaries by up to 77% 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
Datadog governance 101: From chaos to consistency
2025-08-20 · via Datadog | The Monitor blog
David Iparraguirre

David Iparraguirre

Aaron Herrmann

Aaron Herrmann

Addie Beach

Addie Beach

As your organization scales, managing observability resources and usage becomes increasingly important. More users and teams mean more dashboards, tags, API keys, and costs to manage. The job of keeping track of these resources and ensuring that they’re compliant can quickly grow in complexity. An effective observability governance strategy can help you handle these challenges at scale as you repeatedly work to onboard new services, determine who owns dashboards and monitors, control visibility over sensitive information, and manage usage over key features.

In this post, we’ll explore the basics of observability governance, a few key best practices, and how you can use Datadog to put your governance strategy into practice.

What is observability governance?

A key feature of many observability platforms is that they enable anyone in your organization to access monitoring data, which is essential for breaking down silos across teams. However, this openness and flexibility can present significant compliance and security risks. As the number of dashboards, monitors, and pipelines in your monitoring platform grows, it can become challenging to manage who owns what and who should have access to it. Additionally, usage anomalies can easily go unnoticed until costs spiral out of control.

Observability governance addresses these challenges by providing you with a framework and tooling for handling the growth of your monitoring efforts safely and consistently. It helps you manage data access, attribute costs to specific teams and services, enforce organization-wide policies, and ensure effective product usage.

How observability governance is structured can vary across organizations. At its simplest, it can be a set of guidelines and best practices that teams follow. In larger organizations or in industries dealing with sensitive data, governance may be managed by a centralized team responsible for ensuring those practices are followed and applied consistently.

Regardless of whether governance management is left to individual teams or a single centralized group, the core best practices remain largely the same. We’ll explore what these practices look like and how you can implement them below.

Observability governance best practices

A good observability governance framework covers every aspect of how your organization interacts with monitoring data. It should include tools and processes that are simple enough for teams to easily implement, while remaining flexible enough to accommodate their individual needs.

There are four key pillars to an effective observability governance strategy:

Tagging

Consistent tagging should be the foundation of your governance strategy, as it helps you establish a single source of truth across your data. Generally speaking, you should make sure that your metrics, logs, traces, and event data are annotated with four basic tags: service, env (environment), team, and version. While the exact tags you use may depend on the needs of your organization, ensuring that these four are added to every piece of data gives you the reliable, organization-wide context you need to draw relationships between services, infrastructure, and teams.

You can use these relationships to establish clear lines of ownership and dependency. With tags, you can quickly identify which teams are responsible for which services, and which ones they don’t interact with at all. When combined with insights into usage activity, this knowledge makes it easier to determine where access to certain tools or data should be restricted. In Datadog, you can also use tags to define access boundaries, enabling you to control who can view sensitive data.

For smoother adoption of tagging policies, ensure that teams across your organization can easily tag their resources without disrupting their workflows. To help with this, Datadog provides several ways to assign tags, including directly within the platform UI or via the Datadog API.

Access and key management

One of the most critical functions of governance is managing data permissions. Tagging can help you control access on a granular level. To handle permissions more sustainably at scale, you’ll also need to define user roles. Many monitoring platforms include default roles that let you quickly apply common, system-wide permission sets—such as admin or read-only—to users across multiple teams. Additionally, Datadog supports custom roles to more precisely manage access so that you can tailor permissions for specific personas like auditors or support engineers.

A list of roles for an organzation.

Beyond controlling what data users can view and edit, you’ll want to manage how they access it. Datadog uses both API keys and application keys to authenticate users. To strengthen system security, you should reduce the risk of compromised keys being used to access your data. Datadog enables you to do this via several methods. First, you can scope your application key permissions to ensure each user has only the privileges necessary to do their job, reducing the impact of potential attacks. Second, you can use multiple Datadog API keys across your organization, making it easy to regularly rotate and revoke keys.

As more services, tools, and teams are added to your organization, you should periodically revisit your access policies to ensure that they continue to block unauthorized access without becoming overly restrictive. You’ll also want to configure alerts on system events that may indicate malicious activity. For example, a sudden spike in API key creation or usage could point to a compromised integration or an abused credential. Datadog Audit Trail can help you identify which events to monitor and correlate anomalous behavior with historical activity. If you do notice a suspicious event, Audit Trail enables you to investigate deeper with a record of recent user actions. This can help you determine whether sensitive data was accessed or critical configurations were changed.

Cost control

Governance also plays a key role in managing observability costs. By enriching your data with ownership information, governance helps you attribute usage to the specific teams, services, and resources contributing most to your overall expenses.

Datadog provides direct visibility into team-level and resource-level spend through features like Usage Attribution. Usage Attribution uses your tags to build detailed reports that break usage data down into customizable facets like team, app, and service.

Datadog usage for products such as APM and USM broken down by team.

Tagging can also make your cost insights more robust. For example, Datadog FinOps analysts found that breaking down our cloud spend by team helped them collaborate more deeply with engineers on storage optimization projects, with the resulting changes saving us roughly $1.5 million dollars annually.

Once you’ve identified areas where you can optimize observability spend, you can fine-tune data sampling rates for services and endpoints across your system. This lets you limit the amount of data you ingest from high-throughput resources, which can easily drive up costs and create unnecessary noise, while still capturing enough from lower-volume sources to effectively troubleshoot issues. Within Datadog, you can easily manage sampling for individual resources via log indexing, trace ingestion controls, and user session sampling. You can also adjust retention periods so that you only store representative samples of critical data.

Additionally, you can configure cost alerts to catch unexpected spend increases early. Datadog Cloud Cost Monitoring lets you calculate these alerts in several ways, including historical activity comparisons, exact thresholds, anomaly detection, and forecasts. As opposed to ingestion controls, these alerts are based on actual spend, making them more resilient to change in data volume or pricing.

A list of cost monitors, a few showing triggered alerts.

Onboarding and organizational alignment

Creating governance policies is the first step, but enforcing them can present further challenges. Teams may adopt best practices unevenly, prioritizing those that are closest to their existing processes. Some teams may also struggle to understand which policies and procedures even apply to them in the first place.

To align your teams, you’ll want to give them a single resource that helps them understand what they’re responsible for. You can do this in Datadog via Teams, which enable you to easily group and filter assets—including dashboards, incidents, services, and monitors—based on ownership. Once you’ve established which resources your teams own, you can set up Scorecards to help them evaluate how well their configuration aligns with organizational best practices.

Scorecards broken down by area, including ownership and production readiness.

Finally, you’ll want to define policies for product adoption and project creation to ensure that any new activity follows your governance strategy. Datadog Workflow Automation can help teams integrate these policies into their work by providing standardized, easy-to-use flows for common tasks. These flows can include setting up or removing user accounts, scaffolding new projects via Golden Paths, and identifying discount program opportunities.

Unify governance activity with Datadog

As we’ve discussed, Datadog has a variety of features that can help you design and implement your governance strategy. However, using these features often means navigating between different areas of the platform while trying to ensure that all of your observability data is secured and monitored.

To help address this, we’ve created the Datadog Governance Console. From the console, you can view Datadog activity for every team in your organization. The console enables you to visualize tagging coverage for your services, customize cost and access policies, and view governance guides. Together, these views help you identify and respond quickly to compliance gaps. To visualize this activity at a high level, you can create governance policies that give you an overview of adoption for key best practices.

The Governance Console view, with organization-wide usage metrics displayed.

Let’s say you want to ensure that all of your data has team, env, and service tags. You can create a governance policy to help you track how much of your data includes these tags. Then, when you notice that your adoption rates for this policy are low, you can decide to revisit your tagging outreach strategy to improve internal alignment.

Manage observability data across your organization

Observability data is key for troubleshooting issues within your system, but it can also present security risks and drive up costs. By helping you develop a clear, consistent strategy for managing your data, observability governance makes it easier for your organization to scale its monitoring efforts safely, reliably, and cost effectively.

Datadog Governance Console is currently in Preview. To get started, you can sign up for the Governance Console program. Or, if you’re new to Datadog, you can sign up for a 14-day free trial.