Oxvel
FeaturesIntegrationsPricingDocsChangelog
Sign inGet startedOpen the app
Documentation

Integrations

Integrations

Vercel

Oxvel reads your deployments and their build logs, warns you when production doesn't update, and can roll back to the previous deployment.

Connect Vercel

  1. 1On Vercel, open Account Settings, Tokens, and create a token.
  2. 2For the scope, choose the team that owns your projects. Set an expiration date if you want.
  3. 3In « Paramètres, Connecteurs » (Settings, Connectors), click Connecter (Connect) next to Vercel and paste the token.

What Oxvel reads

  • Projects, with their Git repository and production URL.
  • Deployments, production and preview, with their status, the commit and its author.
  • The build log of a deployment, especially the end and the error lines, to explain a failure.
  • Environment variable names and where they exist (production, preview, development). Never their values.

Failed deployment

When a production deployment fails, Oxvel sends it by email (if « Alertes d'astreinte » (On-call alerts) is turned on) and to the Slack alerts channel. If « Analyser les nouvelles erreurs tout seul » (Analyze new errors automatically) is turned on in your , it reads the log and your code first, and the alert already says what is blocking, with a link to the full analysis.

Roll back to the previous deployment

On an incident page, if the error's repository is deployed on Vercel, Oxvel shows what is live and the Revenir au déploiement d'avant (Roll back to the previous deployment) button. After you confirm, production switches back to the previous deployment right away, with no new build. You can also ask in the chat ("roll back my-app to the previous deployment"). Oxvel shows you what is live and what will replace it, and nothing changes until you click Revenir (Roll back). You can forbid this in your .

Example questions

  • "Why did the last deployment of my-app fail?"
  • "What went to production right before the incident?"
  • "Which projects have a broken build?"

Your functions' runtime logs aren't read. For those, connect Datadog or another logging tool.

On this page