Blog: Kubernetes observability in 2026, with OpenObserve 1.0 as the backend - #268
Draft
saiyam1814 wants to merge 15 commits into
Draft
Blog: Kubernetes observability in 2026, with OpenObserve 1.0 as the backend#268saiyam1814 wants to merge 15 commits into
saiyam1814 wants to merge 15 commits into
Conversation
Deploying website with
|
| Latest commit: |
084b62f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://edf94948.website-dab.pages.dev |
| Branch Preview URL: | https://blog-kubernetes-observabilit.website-dab.pages.dev |
…shot captions, rc2 note
…, real log line, versions
…AQ, entity schema - Lead the TL;DR and meta description with the 31 ms search and 43m CPU numbers - Align title and seoTitle on "with OpenObserve 1.0 as the backend" - Link OpenObserve pages on first relevant mention instead of only in the footer - Name Loki, Elasticsearch and the LGTM stack next to the comparison table - Open each "How it's built" subsection with one self-contained sentence - Six-question FAQ in frontmatter (renders the FAQ section and FAQPage JSON-LD) - Template: `about` and `mentions` frontmatter entities in the BlogPosting JSON-LD, plus `dateModified` support with a visible Updated date Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Adds the OpenObserve vs Prometheus and Mimir post, which runs both file formats on the same engine, next to the log-records comparison. The section fragment Jacob sent does not resolve (headings on that page have no ids), so the link points at the post. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Preview only. Please do not merge yet; this PR exists to get a Cloudflare Pages preview URL to share with the OpenObserve team for review.
Post: Kubernetes observability in 2026, with OpenObserve 1.0 as the backend
Problem (why the backend is where observability cost lives), landscape, how OpenObserve 1.0 is built (write path, index file, query funnel, Vortex, MCP), and a hands-on run on a kiac cluster with a companion repo: https://github.com/saiyam1814/openobserve-k8s-demo
Assets: cover, 5 excalidraw-style diagrams, 2 GIF animations, 8 screenshots under
public/img/blog/kubernetes-observability-in-2026-with-openobserve/(2.6 MB total).Before merge: set
datePublishedto the publish date, and confirm the SLO section wording with the OpenObserve team (it describes a bug in 1.0.0-rc1 that has been reported upstream).