example.com/path/to/article
000 points · username · 0 hours ago
example.com6 points · 3 comments · 4 days ago · chipfixer
Like for example, if I am seeing an error rate spike, and I group by deployment, I want to immediately see the deployment's k8s neighborhood, which would then show me the configmap that was updated recently and incorrectly.
Similarly, say a node is low on disk and that is causing a ripple effect on a statefulset trying to write new files, which then affects request latency.
The list goes on.
To solve this, one idea we had was: build a smart chart legend that recognizes a k8s tag (based on OTEL semantic conventions), and then for every entry pops an "infra map" icon. Click and you see the full k8s neighborhood of that entity with health annotations. So now it's easier to go from app telemetry to k8s infra.
I am curious if this UX makes sense, and if not how do you solve this correlation problem today?
https://cardinalhq.io/use-cases/kubernetes
jesol
jeansilga
say a node is low on disk: what about setting up monitoring alerts for those king of things.
In general, alerts are of great help. An alert fired after an update is a big smell about that update causing the issue.
[deleted]
That's all to say, have you considered that framing, and if so, have any opinions on why more general observability tools haven't gone that direction?