TCP Port Monitoring
Monitor TCP services, databases, queues, and infrastructure connectivity.
Alertum TCP monitoring opens a socket connection to your host and port on defined intervals, verifying that services are reachable and responding. Incidents open immediately when connectivity fails.
How it works
TCP monitoring opens a socket connection to a host and port on defined intervals, verifying the service is reachable and responding. Incidents open when connectivity fails or response exceeds configured thresholds.
Core capabilities
- ·TCP connectivity and port availability checks
- ·Response time threshold monitoring
- ·Multi-service infrastructure coverage
- ·Incident creation on connectivity failure
Assertions and thresholds
- ·TCP connection success assertion
- ·Maximum connection response time threshold
- ·Port reachability validation
Typical use cases
- ·Database host reachability monitoring (PostgreSQL, MySQL, MongoDB)
- ·Message queue and broker connectivity checks (RabbitMQ, Kafka)
- ·Internal microservice TCP health validation
Frequently asked questions
What ports can TCP monitoring check?
Any TCP port — including database ports (5432, 3306), message queues (5672), Redis (6379), SMTP (25, 587), and any custom internal service port.
How is TCP monitoring different from ping monitoring?
Ping monitoring uses ICMP to check host reachability. TCP monitoring verifies that a specific service port is accepting connections, which is more precise for service health.
Can I monitor internal services?
TCP monitoring works for any host reachable from Alertum's monitoring infrastructure. Public hosts and exposed ports are monitored directly.
Is TCP monitoring useful for database monitoring?
Yes — TCP monitoring verifies database host connectivity and detects port failures quickly, as a lightweight complement to query-level health checks.
Related features