VOOZH about

URL: https://docs.datadoghq.com/change_tracking/

⇱ Change Tracking

For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/change_tracking.md. A documentation index is available at /llms.txt.

Change Tracking

Change Tracking is not available in the selected site ()

Overview

Change Tracking streamlines troubleshooting and incident response by surfacing relevant changes to your service and its dependencies, enabling faster detection and remediation when issues arise.

Change Tracking supports monitoring of a range of modifications to your service and its dependencies including:

  • Deployments
  • Feature Flags
  • Traffic Spikes
  • Configuration Changes
  • Database Modifications
  • Schema Changes
  • Scale Adjustments
  • Kubernetes Adjustments
  • Kubernetes Pod Crashes
  • Watchdog Alerts

For details on specific types of supported changes and setup requirements, see the Tracked changes section.

Using Change Tracking

Change Tracking is available on several pages in Datadog:

Monitor status page

View and analyze changes from the monitor status page.

Prerequisites

To use change tracking on the Monitor Status Page, ensure the appropriate service has been:

  • Specified in the monitor query.
  • Selected as part of a group.
  • Added as a service tag on the monitor.

To analyze changes from the monitor status page:

  1. Go to the monitor status page for the monitor you are analyzing.
  2. Locate the change tracking timeline at the top of the page.
    • For monitors with multiple graphs (dictated by the group by in the monitor query), filter to an individual group.
  3. Use the timeline together with the event graphs to correlate change events with the alert.
  4. Click the change indicator in the timeline to view more details about the change in the side panel.
  5. From the side panel, you can investigate more details about the change and take the following actions:
    • View the deployment in your CI/CD system.
    • View the latest commits in your repository.
    • Compare changes between deployments to identify potential issues.
    • Configure additional custom links in the deployment side panel to quickly access other resources relevant to you.

Services

View and analyze changes from the service page.

To analyze changes from the service page:

  1. Navigate to the service page you want to investigate.
  2. Locate the changes timeline in the Service Summary section.
  3. Use the service and dependencies tabs to view either:
    • Changes limited to the specific service (Changes by Service)
    • Changes to the specific service and dependent services that might impact this service (Changes by Service + Dependencies)
  4. Click the change indicator to view detailed information and take remediation actions.

Dashboards

View and analyze changes from any dashboard.

Prerequisites

To see relevant changes within the timeline and as overlays on your dashboard, ensure you have set at least one timeseries widget.

To analyze changes from dashboards:

  1. Navigate to your dashboard.
  2. Click Show Overlays at the top of the page to enable the change timeline and change overlays on supported widgets.
  3. Hover over any change indicator or overlay to view a summary of the change.
  4. Click the change indicator or overlay to view detailed information and take remediation actions.

Widgets

In addition to the out-of-the-box integrations, Change Tracking is available as a data source for widgets across Datadog, including Dashboards and Notebooks.

To configure a widget using Change Tracking data:

  1. In a dashboard or notebook, add or edit a supported widget type (Timeseries, Query Value, Table, Tree Map, Top List, Pie, Change, or Bar Chart).
  2. From the data source dropdown, select Change Tracking.
  3. Configure your filters (Service is required).
  4. (Optional) For widgets that support grouping, use Group by to split results.

For Timeseries widgets, you can also enable Change Tracking as an Event Overlay, which displays changes on top of the timeseries to help correlate them with metric behavior.

View change details

To view information about a change or set of changes, click a datapoint in the widget and select View Changes. This opens the Change Tracking side panel with additional details.

Tracked changes

Change Tracking follows these types of changes across your infrastructure:

Change TypeTracking Requirements
Code Deployments (APM)APM & Deployment Tracking. A version must be available on the service.
Kubernetes Deployment Manifest UpdatesDatadog Agent Set Up for Kubernetes (Add service label to Kubernetes yaml file if possible).
Feature FlagsUse the LaunchDarkly integration or send custom events using the Events API. See the Feature Flag Tracking documentation for setup and advanced options.
Custom Configuration Change EventsEvent Management API.
Watchdog Alerts (Error Rate Spikes, Latency Spikes, Cloud and API Outages, etc.)See Watchdog documentation to learn more about requirements for specific Watchdog Alerts.
Traffic Spikes (APM)Application Performance Monitoring (APM)
CrashLoopBackOff Kubernetes Pod CrashesKubernetes Integration (Add service label to Kubernetes yaml file if possible).
PostgreSQL, SQL Server and MySQL Database Table (Schemas) ChangeSee Exploring Database Schemas documentation to learn more about tracking schemas using DBM, and Correlate Database Monitoring and Traces to set up APM and DBM correlation.
MongoDB Index & SearchIndex ChangesDatabase Monitoring (DBM), Correlate Database Monitoring and Traces.
PostgreSQL Database Settings ChangeDatabase Monitoring (DBM), Correlate Database Monitoring and Traces.
SQL Server Database Settings ChangeDatabase Monitoring (DBM), Correlate Database Monitoring and Traces.
Kafka Schema UpdatesData Streams Monitoring (DSM).
Manual Kubernetes Deployment Scale EventsKubernetes Audit Logging.
Cloud Infrastructure Resource Changes (This feature is in Preview and currently limited to a small sample of cloud resource changes. To request access, see the Resource Changes documentation linked in Tracking Requirements.)Resource Changes - Enable Resource Collection and optionally cloud provider event forwarding.

Further reading