Tracking deployments
The Deployments page is a chronological list of release events — markers you record when a service deploys, so you can correlate them with metrics and incidents later.
Why track them here
Most incidents are caused by deployments. Having a chronological list right next to your metrics makes it easy to answer "what changed around the time this broke?".
Deployment markers appear as vertical lines on charts in Services, Metrics, and Dashboards — hover for details.
Header
- Title:
Deployments · Track releases and correlate with signals. - Refresh button top-right.
- + New Marker button — disabled when the source switcher is set to "All sources" (each marker is per-source). Pick a specific source from the scope switcher to enable it.
Results table
Columns:
| Column | Means |
|---|---|
| TIMESTAMP | When the deployment happened. |
| SOURCE | Which source the marker belongs to. |
| SERVICE | Which service deployed. |
| VERSION | Tag, commit SHA, or release name. |
| ENVIRONMENT | Free-form label (e.g., production, staging). |
| COMMIT | Short commit hash, often a link if a Git remote is configured. |
| DEPLOYED BY | Who triggered it (when known). |
Empty state:
> "No deployment markers found. Create markers from the UI or via the CI/CD webhook."
Three ways to record a deployment
- Manual marker — pick a source, click + New Marker, fill the form (service, version, environment, commit, optional notes). Useful for ad-hoc deploys.
- Webhook from CI/CD — POST a JSON payload to
/api/v1/deploymentsfrom your CI workflow. Authenticated with the source's API key. Lets the marker appear automatically on every deploy. - GitHub integration — install the ObserveKit GitHub App on your repos. Workflow runs that deploy emit markers automatically.
Detail view
Click a row to see:
- Diff link to GitHub (when configured).
- Linked PR / commit.
- Pre/post error rate comparison for the deployed service.
- Linked incidents that opened within 30 minutes after this deploy.
What this is not
- Not a CI/CD system. ObserveKit observes deployments; it doesn't run them.
- Not a release-notes tool. Use the version tag + diff link for that.
- Not multi-source. Each marker belongs to one source. Aggregated cross-source views are on the roadmap.