A TCP monitor checks whether an endpoint accepts a connection on a chosen port. Use it for a service that is intentionally reachable by the monitoring system, and pair it with an application check when connection availability alone is insufficient.
01 Create the port check
- Confirm the service hostname, actual listening port and expected public accessibility with its administrator. Do not expose a private database or management interface merely to add external monitoring.
- In 360 Monitoring, open Websites > Add website and select the TCP check type.
- Enter the supported target and port, then use a descriptive name such as the service, environment and purpose.
- Set the available interval, timeout, sensitivity and monitoring location to fit the service. Select the people responsible for investigating failures.
- Start monitoring and confirm successful checks. If the service is restricted, have the administrator permit only the required current monitoring sources through an appropriate narrow rule.
- Document what the check proves and add an application-level check where needed, such as HTTPS content for a customer portal.
Common questions
Does a successful SMTP port check mean email is delivered?
It establishes connectivity to that port. Authentication, message acceptance, queue processing and final delivery require separate evidence.
Why does the port work from my office but fail from the monitor?
Check source-address restrictions, regional filtering and whether you are using a private network route. Compare the exact endpoint and timestamp before changing firewall policy.
Should I monitor an IP address or hostname?
Use the hostname when DNS is part of the service customers depend on. A deliberate IP check can help isolate a server, but it will not detect an incorrect public DNS change.