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
{{ message }}
This repository has been archived by the owner on Dec 23, 2024. It is now read-only.
When a non-fatal check fails, the top level status is still "ok". Is the intent that you have to check each component for success in order to determine if the service is actually 100% ok?
Would it be possible to add support for a degraded state or something along the lines of "there are failures, but nothing fatal"?
The text was updated successfully, but these errors were encountered:
I do like this idea. Could you maybe expand upon it a bit? I'm thinking in terms of how to best use that information in a consumer...a readiness probe for example. How could we unambiguously say "there are some failures, but nothing fatal" to a listening process?
This project is no longer actively supported and will be archived. Therefore all issues and pull requests are being closed. Please, feel free to fork it and apply the proposed change.
When a non-fatal check fails, the top level status is still "ok". Is the intent that you have to check each component for success in order to determine if the service is actually 100% ok?
Would it be possible to add support for a degraded state or something along the lines of "there are failures, but nothing fatal"?
The text was updated successfully, but these errors were encountered: