All monitor types
Basic monitoring

UDP monitoring

Datagram probe — UDP has no handshake, so send a message and match the reply.

Every UDP monitor runs on the same spine as the rest of PulseTrace — probed from each region you pick, scored on every check, and streamed into one timeline where incidents open on their own, anomalies surface without a threshold to guess, and reports are generated for you. Point it at a target, choose an interval, and it's watched.

What each check verifies

  • Local socket opens
  • Optional: send a datagram and match a substring in the reply

The panel on the right is the real create-monitor screen — it fills itself in with a UDP example, exactly what you'd type.

When to use it

For UDP services where a request/response pair proves liveness — DNS servers on 53, NTP, syslog receivers, game servers, custom telemetry. You provide the payload to send and the response to expect.

What an alert looks like

ntp.internal:123 is DOWN — no response within 2 s from eu, asia.

Plan availability

Every plan, including Free.

Compare plans →

Questions about UDP monitoring

Why do I need to provide a payload?
UDP has no handshake, so the only way to prove a service is alive is to send something it will answer. The monitor sends your bytes and matches the reply.