Vercel
If you deploy on Vercel, the Vercel integration is the fastest path to release attribution. It does three jobs:
- OTel sink — routes Vercel's OpenTelemetry Collector output into your tenant, so you don't have to ship your own exporter config per environment.
- Deploy webhooks — publishes a change event every time a Vercel deployment succeeds.
- Rollback deep-link — the Doctor page links to the Vercel rollback dialog for a suspected-bad release.
Install
- In the GreenSlope dashboard, go to Settings → Integrations → Vercel.
- Click Install on Vercel and authorise for the team/projects you want instrumented.
- Pick the projects to enable. Each project is mapped to a GreenSlope service — the name defaults to the Vercel project name and can be edited.
OTel sink
Once installed, GreenSlope is registered as the OTel destination for
the project. Your next.config.ts doesn't need the manual
instrumentation.ts from the Next.js quickstart
— the Vercel-managed collector handles export.
Deploy webhooks
When a Vercel deploy finishes, we receive a webhook and translate it
into a deploy change event. The mapping:
| Vercel field | GreenSlope field |
|---|---|
deployment.meta.githubCommitSha | release_id |
deployment.target (production, preview) | environment |
deployment.meta.githubCommitAuthorLogin | actor |
deployment.meta.githubPrNumber | pr |
Preview deploys are recorded as change events but scoped to
environment=preview, so they don't trigger production SLO regression
checks.
Deploy REST API
For non-Vercel deploy paths (a worker deployed via GitHub Actions, say), post directly to the REST API — see Change events.
Uninstall
Remove from Settings → Integrations → Vercel → Uninstall, or from the Vercel dashboard's integration page. Uninstalling stops new webhooks but keeps historical change events. We retain them for 90 days per tenant limits.
Related