Choose the right check
| Type | Target and configuration | What it establishes |
|---|---|---|
| HTTP / HTTPS | Full URL; optional method, headers, keyword, and Basic Auth | Whether a web endpoint passes its HTTP and content checks. |
| TCP | Host and TCP port | Whether the service accepts a TCP connection. |
| ICMP | Host | Whether the host answers an ICMP reachability check. |
| DNS | Name, record type, and optional expected value | Whether the selected DNS record resolves as expected. |
| Minecraft | Minecraft server address | Whether the game server responds to its protocol check. |
Use targets reachable from the managed monitoring infrastructure. A service reachable only from your laptop, VPN, or private network may not be reachable by a managed probe. Target validation may reject private or reserved addresses.
HTTP and HTTPS checks
Create or edit an HTTP monitor, enter its full URL, and configure only the options your service needs.
- HTTP Method: choose the request method your health endpoint supports. Use a dedicated health endpoint where possible.
- Custom headers: enter headers in the format requested by the form. Use them for required application headers or authorization.
- Keyword: select Must Be Present or Must Be Absent. Use stable response text; dynamic timestamps or user-specific content make poor checks.
- Basic Auth: select the authentication type and supply the username and password for a dedicated monitoring identity.
- SSL monitoring: enable certificate monitoring for HTTPS endpoints when you want certificate problems included in monitoring.
Do not point repeated POST or other action methods at an endpoint that creates orders, sends messages, or changes business data. A monitoring request runs repeatedly.
Infrastructure checks
For TCP, supply the actual service port. An open port alone does not prove the application behind it is functioning correctly. For ICMP, confirm the host and its firewall permit ICMP replies; a blocked reply can look like a failed host.
For DNS, select a supported record type: A, AAAA, CNAME, MX, TXT, or SRV. Add an expected value when resolution alone is insufficient. Allow for DNS changes and propagation when investigating a mismatch.
Interval, locations, and organization
Give the monitor a clear name, choose its interval, then optionally add a group and tags. Free uses five-minute checks. Pro enables faster checks and multiple regions; only available locations can be selected. See monitoring locations.
Leave Show on public status page off unless the monitor should be visible to visitors. Public visibility is separate from whether your organization has enabled its public page.
Edit, pause, and remove
Open an existing monitor's edit control to adjust its configuration. Verify a subsequent check after changing a target, credential, keyword, or interval. Pause a monitor when you deliberately want to stop checks; use a maintenance window for planned work that should suppress alerts during a defined period.
Deleting a monitor is permanent. Consider exporting required history first if your plan allows it, and review Nexus Point dependencies and alert routes that refer to it.
When a check fails
Read the error and timestamp on the monitor detail page. Check the URL or hostname, port, credentials, response content, and location availability. If the check fails from the managed probe but works locally, compare network access and firewall behavior. See troubleshooting.