Browse documentation
Adding a service check
↩ Services
A service represents an application running on one of your servers. Adding one lets you document it and, optionally, monitor its health.
The Services list
Select Services in the sidebar. The list shows each service with its Name, Type, Server, Site, Groups, and Status (a coloured dot: Running, Stopped, Degraded, or Unknown). Use the search box and the All sites / All groups filters to narrow it down.
Adding a service
- Select Add service.
- Complete the form:
| Field | Required | Notes |
|---|---|---|
| Name | Yes | e.g. nginx |
| Site | No | Filters the server list |
| Server | Yes | The server this service runs on |
| Type | No | Web, Database, File Share, DNS, DHCP, VPN, or Custom |
| Status | No | Only set manually if monitoring is off |
| Redundancy | No | None, Active/Passive, Active/Active, or Load Balanced |
| Frontend URL | No | Public URL, if the service has a front end |
| Health Check URL | No | Endpoint to check for HTTP monitoring |
| Linked application | No | Link to a Software record for version tracking |
| Description | No | Free-form notes |
- Select Add service.
Discovering services from a server
Instead of adding services one by one, you can discover them from the server side. On a server's Services tab, agentless (SSH / WMI) servers offer a Discover services button that scans the host and lets you pick which detected services to start tracking — see Viewing packages and services.
Recording ports and access methods
On a service's detail page you can also document service ports (port, protocol, direction) and access methods (how to reach it — direct, VPN, proxy, jump host, with protocol and URL). These are reference details, not health checks.
Notes & tips
- Set up health monitoring after creating the service so its status updates automatically.
- Group related services (see Linking services to servers) to filter large lists quickly.