Logs, metrics and alerts

Observability in the sidebar shows how everything in your organisation is doing: metrics over time, the events Plexivo records about your resources, alerts, incidents and measured availability.

Metrics#

Plexivo measures every resource once a minute and keeps the measurements for 14 days. Choose 1h, 24h, 7d, 14d or a custom range; each point on a chart is the average for its slice of the range.

The Advisor tab points out resources whose latest CPU, memory or storage reading in the last day is at 80% or more of what they reserve, so you can resize before it matters.

Logs#

How far back you can search events depends on your plan. By default it is 1 day on Developer, 7 on Startup, 28 on Business and 90 on Enterprise.

Alerts#

An alert opens when something needs your attention: for example, a Plexivo Postgres database that stops serving, or a TLS certificate on one of your custom domains that fails its check or expires within 30 days. It closes on its own when the resource recovers. Open alerts are in Observability → Alerts, where owners and admins can Acknowledge them.

Get notified#

1. Add a channel. In Observability → Alerts, open Notification channels. Under New notification channel, name it and choose Email, for a member of your organisation, or Webhook, for an https:// address. Choose Save channel, then Send test to check it.
2. Add a rule. Open Rules. Under New alert rule, enter a rule name, choose one resource or All resources, the lowest level that should notify, and the channel. Choose Save rule.

Plexivo notifies the channel when an alert opens and when it is resolved. Each channel receives up to 30 messages an hour. The channel list shows when each one last delivered or failed.

Signed webhooks#

Plexivo sends a POST with a JSON body:

{
  "type": "alert.opened",
  "alert": {
    "state": "opened",
    "severity": "critical",
    "resource": "orders-db",
    "message": "Database orders-db is not serving: its primary is unavailable.",
    "at": "2026-10-27T09:14:00Z"
  }
}

type is alert.opened or alert.resolved, and alert.test for a test; state matches it. severity is critical or warning. Requests come from the user agent Plexivo-Alerts/1.

Every request carries an x-plexivo-signature header: t=<unix seconds>,v1=<signature>. The signature is the lower-case hex HMAC-SHA256 of t, a full stop and the raw body, keyed with the channel’s signing secret. The secret is shown once, when you create the channel. Check the signature, and reject old timestamps, before you trust a request:

import crypto from 'node:crypto';

function verify(header, rawBody, secret) {
  const { t, v1 } = Object.fromEntries(header.split(',').map((p) => p.split('=')));
  if (Math.abs(Date.now() / 1000 - Number(t)) > 300) return false;
  const expected = crypto.createHmac('sha256', secret).update(`${t}.${rawBody}`).digest('hex');
  return expected.length === v1.length &&
    crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(v1));
}

Answer with any 2xx status within 5 seconds. Plexivo does not retry a failed delivery, so keep your endpoint fast and send the work to a queue.

Email notices#

In Settings → Notifications, owners and admins choose whether the organisation’s owners and admins receive Spend budget alerts and Service incident notices, which cover incidents and how maintenance ended. Both are on until you change them. Security, payment, renewal and account notices, support access notices and the announcement and reminder of scheduled maintenance are always sent.

Incidents and availability#

• Incidents lists the incidents that affected your organisation, with their updates and how they were resolved.
• SLA & Uptime shows measured availability and your availability commitment. See Service Level Agreement.
• Platform-wide status is at status.plexivo.io.