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

推荐订阅源

Vercel News
Vercel News
博客园 - 【当耐特】
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
aimingoo的专栏
aimingoo的专栏
WordPress大学
WordPress大学
G
Google Developers Blog
博客园 - 叶小钗
大猫的无限游戏
大猫的无限游戏
P
Proofpoint News Feed
J
Java Code Geeks
U
Unit 42
云风的 BLOG
云风的 BLOG
阮一峰的网络日志
阮一峰的网络日志
N
Netflix TechBlog - Medium
宝玉的分享
宝玉的分享
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
D
Docker
V
Visual Studio Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
H
Help Net Security
V
V2EX
T
Tailwind CSS 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
Unify visibility into changes to your services and depend...
2025-01-23 · via Datadog | The Monitor blog
Aaron Weber

Aaron Weber

Evan Pandya

Evan Pandya

In modern application development, changes happen constantly: Deployments are pushed, feature flags are toggled, and Kubernetes events reshape infrastructure, to name just a few. While these practices drive innovation and scalability, they also introduce complexity---especially during incidents. Fragmented tools and workflows across teams and organizations make it difficult to pinpoint the root causes of issues, leading to longer resolution times.

To address these challenges, Datadog Change Tracking offers real-time visibility into a wide array of system changes by surfacing relevant changes directly within Datadog’s monitors, dashboards, and service pages. Change Tracking provides an immediate and unified view of changes such as application deployments, feature toggle updates, Kubernetes events, and database modifications. Teams can promptly identify relevant changes and take informed action, accelerating root cause analysis and reducing time to resolution.

In this post, we’ll walk you through an example of how Change Tracking can help you:

View changes to your services and dependencies directly in context

Imagine that you receive an alert that the error rate for a critical API is spiking. Your team’s first step is to investigate potential root causes. Without a unified view of changes, the investigation process is fragmented. Your team must manually gather data from various logs, monitoring tools, and pipelines to try to understand what might have changed. This manual work delays incident resolution and increases the risk of focusing on the wrong area.

With Change Tracking, changes made to the API and its dependencies are immediately accessible in context across the Datadog platform, including on:

  • Monitor status pages: When a monitor is in a warning or alerting state, use Change Tracking to review recent changes related to the affected service directly on the status page. This functionality helps you quickly identify if a recent deployment, feature flag, or other change might have contributed to the monitor’s change in state.
  • Service pages: On the Service Summary page in APM, view the timeline of changes to the service and its dependencies alongside metrics such as latency, error rate, and throughput. This functionality helps you see how recent updates align with fluctuations in performance or health metrics.
  • Dashboards: Use the Show Overlays button to display tracked changes as interactive overlays directly on timeseries widgets or directly in the change timeline for clear visual correlation between changes and metric trends.

The following screenshot shows a monitor status page for our example API that is experiencing an increase in error rate. Here, we see that Change Tracking is surfacing a deployment change and a feature flag change as potential root causes for you to investigate.

A monitor status page shows the deployment change and feature flag change, along with an event timeline and event details.

Correlate recent changes with disturbances in service health and performance

With relevant changes automatically surfaced, you can use Change Tracking to correlate these events with the spike in error rate. Hovering over individual change events, such as the feature flag change, reveals details to streamline your analysis. Among these details are the associated service name and the timestamp of the change.

You can access details about the feature flag change by hovering over the change.
A monitor status page shows the name, timestamp, and associate service for a feature flag change.
You can access details about the feature flag change by hovering over the change.

By choosing View Details on the feature flag change, you open the change details side panel. Here, you discover that the feature flag was toggled on and introduced a configuration that directs the API to a different data store. While this change could have contributed to the increased error rate, you don’t know for sure.

Details of the feature flag change that directed the API to a different data store.
The side panel shows more details about the feature flag change, including the user who made the change, an identifier, and a description.
Details of the feature flag change that directed the API to a different data store.

You can then shift your investigation to the deployment. When you review the latest commit linked to the deployment, you uncover code changes that didn’t properly account for the increased load conditions on the new data store. The code changes caused the spike in errors when the feature flag was enabled.

Details of the deployment change, including the corresponding increase in error rate.
The side panel shows more details about the deployment change, including the environment and a timestamp. The panel also shows request rate, error rate, and latency.
Details of the deployment change, including the corresponding increase in error rate.

Access detailed change insights and take next steps within Datadog

Now that you have identified the root cause as a combination of the faulty deployment and the feature flag, you can focus on stabilizing the system. You determine that the most efficient way to address the issue is to toggle off the feature flag, redirecting traffic back to the original data store. If you have configured the LaunchDarkly integration in Datadog, you can toggle off the feature flag directly in the Change Tracking side panel by using the LaunchDarkly remediation workflow powered by Datadog Workflow Automation. Alternatively, you can set up a custom workflow or manage the flag externally, depending on your internal processes and preferences.

After you identify the root cause of the issue, you can toggle off the feature flag in Datadog.
A configuration screen provides the option to connect to LaunchDarkly and toggle off the feature flag. The screen also presents options to toggle on Slack notifications and action approvals.
After you identify the root cause of the issue, you can toggle off the feature flag in Datadog.

The change details and available actions in Change Tracking are dynamic and tailored to the type of change. For example, application deployment changes include rollout details, version differences, and links to CI/CD pipelines. Conversely, Kubernetes deployment changes provide diffs, cluster metadata, and quick links to logs and pods. Change Tracking gives you the right context and tools for different types of tracked changes, enabling in-depth analysis and efficient responses across a wide range of use cases.

Get started with Change Tracking today

Datadog Change Tracking provides comprehensive visibility into changes across your services and dependencies, integrating insights into monitor status pages, dashboards, and service pages. With Change Tracking, you can view changes, correlate the changes with performance data, and take next steps to remediate issues. As a result, you can improve efficiency and reliability by identifying root causes and resolving incidents faster.

You can find a comprehensive list of supported change types and tracking requirements in the Change Tracking documentation. If you don’t already have a Datadog account, sign up for a 14-day free trial today.