Opyntel
Vercel

Vercel monitoring: all your Vercel projects in one dashboard

Vercel keeps 12 hours to 3 days of observability data unless you add Observability Plus. Opyntel’s Vercel monitoring shows every project at a glance, plus the other systems you run, with a year of history on Opyntel Pro. Some features need a Vercel Pro plan or higher.

See how it works
Built in vs Opyntel

Vercel on its own, and Vercel with Opyntel

Feature by feature, the biggest gaps first: what Vercel gives you, and what you get in one dashboard with Opyntel.

Every project at a glance

On Vercel

Vercel Observability works at the team level and the project level, and functions, CDN requests and external APIs show at both. Function latency and breakdowns by path need Observability Plus, and the view covers only what runs on Vercel.

With Opyntel

Opyntel puts the full list of your services in one table: every Vercel project with its requests, error rate and duration, Vercel plus the other systems you run. Down and degraded services sort to the top, so you see it all at a glance without switching dashboards.

Latency percentiles and error rate

On Vercel

Without Observability Plus, Vercel Functions show no p75 latency and no breakdown by path. Observability Plus, on Pro and Enterprise, adds p75 latency, sorting by p75 and a breakdown by path and route.

With Opyntel

Opyntel reads function error rate and p50, p95 and p99 duration per project from Vercel drains, which Vercel Pro and Enterprise teams can set up without Observability Plus. They sit in the same table as the latency and error rate of your services on other platforms, so a slow API and the front end that calls it read side by side.

Alerts when it goes down, and when it recovers

On Vercel

Vercel alerts need a Pro or Enterprise team with Observability Plus. They fire on usage anomalies and on 5xx error spikes more than 4 standard deviations above the 24-hour average, by email, Slack or webhook.

With Opyntel

Opyntel alerts when a project's error rate passes your threshold, out of the box on every plan, and on any duration or error threshold you set per project on Pro and up, by email, Slack or SMS depending on your plan. Every alert notifies when it fires and again when it resolves, so you know when the project has recovered.

History

On Vercel

Observability keeps data for 12 hours on Hobby, 1 day on Pro and 3 days on Enterprise. Observability Plus, billed per million events, keeps 30 days.

With Opyntel

Opyntel keeps the requests, errors and duration your Vercel drains send for 30 days on the free plan, a year on Pro and unlimited on Enterprise, with or without Observability Plus. You can compare this week with last quarter without paying for longer retention on each platform.

The total cost of your app

On Vercel

The Usage page shows usage for all projects in the account, with a breakdown by project and the projected cost of each item. Spend Management, on Pro and on Enterprise with Flexible Commitment, triggers notifications, a webhook or a pause when spend reaches an amount you set.

With Opyntel

Opyntel reads actual spend per project from Vercel billing on Pro and adds it to the bills of the other systems you run, so the total cost of your app is one number at a glance. Monthly budget alerts and forecasts across every platform come with Enterprise.

Setup

How to set up Vercel monitoring with Opyntel

Vercel monitoring in four steps: from Vercel to one dashboard with everything else you run.

  1. Create a Vercel access token
    Under Tokens in your Vercel account settings, create a token scoped to your team. Vercel tokens cannot be made read-only, so Opyntel only sends GET requests; spend also needs a role with billing access.
    Create a Vercel access token
  2. Sign in to Opyntel
    Open your Opyntel dashboard and add a source. Accounts start from the waitlist, so join it to get yours.
  3. Paste the token in your dashboard
    Add Vercel as a source, paste the token and pick the team. For requests, errors and duration, add the drain your dashboard shows to the team’s drains.
  4. See Vercel in one dashboard
    Vercel monitoring lands next to the other platforms you run: every service and server sits in one dashboard, down and degraded first, with default alert rules on from the start.

Don’t see your platform? From your Opyntel account you can request an integration with more platforms. Until then, and tell us which one you run on.

FAQ

Vercel questions, answered

Short answers; some link to a guide that goes into detail.

Vercel logs each invocation as a request to the cron path, but it neither retries nor alerts. Opyntel alerts when a scheduled run fails or does not happen. Why a Vercel cron job did not run.

No. Vercel shows P75 for functions, and only with Observability Plus. Vercel P95 and P99 latency percentiles.

Check vercel-status.com first. If every project you host fails together it is the platform; if one project’s functions return errors alone, it is that deployment. Opyntel checks your public endpoints from several regions and alerts when one goes down.

The Logs tab of a project shows runtime logs from functions and middleware, filtered by level, path and deployment, and vercel logs <deployment-url> streams them in a terminal. Log drains send them elsewhere if you need history.

Function invocations and duration, data transfer, image optimization and build minutes, on top of the per-seat price on Pro. Opyntel shows spend per project next to your other platforms with Opyntel Pro.

The alerts your platform doesn’t send.

One dashboard for everything you run, with the alerts your platforms leave out. Read-only, nothing to install in your apps.

See how it works