GitHub integration
Deploy markers on your uptime charts
Connect GitHub and every deploy is drawn on your monitors' charts and cited beside incidents. The first question of every outage, answered before it's asked.
Sentinel → GitHub
Why deploy markers
Outages start making sense when deploys are visible
The first question of every incident is the same: did we just ship something? Answering it usually means alt-tabbing between a monitoring dashboard and a git log, holding timestamps in your head. Sentinel draws the answer directly on the chart: a dashed line where each deploy landed, against the response times that followed it.
It works the quiet way: install the GitHub app once, link repositories to the monitors they deploy, and every push and deployment shows up where you debug. The app consumes webhooks only, so it can see nothing in your account beyond the fact that a deploy happened.
- Install in one click from your Sentinel dashboard
- Link any repository to any monitor, many to many
- Markers from default-branch pushes and GitHub Deployments
- Optional pause while a deployment runs, with a failsafe resume
Deploys in this window
3f2c1a9 acme/client-site by dana · 12:47 PM
Response times rose four minutes after this deploy landed.
Features
Everything deploy tracking should do
Deploy markers on your charts
Every default-branch push and every deployment draws a dashed line on the monitor's response-time chart, with the deploys behind the lines listed underneath.
Cited beside incidents
When an incident opens within an hour of a deploy, the incident page says so: which repo, which commit, who shipped it, and how many minutes before the incident it landed.
Pause monitoring during deploys
Opt a monitor in, and it pauses the moment a GitHub Deployment starts and resumes when it finishes. A 20-minute failsafe means a hung deploy can never silence monitoring for good.
Reads nothing, by design
The app only consumes webhooks. It holds no API credentials, makes no API calls, and cannot see your code, issues, or anything else in your account.
Repos and monitors, many to many
A monorepo can feed several monitors, and a monitor can listen to several repos. Each link chooses its own behavior: markers, pauses, or both.
Failed deploys flagged
When a deployment reports failure, its marker turns red on the chart, so a bad ship is visible at the exact spot the response times started misbehaving.
How do I connect Sentinel to GitHub?
From your team's Integrations page, click Connect GitHub, choose which repositories the app may see, and you land back in Sentinel to link each repo to the monitor it deploys. The whole setup takes about a minute.
What can the app access?
Almost nothing, deliberately. It consumes webhooks about pushes and deployments, holds no API credentials, and makes no API calls: your code, issues, and pull requests are invisible to it. Its GitHub permissions are read-only Contents and Deployments metadata.
When is a marker drawn?
When a push lands on the repository's default branch, or when a GitHub Deployment is created. The marker sits at the start of the deploy, and if a deployment later reports failure, the marker turns red.
Does pause-during-deploys work with my CI?
Pauses trigger on GitHub Deployment objects, which GitHub Actions environments, Vercel, Railway, and most CD platforms create. Plain pushes only draw markers, since a push has no duration. If your pipeline deploys without creating Deployments, you can pause explicitly with the Sentinel API instead.
Which plans include the GitHub integration?
Every plan, including free. Deploy markers make monitoring data more useful, and that should not sit behind a paywall.
Put your deploys on your charts
Connect GitHub in one click, and your next push draws its own marker.
No card for the free plan · 14-day trial on paid plans · Cancel anytime