Docs

Deploy tracking

Connect the repository you deploy from, and every deploy to your production branch is measured and compared with the hour before it.

Connecting a repository

First connect your Git account once, in Settings → Integrations. The connection belongs to your team and works for every monitor:

  • GitHub: through the PulseKeeper GitHub App; you choose which repositories it can see;
  • GitLab: gitlab.com or your own GitLab, by signing in or with an access token;
  • Bitbucket: by signing in with Bitbucket.

Deploy tracking is available on plans that include it. See pricing.

Then open a website monitor, go to the Deploys tab and choose the repository and the branch you deploy from. We register the webhook ourselves.

What happens on a deploy

  1. A push to the branch is recorded as a deploy. A successful GitHub deployment status counts too and moves the measurement forward.
  2. About 3 minutes later we measure the site three times from every location of the monitor.
  3. Each location is compared only with itself over the hour before the deploy, so a different mix of locations is never reported as a change.
  4. The deploy gets a verdict: Better, Worse or No change, from server response time.
  5. On plans with PageSpeed, Google PageSpeed also loads the page once after the deploy (up to 3 deploys a day per site). The deploy shows the page weight before and after, and how much JavaScript, CSS, images and fonts changed.

Alerts

A deploy that is noticeably slower or heavier sends one warning to your alert channels: never an SMS, and quiet hours hold it. If the site fails after the deploy, that is an outage and it is reported as one instead.

A slower deploy is a lead, not a verdict: the comparison shows what changed after the commit, not that the commit caused it.