UDP port monitoring support#61

Support UDP port monitoring

Planned or abandonned ?

UDP by definition is stateless, so there’s no guarantee you’d get any sort of response from a UDP port. Places where these sorts of health checks are implemented usually rely on a separate TCP check for anything UDP.

Anything that actively checked UDP would need to be very protocol/application specific, so VoIP, a particular VPN etc. Quite specific for each use-case, not really feasible

It’s entirely feasible. Leave that on the user like every other service that does this.

Hi all, we are considering this feature already.
However, we are not sure what would you want to be considered as incident - whether the service is up or down. Do you have any idea how it should work or any specific use-case? It would be really helpful.
Thanks.

Start basic, does it connect. Maybe eventually a threshold for response (any response). Then maybe matched response

Udp, no ack, how would it answer something ? But ok for KISS 😉

Our use case is to monitor the health of our VPN server/connection.

Fantastic can’t wait to see this it will be so useful in expanding scope of the tool!

Any news?

Too bad :(

The user chooses the IP address and port and enters send data in string or hex format (converted to binary upon sending). This data gets sent to the IP address and port periodically (the period being set by the user). The user also enters an expected result (again string or hex). The monitoring app reports downtime if a certain number of (also user configurable) replies are missed in a row. This mechanism is pretty generic and will be able to detect uptime of a great many UDP protocols. There could also be preset options for popular UDP protocols.

Would like to automate testing if target DNS server(s) are alive and responding… (UDP 53)

(NB, you claim testing DNS is an option under port monitoring but this will only support TCP at present?)