On 02/29 14:30, Maciej Jaros wrote:
David Caro (2024-02-29 13:57):
[...]
The most interesting feature though is being able to pass a url to use as HTTP health check.
To do so you can pass `--health-check-url /path/to/health` to your `toolforge webservice start` command, and toolforge will automatically restart your webservice if it stops responding to that path (you can change the path to whatever you want, ex. `/`).
By "if it stops responding" you mean stops responding with HTTP status 200? Or stops responding with non-zero bytes of content? Or...? :)
In the case of TCP probes (default if you don't specify anything), that'd be if the application stops responding at all (unable to connect, tcp timeout), so only really fatal failures are caught.
For HTTP it will be if the service stops responding at all (unable to connect, timeout, ...) or responds with anything different than a 200 HTTP code (the content does not matter).
Cheers, Maciej Nux _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/