Uptime monitoring

1. Add a monitor

Open Numo Pulse and click Add monitor. Enter the URL and method (GET, POST, or HEAD), a check interval, and a timeout. Numo requires you to testthe endpoint first — you'll see the response time, resolved IP, headers, and TLS certificate before saving.

2. What counts as healthy

By default a monitor is up when it returns the expected status code (200 by default). Under Advanced checks you can tighten that:

• Content assertion — require the response body to contain a string. A 200 with the wrong payload is marked down.
• Latency threshold — get a slowalert when a healthy response is slower than your threshold, and a recovery when it's back under.
• TLS expiry— Numo reads the served certificate every probe and warns you when it's within your chosen number of days of expiring.

3. Alerts

Down, recovered, slow, latency-recovered, and TLS-expiring events are delivered to your workspace's alert channels — the same email, Slack, Discord, and webhook channels Beat uses. See Alert channels to connect one. Snooze a monitor during known work to mute it temporarily.