Deploys
The Deploys page is a chronological log of every deployment HostAtlas knows about, so you can answer the “was this incident caused by the deploy?” question in one click.
What you see
Section titled “What you see”Under Deploys in the sidebar. Each row is a deployment event:
- Server (or group of servers, if fanned out).
- Source — how HostAtlas learned about it: manual, inbound webhook from a CI provider, or a deploy-hook automation.
- Application or repository label.
- Version / commit SHA / release tag.
- Deployer — user or CI system.
- Started at, duration, outcome.
- Any alerts or incidents that fired within a short window afterwards.
Filters at the top: server, source, application, outcome, date range.
What you can do
Section titled “What you can do”- Open a deploy to see the metadata payload as received (headers, JSON body from CI), the correlated fleet events, and links to the affected server(s).
- Mark a deploy manually — useful when your pipeline can’t POST a webhook.
- Correlate — from any server detail page, the deploy markers are overlaid on the metric timeline so a spike after a release is obvious.
How it works
Section titled “How it works”- Deploy events land either via an inbound webhook (from GitHub Actions, GitLab CI, Bitbucket Pipelines, Buildkite, Jenkins, or any HTTP-capable pipeline) or from a Deploy Hook automation that fires on a marker file or CI callback.
- Each event is timestamped in UTC and attached to one or more servers by hostname or tag.
- HostAtlas cross-references the deploy timestamp with alerts, incidents, config changes, and metric peaks in a short window after the event and surfaces them on the deploy detail.
- Rollback information (previous SHA, revert timestamp) is captured when the CI system provides it in the webhook payload.
Related
Section titled “Related”- Pipelines — track the pipeline runs that produced the deploys.
- Activity — the full cross-fleet event stream deploys are part of.
- Alerts & Incidents — what deploys are correlated against.