Use case
Track publications and rollbacks without a chat channel
A publication is a sequence of related outcomes, not just a green or red message. Structured events make the revision, environment, health result and recovery path available after the initial interruption.
Updated 6 min read
Use one event per meaningful outcome
- Record publication success only after the defined health checks pass.
- Record publication failure with the stage and immutable revision.
- Record rollback completion as a separate event linked to the same release context.
A deterministic deduplication key keeps retries quiet while distinct result types remain visible. The release identifier in metadata lets you correlate them without flattening the sequence into one mutable message.
Link to evidence, not hidden execution
Open the release
Provide an HTTPS link to the deployment record or commit view.
Review health evidence
Keep the summarized result in the event and detailed logs in their owning system.
Frequently asked questions
- Does the producer need a special integration?
- No. The examples use an authenticated HTTPS request, so any script, service or visual workflow that can send HTTP can use the same contract.
- Should credentials be included in notification data?
- No. Keep credentials in the producer's secret store and send only the context needed to understand or locate the event.
Keep exploring
Put the pattern to work
Existing accounts can open the inbox and send their next event.