ICMP Monitors - DevHelm

ICMP monitors verify that a host is reachable by sending ping packets and measuring response time and packet loss. They’re the simplest form of availability monitoring — if the host doesn’t respond to pings, it’s likely down.

Define this in code. YAML format · Terraform

When to use ICMP monitors

Infrastructure reachability — verify servers, routers, and network devices respond
Network latency tracking — measure round-trip time between regions and hosts
Baseline availability — simple up/down detection when HTTP or TCP isn’t applicable
Packet loss detection — identify network quality issues

Some hosts and firewalls block ICMP. If you can’t ping a host from your machine, ICMP monitoring won’t work for it. Use TCP or HTTP monitors instead.

Quick example

devhelm monitors create \
  --name "Gateway" \
  --type ICMP \
  --url gateway.example.com \
  --frequency 60 \
  --regions us-east

monitors:
  - name: Gateway
    type: ICMP
    config:
      host: gateway.example.com
      packetCount: 5
    frequencySeconds: 60
    regions: [us-east]
    assertions:
      - config:
          type: icmp_reachable
        severity: fail
      - config:
          type: icmp_packet_loss
          maxPercent: 20
        severity: warn

Next steps

Configuration

Host, packet count, timeout, and ICMP assertions.

Monitoring overview

Compare all six monitor types.