Skip to main content
Most incidents are caused by a change — a deploy, a feature flag flip, a config push. Change events capture those changes as they happen, so an investigation can line them up against when your incident started and point at the one that likely caused it. You don’t connect anything separately for this. Change events are built automatically from the bot and automated messages already flowing through the Slack channels you connect — the deploy bot in your #deploys channel, the feature-flag notifications, the infrastructure alerts.

​
How it works

When an automated message arrives in a channel you’ve connected, incident.io reads it and, if it describes a change, extracts a structured change event from it — pulling out what changed, when, who triggered it, and a link back to the source. A deploy notification becomes a deploy event with its service, environment, and commit; a feature-flag message becomes a flag event with the flag name. During an investigation, these change events are correlated with the incident’s timeline. A deploy that landed three minutes before the first error is exactly the kind of thing the investigation will surface — and because deploy events tie back to the underlying commit, it can connect that change to the specific code that shipped.
Only automated messages are turned into change events — the deploy bots, CI notifications, and flag-change alerts. Ordinary human discussion in the same channels is still used as Slack context, just not as change events.

​
What gets captured

Change events are sorted into categories so investigations can reason about them:
CategoryExamples
DeployA service or application being released
Feature flagA flag being turned on, off, or rolled out
ConfigA configuration or settings change
InfrastructureChanges to infrastructure, such as scaling or networking
DatabaseMigrations and other database changes
AlertAutomated alert notifications
OtherChanges that don’t fit the categories above
Each event also captures whatever detail the message contains — environment, service, commit, flag name, and a link back to the original notification.

​
Setup

There’s nothing extra to set up. Once you’ve connected the Slack channels where your automated change notifications land, change events are extracted from them automatically.
Connect the channels where your deploy, release, feature-flag, and infrastructure bots post. The more of your real change stream investigations can see, the more reliably they can trace an incident back to the change that caused it.

Slack channels

Connect the channels change events are built from.

Code repositories

Connect repositories so deploy events tie back to the code that shipped.