Skip to content

Alerts

Alerts notify you when something needs attention. numbrs evaluates alert conditions on every metric ingestion and on each uptime/relay check. When a condition triggers, you get a notification.

Downtime alerts — Fire when a relay or uptime monitor fails. Triggered on the first failed check. Can be configured to remind you if the outage is ongoing.

Threshold alerts — Fire when a custom metric or relay metric crosses a value you set. Use these for things like “alert when event latency exceeds 500ms” or “alert when daily Claude cost exceeds $10”.

  1. Click Alerts in the sidebar, or go to a specific monitor or metric and click Add Alert
  2. Choose the condition:
    • Above — fires when the value exceeds the threshold
    • Below — fires when the value drops under the threshold
  3. Set the threshold value
  4. Choose notification channels
  5. Save

For downtime alerts, you also choose:

  • On first failure — fires immediately
  • Reminder interval — how often to re-notify if the issue persists (e.g., every 30 minutes)

In-app — Alerts appear in the Alerts section of the app. Available to everyone.

Email — Sent to your account email. Downtime alerts typically arrive within 30 seconds of detection.

Webhook — POST a JSON payload to any URL. Use this to integrate with Slack, Discord, ntfy.sh, or any custom handler.

Downtime alert:

{
"alert_type": "downtime",
"monitor_name": "My Relay",
"monitor_url": "wss://relay.example.com",
"status": "down",
"error": "Connection timeout",
"started_at": "2025-03-25T20:00:00Z"
}

Threshold alert:

{
"alert_type": "threshold",
"metric": "relay.event_latency",
"value": 823,
"threshold": 500,
"condition": "above",
"triggered_at": "2025-03-25T20:00:00Z"
}

Example: Discord notifications via webhook

Section titled “Example: Discord notifications via webhook”
  1. In your Discord server, go to channel settings → Integrations → Webhooks
  2. Click New Webhook, name it numbrs, copy the webhook URL
  3. In numbrs, add a webhook alert channel with that URL
  4. Click Test — a test message should appear in Discord

Every alert that fires is logged with the time, metric/monitor, value, and which notification channels were used. Find this under Alerts → History.

A few things worth keeping in mind:

  • For latency thresholds, require the condition to persist for 2–3 consecutive checks before firing. A single slow response isn’t an incident.
  • Set reminders conservatively. Getting paged every 5 minutes while something’s already broken will make you disable alerts entirely.
  • Start with fewer alerts than you think you need. Add more when you discover what actually requires attention.