Blog: OpenObserve SLO bug is fixed in 1.0.1, verified - #273
Merged
Merged
Conversation
v1.0.1 shipped on 16 September and its changelog names the backport (#14453) that missed the 1.0.0 tag by a day. Verified rather than taken on trust, because I called this fix too early once already. Fresh single-node install on v1.0.1 with SQLite, the exact configuration that fails on 1.0.0: no readonly-database line anywhere in the log, stale_watermark goes false, and the status row keeps advancing, with the SLI moving from 70.84 to 70.21 and the burn rate with it as new measurements land. On 1.0.0 the same setup froze for forty minutes and never fired. So the PostgreSQL workaround is now only for anyone pinned to 1.0.0, and the post says that. Sharp edges reworded, links point at 1.0.1, and dateModified is set, which surfaces an Updated date on the page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
0871d87
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://56d19389.website-dab.pages.dev |
| Branch Preview URL: | https://blog-openobserve-101-slo-fix.website-dab.pages.dev |
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
1 participant
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.
Follow-up to #268. v1.0.1 shipped on 16 September with the SLO fix that missed the 1.0.0 tag by a day.
Verified, not assumed. I called this fix too early once already, so this time I ran a fresh single-node install on v1.0.1 with SQLite, which is the exact configuration that fails on 1.0.0:
readonly databaseerrorsstale_watermarkcomputed_atChanges
dateModified: 2026-09-16added, which renders an "Updated" date on the page and refreshes the BlogPosting schema.Upstream issue openobserve/openobserve#14490 is closed as completed.
🤖 Generated with Claude Code