We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the status of a service that we keep as the historical record is just the status on the final check of the day.
So, if a service is failing all day, but at the end of the day happens to be fixed, the historical status we store is "healthy".
Conversely, if a service happens to fail at the end of the day, the historical status we store is "unhealthy".
This is not ideal. It’s an artefact left over from when we only ran a single check per day.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, the status of a service that we keep as the historical record is just the status on the final check of the day.
So, if a service is failing all day, but at the end of the day happens to be fixed, the historical status we store is "healthy".
Conversely, if a service happens to fail at the end of the day, the historical status we store is "unhealthy".
This is not ideal. It’s an artefact left over from when we only ran a single check per day.
The text was updated successfully, but these errors were encountered: