Skip to main content
Correlate incidents with deployments and config changes from any source. OpenSRE reads Grafana annotations — the standard, source-agnostic “what changed and when” marker — so the agent can answer “did a deploy or config change precede this alert?” even when the change did not come from a GitHub push (ArgoCD/Flux syncs, helm upgrade, Jenkins/CircleCI jobs, Terraform applies, manual hotfixes). This complements the GitHub deploy timeline, which only sees GitHub-originated deploys.

Requirements

No new setup or credentials — it reuses your existing Grafana integration. If Grafana is connected (see Grafana), the annotations tool is available automatically during investigations.

Parameters

Example

Each annotation also carries time_end (set only for region annotations) and dashboard_uid (set only when the annotation is attached to a dashboard); both are null otherwise. The agent uses results like this to flag a likely change-induced regression and tie the suspected root cause to a specific deploy.

Emitting annotations

Make your deploys visible by writing a Grafana annotation when you ship. Most CD tools can post to Grafana’s annotations API, for example:
Tagging deploy annotations consistently (e.g. deployment) lets the agent filter precisely during an investigation.