Opyntel
Netlify

Netlify monitoring: all your Netlify sites in one dashboard

Netlify Observability shows one site at a time and has no alerting. Opyntel’s Netlify monitoring shows every site at a glance, plus the other systems you run, and alerts when a deploy fails or a site stops answering.

See how it works
Built in vs Opyntel

Netlify on its own, and Netlify with Opyntel

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

Every site at a glance

On Netlify

Netlify Observability shows requests, bandwidth, functions, edge functions and slowest URLs for one project. Its own comparison table describes cross-project analysis as a single-site view only.

With Opyntel

Opyntel lists every Netlify site with its latest deploy and its state in one table, Netlify plus the other systems you run. Failed deploys and sites that stop answering sort to the top, so you see the full list of your services at a glance.

Deploys on one timeline

On Netlify

Netlify sends deploy notifications for events such as deploy started, succeeded and failed, by email on Pro and Enterprise, Slack, webhook or a Git provider. You enable them per project in its configuration.

With Opyntel

Opyntel puts every deploy of every Netlify site, with its commit and state, on one activity timeline next to the deploys from your other platforms. When something breaks, you see what shipped just before, wherever it shipped.

Alerts when it goes down, and when it recovers

On Netlify

Netlify Observability lists alerting as not available. Netlify recommends a log drain to a third-party monitoring tool when you need alerting.

With Opyntel

Opyntel checks each site's public URL and alerts when it stops answering or a deploy fails, 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 site is back.

Response time of every site

On Netlify

Observability ranks the slowest URLs of a project, and Netlify lists regional latency among the data a log drain carries. Netlify offers no programmatic access to observability data.

With Opyntel

Opyntel measures the response time of each site from its public URL and shows p50, p95 and p99 per site. Your Netlify front ends sit next to the latency of the back ends they call on other platforms.

History

On Netlify

The Observability time window is 24 hours on Free and Personal, 7 days on Pro and 30 days on Enterprise. For longer retention, Netlify recommends a log drain to a third-party tool.

With Opyntel

Opyntel keeps the deploys of every site and the uptime and response times it measures for 30 days on the free plan, a year on Pro and unlimited on Enterprise, whatever your Netlify plan.

Setup

How to set up Netlify monitoring with Opyntel

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

  1. Create a Netlify personal access token
    Under Applications in your Netlify user settings, select New access token, give it a name and an expiration date, and copy it: Netlify shows it once.
    Create a Netlify personal 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 Netlify as a source and paste the token. Opyntel lists your sites and their deploys and checks each site’s public URL.
  4. See Netlify in one dashboard
    Netlify 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

Netlify questions, answered

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

Netlify issues a Let’s Encrypt certificate once the custom domain’s DNS points at Netlify; a missing record, or a CAA record that leaves out Let’s Encrypt, blocks it. Opyntel alerts before a certificate expires. Why an SSL certificate expired or failed.

Check netlifystatus.com first. If every site you host fails together it is the platform; if one site’s functions fail alone it is that deploy. Opyntel checks your public endpoints from several regions and alerts when one goes down.

Your plan, plus usage such as bandwidth, build minutes and function calls, counted as credits on the credit-based plans. The usage page of your team shows what each site uses.

A synchronous function stops at a fixed execution limit and the request fails; long work belongs in a background function, which can run much longer and answers at once. Opyntel measures your site’s response times, so a function that slows down shows up before it times out.

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