Feature Tutorials
Change Events
Change Events Tutorial
The first thing most responders ask when investigating an incident is "What changed?". In fast-moving, complex environments, it can be challenging to know the answer to that question.
Change Events, or Recent Changes, allows PagerDuty to capture information about important changes from across your infrastructure. Making changes in production environments can be risky; it has been estimated that a majority of production incidents are due to some change that was made in the environment.
Rather than stop making changes (and therefore improvements!) to your systems, track them in PagerDuty using the Recent Changes feature.
Change Events are small updates, in javascript, sent automatically from your tools when a change is made. Capture changes from your code repositories, CI/CD pipelines, and infrasctrure as code tools.
Learn More
Read more about what Change Events provide
- We Built an SRE Agent With Memory - Change Events provide context for triage.
Watch the product demos and webinars
- Introduction video: Change Management – Change Events Integrations
- Webinar: Optimizing Response Time with Change Event Data — Covers how recent changes are a major factor in incident creation and how change event data helps improve MTTR.
- How Change Events show up in the PagerDuty Mobile App
- Change Management – Change Events Integrations - Capturing Change Events from your code repo and CI/CD pipelines.
Check out the training modules on PDU
- Event Intelligence 101 — Covers noise reduction methods and how to use Change Events + Probable Origin for root-cause analysis.
- Change Events.
Watch the click-through tutorial
coming soon
Find the product documentation in our Knowledge Base
Using the API?
Change Events will be sent to via the Events API:
Other Resources
- Read more about Root Cause vs Contributing Factors at ReliabilityWeb.
- or at Tulip.co