Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt

Use this file to discover all available pages before exploring further.

TCP monitors verify that a host is accepting connections on a specific port. Use them for databases, message queues, mail servers, and any service that listens on a TCP port but doesn’t speak HTTP.
Define this in code. YAML format · Terraform

​
When to use TCP monitors

  • Database connectivity — verify PostgreSQL (5432), MySQL (3306), or Redis (6379) is accepting connections
  • Message queue health — check RabbitMQ, NATS, or Kafka broker ports
  • Mail servers — verify SMTP (25/587) or IMAP (993) ports are open
  • Custom services — any non-HTTP service that accepts TCP connections

​
How it works

  1. DevHelm opens a TCP connection to the specified host and port from each probe region
  2. If the connection succeeds within the timeout, the check passes
  3. Response time is measured from connection initiation to completion
  4. Assertions evaluate the connection result

​
Quick example

devhelm monitors create \
  --name "PostgreSQL" \
  --type TCP \
  --host db.example.com \
  --port 5432 \
  --frequency 60 \
  --regions us-east,eu-west

​
Next steps

Configuration

Host, port, timeout, and assertion fields.

Monitoring overview

Compare all six monitor types.