> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/ai-sre/3.0/ai-sre-for-administrators/set-up-change-management/change.md).

# Change Management

Change management in Harness AI SRE helps you understand what code, configuration, and infrastructure changes were deployed when incidents occur. By connecting your CI/CD pipeline data, builds, deployments, and pull requests, you gain precise visibility into what changed and when.

### Key capabilities <a href="#key-capabilities" id="key-capabilities"></a>

Change management provides the following capabilities:

* **Deployment tracking:** Automatically capture which services and versions were deployed to each environment
* **Build correlation:** Link deployments back to specific builds and commit SHAs
* **Code change visibility:** See which PRs and code changes were included in each deployment
* **Incident correlation:** During incidents, instantly identify what changed in your system

***

### How it works <a href="#how-it-works" id="how-it-works"></a>

The [Deploy Change Investigator](/ai-sre/ai-sre-for-administrators/set-up-change-management/deploy-change-investigator.md) connects three data streams from your CI/CD pipeline:

1. **Build webhooks:** Capture artifact versions and commit information when builds complete
2. **Deploy webhooks:** Track when services are deployed and to which environments
3. **PR ingestion:** Automatically sync merged pull requests from your repositories

When an incident occurs, the AI SRE agent uses this data to show you exactly which changes were deployed around the time of the incident, helping you quickly identify potential root causes.

***

### Get started <a href="#get-started" id="get-started"></a>

To enable change management capabilities:

1. [Set up the Deploy Change Investigator](/ai-sre/ai-sre-for-administrators/set-up-change-management/deploy-change-investigator.md)
2. [Configure sources of change](/ai-sre/ai-sre-for-administrators/set-up-change-management/sources/overview.md) to send webhooks from your CI/CD pipelines
3. Learn how the [AI Agent uses change detection](/ai-sre/3.0/ai-sre-for-incident-responders/use-ai-agents/rca-change-agent.md) during incident investigation

***

### What is tracked <a href="#what-is-tracked" id="what-is-tracked"></a>

Change management tracks:

* **Service deployments:** Which services were deployed, when, and by whom
* **Artifact versions:** Specific versions and build IDs for each deployment
* **Code changes:** Pull requests, commits, and files changed
* **Environments:** Deployment targets (production, staging, QA, etc.)
* **Timeline correlation:** Map deployments to incident timelines

This data enables the AI SRE agent to provide context-aware insights during incident response and root cause analysis.

***

### Next steps <a href="#next-steps" id="next-steps"></a>

* Go to [Deploy Change Investigator](/ai-sre/ai-sre-for-administrators/set-up-change-management/deploy-change-investigator.md) to set up change tracking.
* Go to [Sources of change](/ai-sre/ai-sre-for-administrators/set-up-change-management/sources/overview.md) to send webhooks from your CI/CD pipelines.
* Go to [AI Agent change detection](/ai-sre/3.0/ai-sre-for-incident-responders/use-ai-agents/rca-change-agent.md) to understand how change data supports investigation.