Build a structure that remains easy to scan
When one person is responsible for many client services, naming matters more than dashboards full of charts. Give each checker a short display name that says what the service is. Keep the URL or server as the technical target underneath it.
Enable groupings in Settings, then use one consistent model: one group per client, or broader groups such as Hosting, Infrastructure, and Internal services. Avoid mixing both models unless the list is small enough to remain obvious.
Northwind can contain Public website, Customer portal, and Mail submission. The collapsed group shows its status before any checker is opened.Add many checkers without repetitive forms
Use Bulk insert for a new hosting server, a client onboarding, or a monitoring migration. Website and port rows can be pasted together as CSV or tab-separated data. Include names and groups in the import so the dashboard is organized immediately.
- Start with a small batch and use the provided field-name line.
- Keep one checker per row.
- Confirm permission to monitor every target.
- Review the validation result before correcting only the rejected rows.
For ongoing automation, create an API key in Settings and use the JSON API to list, create, update, test, or delete checkers.
Choose alerts based on responsibility
Use one email per state change for services that can wait until normal support hours. Enable repeat alerts every minute only for targets where the responsible person wants to be reminded until recovery.
The consecutive-down setting controls when the target changes to DOWN. A threshold of one gives the fastest state change. Two or three observations can be more comfortable for remote services with occasional network loss. The display name is included in alerts, so the recipient does not need to interpret a long URL.
Keep useful records after recovery
Open a checker to review DOWN and UP intervals, protocol details, recovery times, and captured webpage diagnostics. Add a short description of the cause and corrective action while the event is still fresh.
Checker lists and complete histories can be exported to XLSX. The combined workbook keeps checker configuration and incident history on separate sheets, which is useful for a client review or an internal maintenance record.