From 1107dc61d285882b8abcf2fbc2b543b71b61534a Mon Sep 17 00:00:00 2001
From: Aaron <32344007+aaronvweber@users.noreply.github.com>
Date: Fri, 31 Jan 2025 11:47:41 -0500
Subject: [PATCH] Updated docs to include custom configuration changes (#27396)

---
 content/en/change_tracking/_index.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/en/change_tracking/_index.md b/content/en/change_tracking/_index.md
index 0dc10b0b5103d..eec1dfadbc1b5 100644
--- a/content/en/change_tracking/_index.md
+++ b/content/en/change_tracking/_index.md
@@ -39,6 +39,7 @@ Change Tracking streamlines troubleshooting and incident response by surfacing r
 Change Tracking supports monitoring of a range of modifications to your service and its dependencies including:
 - Deployments
 - Feature Flags
+- Configuration Changes
 - Database Modifications
 - Schema Changes
 - Scale Adjustments
@@ -118,6 +119,7 @@ Change Tracking follows these types of changes across your infrastructure:
 | Kubernetes Deployment Manifest Updates | Datadog Agent Set Up for Kubernetes (Add service label to kubernetes yaml file if possible)
 | LaunchDarkly Feature Flag Events (service tag must be defined on event) | Third Party Datadog Integrations ([LaunchDarkly only][5])
 | Custom Feature Flag Events | [Event Management API][6]
+| Custom Configuration Change Events | [Event Management API][6]
 | Watchdog Alerts (Error Rate Spikes, Latency Spikes, Cloud and API Outages, etc.). | See [Watchdog][7] documentation to learn more about requirements for specific Watchdog Alerts.
 | CrashLoopBackOff Kubernetes Pod Crashes | Kubernetes Integration (Add service label to kubernetes yaml file if possible)
 | PostgreSQL Database Table Change | [Database Monitoring (DBM)][8], [Correlate Database Monitoring and Traces][10]