You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice (better Developer Experience) if a non-ok request to /api/system/healthcheck would also write to the STDOUT logs what the issue is.
We have Cockpit being deployed with CI/CD runners and it's hard to guess why a server it's passing it's healthchecks - if there was output to the logs it would make debugging much easier.
2024-08-15T11:27:51.264 app[9185e6d9f76168] fra [info] 2024/08/15 11:27:51 [info] 372#372 "cockpit" application started
2024-08-15T11:27:53.661 health[9185e6d9f76168] fra [error] Health check on port 80 has failed. Your app is not responding properly. Services exposed on ports [80, 443] will have intermittent failures until the health check passes.
The text was updated successfully, but these errors were encountered:
mountainash
changed the title
[DX]: /he
[DX]: Bad /healthcheck should write logs
Aug 15, 2024
It would be really nice (better Developer Experience) if a non-ok request to
/api/system/healthcheck
would also write to the STDOUT logs what the issue is.We have Cockpit being deployed with CI/CD runners and it's hard to guess why a server it's passing it's healthchecks - if there was output to the logs it would make debugging much easier.
The text was updated successfully, but these errors were encountered: