Timeout of checks

[Trigary]

Some checks (e.g. HTTP, reachability) take a very long time to fail (to time out), therefore it takes a long time for all of the checks to finish when checking misconfigured networks.

I think it would be useful to have lower timeouts for checks. I can think of several ways to implement this:

• Optional global timeout setting in the JSON/YAML config: any check that takes longer than the specified time is automatically aborted
• Timeouts within the individual commands executed by the checks (ping -W ... and curl --max-time ... or curl --connect-timeout ...
  • The timeouts could be hardcoded values (lower than the implementation defaults)
  • Or they could be configurable on a per-check basis via the check's configuration

[tcaiazzi]

Dear @Trigary,

Thank you for reaching out!

Your suggestion is a good one. The best approach may be to support both options:

1. A global timeout setting.
2. Per-check timeouts.

We’ll consider this for the next release. If you’d like to contribute, PRs are always welcome!

Thanks!