Monitoring
Port monitoring
Is the port open and completing a handshake, for the services that have no HTTP to check.
Free plan with 20 monitors. No card.
What it checks
Port monitoring
A database, a mail server or a VPN endpoint has no page to fetch. The port answering is the whole signal, and it is the one that goes quiet first.
Anything on a private subnet is checked by an agent instead, from inside.
- A TCP connection to the host and port you name, from every assigned location.
- Handshake time, recorded per check.
- Any port: 5432, 6379, 25, 3306, 1194, whatever the service listens on.
It comes with the rest of the platform
Every monitor type shares the same alerting, the same status pages and the same map: escalation with on-call hours, a public status page, checks from independent networks, and agents for anything the internet cannot reach.
Questions
- Does it send anything to the port?
- No. It opens a connection, measures the handshake and closes. Nothing is written to the service.
- Can I monitor a database directly?
- The port, yes, from anywhere. Query timing and disk figures come from an agent on the machine.