TCP Port Monitoring
Monitor the availability of TCP ports on your servers
TCP Port Monitoring
Metoro’s TCP Port Monitoring allows you to monitor the availability of TCP ports on your servers and network services. This is useful for monitoring database connections, custom services, or any other network service that listens on a TCP port.
Features
- Simple Connection Testing: Verify that TCP ports are open and accepting connections
- Response Time Tracking: Measure and track connection response times
- Configurable Timeouts: Set connection timeouts to avoid long waits for unresponsive services
Configuration Options
Basic Settings
- Monitor Name: A descriptive name for your monitor
- Check Type: Select “TCP” for TCP port monitoring
- Host: The hostname or IP address to monitor
- Port: The TCP port number to check
- Check Frequency: How often to check the connection
Connection Settings
How TCP Monitoring Works
The TCP monitor performs a simple TCP connection check:
- Attempts to establish a TCP connection to the specified host and port
- Records the time taken to establish the connection
- Returns success (status code 200) if the connection succeeds
- Returns an error if the connection fails or times out
A successful TCP connection indicates that the service is running and accepting connections. However, it does not verify that the service is functioning correctly beyond accepting connections.
Use Cases
TCP monitoring is ideal for:
- Database Servers: Monitor MySQL, PostgreSQL, or other database servers
- Mail Servers: Check SMTP, IMAP, or POP3 services
- Custom Services: Monitor any service that listens on a TCP port
- Network Infrastructure: Verify that firewalls and network paths are open
Example TCP Monitor Configuration
Here’s an example configuration for monitoring a PostgreSQL database server:
- Monitor Name: PostgreSQL Production Server
- Check Type: TCP
- Host: db.example.com
- Port: 5432
- Check Frequency: Every 5 minutes
This monitor will check if the PostgreSQL service is accepting connections every 5 minutes by attempting to establish a TCP connection to port 5432.