TCP port monitoring

TCP port and network service monitoring

Monitor whether a database, gateway or custom network service is reachable on the expected port. RMON checks connectivity from selected locations and alerts when the service stops responding.

What you gain Monitor the right portMeasure connection timeLocate connectivity failures
Why it matters

Check the service endpoint your applications depend on

A host can answer Ping while an important application port is unavailable. RMON resolves the service name, attempts the configured TCP connection and records whether a usable endpoint responded.

A successful connection confirms that the port accepts connections. It does not validate the application response. Multi-location checks show whether reachability differs by network path.

01

Monitor the right port

Check the actual service endpoint instead of relying only on host availability.

02

Measure connection time

Track connection timing and alert when the response-time threshold is exceeded.

03

Locate connectivity failures

Compare results and connection timing from different monitoring locations.

RMON capabilities

What this solution can cover

  • DNS-name or IP-based TCP checks
  • IPv4 and IPv6 connectivity
  • Sequential attempts across resolved addresses
  • Name-lookup and connection timing
  • Retries and response-time thresholds
  • Multi-location alerts and history
Practical workflow

Create a TCP service check

  1. 01

    Enter the endpoint

    Choose the service DNS name or address and the TCP port it should accept.

  2. 02

    Set the schedule

    Choose how often to connect and how long to wait before a timeout.

  3. 03

    Choose locations

    Assign agents or regions that use the relevant network paths.

  4. 04

    Set thresholds and alerts

    Configure retries, timing limits, notification channels and a runbook.

Open tcp monitoring guide
Questions, answered

Common questions about tcp port monitoring

Can RMON monitor any TCP port?

RMON can attempt a connection to the configured TCP endpoint and port, subject to normal network access.

Does a successful TCP check confirm application health?

It confirms that the port accepts a connection. Use an HTTP, SMTP or RabbitMQ check when you need to test the application protocol.

Does RMON support IPv6 TCP checks?

Yes. TCP checks can use IPv4 and IPv6 addresses returned for the service name.

Self-hosted monitoring with RMON

Know what failed before users have to report it.