Oxvel
FeaturesIntegrationsPricingDocsChangelog
Sign inGet startedOpen the app
Documentation

Integrations

Integrations

PagerDuty

Oxvel knows who is on call, reads your PagerDuty incidents, and can alert on-call for every new production error.

Connect PagerDuty

  1. 1In PagerDuty, open Integrations, API Access Keys, and create a read-only key.
  2. 2For Oxvel to alert on-call, open your service, go to the Integrations tab, add an Events API V2 integration and copy its integration key.
  3. 3In « Paramètres, Connecteurs » (Settings, Connectors), click Connecter (Connect) next to PagerDuty and paste the API key, plus the integration key if you have it.

EU accounts (api.eu.pagerduty.com) are detected automatically.

What Oxvel reads

  • Incidents, open or resolved, with the service, urgency and who is handling them.
  • Incident details, including the timeline, the team's notes and the content of the alerts.
  • Who is on call right now, and until when.

Alert on-call

With the integration key, every new production error (captured by Oxvel or Sentry) triggers a PagerDuty alert, with Oxvel's analysis if it's ready and a link to the incident. The alert closes automatically when the error is resolved in Oxvel, or when Oxvel sees that the fix holds in production. The Slack alerts message also says who is on call.

Analyzed alerts

When an incident is triggered (except alerts sent by Oxvel itself), Oxvel analyzes it automatically within 15 minutes. It reads the data around that moment, the errors in production, the latest deployments and the code, then posts its diagnosis to the Slack alerts channel, to Discord and by email. This requires « Analyser les nouvelles erreurs tout seul » (Analyze new errors automatically) in your (at most 5 analyses per day).

Without an integration key, Oxvel only reads. It doesn't alert anyone.

On this page