Docs · 6/13 Deploys

Deploys

Deploy tracking puts a marker on BugOtter's timeline each time you ship. Issues then say which deploy they started after ("Started 4 min after deploy c0ffee1"), and each deploy gets a before-and-after check. Connect Vercel and it's automatic; otherwise add one webhook.

In 30 seconds

using Vercel? Import your projects and you're done. Otherwise open the app → Setup → Mark your deploys, copy the webhook URL, and add it to GitHub or Netlify.

Vercel

Import your projects from Vercel and every production deploy is tracked, checked every 5 minutes. Nothing else to do.

Webhooks

Each app has a deploy webhook URL, with its key built in: app → Setup → Mark your deploys → Show me how.

  • GitHub: repo → Settings → Webhooks → Add webhook. Paste the URL, set content type to application/json, and pick Pushes (counts pushes to the default branch) or Deployment statuses (counts successful production deploys). The Secret field isn't needed.
  • Netlify: site → Project configuration → Notifications → Outgoing webhook → Deploy succeeded. Paste the URL. Production deploys count.

Add &branch=staging to the URL to follow another branch. For GitHub pushes, that branch counts instead of the default one. For GitHub deployment statuses and Netlify, preview deploys count too.

Anything else

Run npx bugotter deploy as the last step of your deploy. It takes the commit and its message on its own; pass --version and --message to set them. Or call the endpoint yourself:

Terminal or CI
curl -X POST https://bugotter.com/api/YOUR_PROJECT/deploys \
  -H "Authorization: Bearer $BUGOTTER_KEY" -H "content-type: application/json" \
  -d '{"version":"c0ffee1","message":"Fix coupon"}'

YOUR_PROJECT and the key are in the webhook URL on the Setup tab, and in .env.local as BUGOTTER_PROJECT and BUGOTTER_KEY after init. See the CLI.

What you get

  • On every issue: an issue that starts within 2 hours of a deploy says "Started N min after deploy X. Could be related, could be a coincidence."
  • On the timeline: deploys show on the app's Overview, and as markers on traffic charts.
  • A deploy check: for each deploy in the last 7 days, BugOtter compares the 24 hours before with the time since: errors per 100 visits, new errors, response time, paid conversion and revenue per visit. It says Looks fine, Worse since … or Too early (under an hour, or fewer than 30 visits). Find it on the app's Setup tab under Mark your deploys and on the Errors tab.
A deploy check: v1.8.1 looks fine, no new errors, and errors, speed and sales are like the day before
  1. The verdict: Looks fine, Worse since … or Too early.
  2. Before and after shows each number side by side.

Common questions

"Unknown project or upload key"

The key in the URL or header is wrong. Use the upload key from the app's Setup tab, not the DSN key.

The webhook answers "skipped": true

That event didn't count as a production deploy: a push to another branch, or a preview deploy. Add &branch=… to follow another branch.

Is the webhook URL secret?

Yes. Its key lets anyone post deploy markers and source maps for that app. Keep it in your CI's secrets, not in public code.

See alsoErrors and source mapsCLIAdd your apps