Skip to main content
Open console

Monitoring and metrics

What is measured on your environments, where you can see it, and how availability is watched.

6 min read

Two things are watched without any setting up: how hard each environment is working, on its Metrics tab, and whether production is answering. The second sends an availability notification.

The Metrics tab

Every environment has one. It shows the last 15 minutes, hour, 24 hours, 7 days, 30 days or 90 days, 24 hours to begin with.

CPU, memory and disk

Measured How often Kept
CPU and memory Once a minute 90 days
Disk Every 15 minutes 90 days

Each line is drawn against what the plan allows: the top of the chart is your allocation, not the machine's size. On a shared machine, a line near the top is this environment using its allocation, whatever the rest of the machine is doing.

Each figure shows its peak and average over the window. Disk shows how much it has changed. A disk passing 80% also sends a notification.

"The machine has gone quiet" under a reading means nothing has been reported for a while. That is usually a machine that is down or being rebuilt: check the environment's Activity.

For history beyond 90 days, send your logs somewhere that keeps them.

Traffic

Counted at the edge, from every request that reached the environment.

Figure What it is
Requests Every request your application answered
Errors Responses of 400 and above, together — not split into 4xx and 5xx
p95 response The time 95% of requests were answered within
Estimated bandwidth Bytes in and out through the proxy
Most visited The ten busiest paths over the last 24 hours, or over the whole window on 30 and 90 days. The platform's own uptime check, /.well-known/vallic-health, is counted in Requests but never listed here

The lines are per minute over the last hour, per hour up to 7 days, and in longer steps over 30 and 90 days. The p95 tells a slow site from a fast one; it is not accurate enough to benchmark a change of a few milliseconds.

Errors count 404s. A spike of them is usually a crawler or a scanner, not your site breaking. The busiest paths list is the quickest way to tell which.

What the edge refused is counted apart, in none of the figures above. It is listed under the paths, by reason:

Refused Because
Probes for files no site serves The probe guard, what is refused by default, or your own probe rules; the paths they asked for are listed as Probes denied
No user agent A request that named no user agent, where the project refuses those
SQL injection A scanner's SQL injection in the address, where the project refuses it
Blocked addresses An address on the project's block list
Blocked user agents A user agent on the project's block list
Outside an allow list An address an environment's allow list leaves out
Over the rate limit More requests than the project's rate limit lets one visitor make (429)
Asked for the password A request without the environment's password (401) — every reviewer's first visit is one

A 429 or 401 your application gives itself is a request like any other.

Where a project counts SQL injection rather than refusing it, the card says how many requests carried it. They reached your site and are in the figures above. Use the number to judge whether refusing them would turn anybody real away.

Who is asking lists the clients that sent the most requests over the window, refused or served: browsers, search engines, AI crawlers, SEO tools, link previews, uptime monitors, scripts. Only that category is kept, never the user agent itself. A crawler that calls itself a browser is counted as a browser. To turn one away, add its name under Blocked user agents on the Edge tab.

Behind a CDN, this is what reached us, not what your visitors asked for. Requests the CDN answered from its cache are not in these numbers; the CDN tab shows what it served.

Is production answering

Every running production environment is requested once a minute at its primary domain: your own once you have made one primary, the platform hostname before that. A redirect is an answer and is not followed.

  • Any answer below 500 counts as up, a 404 on the home page included.
  • A check that fails is asked again a couple of seconds later, and only counts if that fails too.
  • After three failures in a row, about three minutes, the environment is counted as down and an availability notification is sent. It says what the last check got: the status it answered, or that it did not answer and why.
  • When it answers again, a second notification says so.

Staging and development environments are not watched this way.

This check is made from one place. Its notification reaches whoever you chose under Notifications. It is not the measurement your uptime SLA is judged on.

Availability for the SLA

Every project's production is committed to an uptime figure. Availability is measured separately, from more than one location, against your own domain, not the machine.

Your own downtime is marked as yours. Your site is behind its maintenance page while a deploy runs, for a few minutes after it finishes, and while you have switched it offline. These windows are recorded, but they do not count against the SLA and are not credited. Only production is measured for credits: staging and development carry no commitment.

The tiers, the figures and the credits are on Projects; the terms are in the SLA itself. The measurements are not shown in the console.

What is not here

  • No application monitoring of our own. Nothing inside your code is timed or traced by the platform. You can send traces to a service you use: see below.
  • No custom checks or thresholds. You cannot point the availability check at a different path, or change when it alerts.
  • No per-machine charts. You see each environment against its allowance, not the machines underneath.

Application monitoring with your own account

In the log forwarding card on the project's Configuration page, Application monitoring lets you choose an agent from your team's integrations. It needs the Admin role, and a plan that includes log forwarding.

Integration What happens
New Relic On a PHP stack, the New Relic extension is switched on in your application, cron and worker containers, with your licence key, distributed tracing on, and the environment's name as the application name. Nothing to install.
OpenTelemetry (OTLP) The standard OTEL_* variables are set — service name, exporter, protocol http/protobuf, endpoint and your authentication header — and on PHP the OpenTelemetry extension is switched on. Your application must include an OpenTelemetry SDK to produce anything.

Datadog is not offered as an agent; send to Datadog through OTLP instead.

  • New Relic is for PHP. On a Node or Go application it sets variables nothing reads; use OpenTelemetry with your language's SDK there.
  • The OTLP endpoint is passed as written. The same integration's endpoint is also where your logs go, and OpenTelemetry SDKs add /v1/traces to it: check where your traces actually arrive.
  • It is sent when you save, to every machine the project runs on.

Next

  • Notifications — where the availability alert goes
  • Logs — the detail behind a spike in errors