Create an specific health check endpoint for the UDP tracker

[josecelano]

We check if the UDP tracker is running by making a connection request.

See https://github.com/torrust/torrust-tracker/blob/develop/src/servers/health_check_api/handlers.rs#L90-L113

But that leads to having non-accurate data in the statistics:

{
  "torrents": 64671,
  "seeders": 15736,
  "completed": 58213,
  "leechers": 31896,
  "tcp4_connections_handled": 2,
  "tcp4_announces_handled": 1,
  "tcp4_scrapes_handled": 1,
  "tcp6_connections_handled": 0,
  "tcp6_announces_handled": 0,
  "tcp6_scrapes_handled": 0,
  "udp4_connections_handled": 16378558, <- including health check requests
  "udp4_announces_handled": 10314717,
  "udp4_scrapes_handled": 443622,
  "udp6_connections_handled": 0,        <- including health check requests
  "udp6_announces_handled": 0,
  "udp6_scrapes_handled": 0
}

Especially if you enable a monitoring system using the healthcheck endpoint as we did for the torrust demo.

My first idea was to implement a new UDP protocol request type. I did not do it because we are using the aquatic UDP crate.

• Should we implement our own UDP tracker to be able to do this type of customization?
• Should we create this new healthcheck UDP request?

I do not think it's a very important issue, but it could be an additional reason to implement our own UDP tracker in the future.

cc @WarmBeer @da2ce7