UDP Port Monitor

The UDP monitor in updu enables connectionless health checking by blasting a datagram string to an endpoint, bypassing the TCP handshake overhead and checking if your service answers back.

Configuration Options

When setting up a UDP monitor, you can configure the following options:

Basic Settings

• Name: A descriptive name for your monitor.
• Group: Optional group assignment for organizing monitors.
• Interval (seconds): How frequently updu should perform the check.
• Timeout (seconds): The maximum time updu will wait for a response datagram before returning a timeout error.

UDP Specific Settings

• Hostname: The IP address or domain name of the app (e.g., 192.168.1.5).
• Port: The UDP port the server is listening for traffic on.
• Send Payload: (Optional) An ASCII string detailing the payload content to insert into the outgoing UDP UDP datagram. e.g. \xff\xff\xff\xffTSource Engine Query\x00 for a Steam gameserver.
• Expected Response String: (Optional) An ASCII string verifying updu receives a return packet payload from the server containing this exact string.

Example Use Cases

• Dedicated Game Servers: Checking if older source games like Minecraft, Counter Strike, and TF2 are successfully accepting traffic and player queries.