Repository navigation
feat: retain independent daily uptime evidence - #79
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prometheus retains only 30 days of raw data. This adds an independent probe and daily JSON reports for longer uptime evidence.
Tested:
just check, followed by finaljust uptime-test(18 tests), Ruff andty check. Regression controls detect membership loss, malformed HTTP, incorrect failure exits and missing deadlines. Archived evidence reconstructs at 200 days without raw observations or Prometheus.Not checked: production probes, scheduler installation or a physical backup destination. Deployment requires an independent Linux host and separate backup storage.