Create a monitor
Create a monitor in Servor step by step — pick a monitor type, set the check interval, and start tracking uptime for any endpoint or server.
A monitor watches something for you — a website, a port, a domain, an SSL certificate — and checks it on a schedule so you find out about problems before your users do. This page walks you through creating your first monitor, choosing the right type, and setting a sensible check interval.
If you haven't connected a machine yet, you can still monitor any public URL or host. To also collect CPU, RAM and disk metrics, add a server first.
Create a monitor
Open Monitoring → New monitor
From the dashboard, go to Monitoring and click New monitor — open Monitoring in Servor. Creating monitors requires an admin or owner role — see roles and permissions if the button is hidden.
Pick a monitor type
Choose what you want to check: an HTTP(S) endpoint, a TCP port, a ping, a DNS record, an SSL certificate, a keyword on a page, and more. Not sure which one fits? See monitor types for a full breakdown and examples.
Enter the target
Fill in what the type needs — a URL for HTTP, a host and port for TCP, a domain for DNS or SSL, and so on. Give the monitor a clear name you'll recognize in alerts (for example Marketing site rather than Monitor 3).
Set the check interval
Choose how often Servor checks the target. A shorter interval catches outages faster; a longer one is lighter on the target. See choosing an interval below.
Save
Save the monitor. Servor runs the first check right away, so within moments you'll see it reported as up, degraded or down. Learn what each state means in monitor status.
Set up alerts next
A monitor on its own just records status. To actually hear about problems, add an alert rule and a notification channel so Servor notifies you by email, Slack or Discord when the status changes — open alert settings in Servor.
Choosing a check interval
The check interval is how often Servor tests the target. There's a trade-off:
| Interval | Good for | Trade-off |
|---|---|---|
| Short (e.g. 30s–1m) | Production sites, customer-facing APIs | Detects outages fast; more load on the target |
| Medium (e.g. 5m) | Most services, internal tools | A sensible default for the majority of monitors |
| Long (e.g. 15m+) | Low-priority or rarely-changing endpoints | Lighter, but slower to notice a problem |
A good rule of thumb: match the interval to how quickly you'd actually want to react. If a five-minute outage of a page is fine, a one-minute interval just creates noise.
Plan limits
The number of monitors you can run depends on your plan. If you hit the ceiling, see plans and limits to raise it.
After it's running
Once a monitor is live you can:
- Watch its uptime % and history — see monitor status.
- Get notified on changes — see alerts and notification channels.
- Show it publicly by linking it to a status page component.
- Have Servor open an incident automatically when it goes down — see automatic incidents.