chipfixer
OpenTelemetry and one UI trick changed the way we debug Kubernetes
An alert on the other hand, say on a node that is low on disk, doesn't automatically tell you all the affected workloads. Not saying the alert doesn't help, but this experience helps identify the affected pods and apps much faster.
In theory, I agree with you. But you can't eliminate 'joins' all together, IMO, because it's not practical to know beforehand what context will be useful.
Connecting Kubernetes dependencies to application telemetry
I’m building Cardinal (cardinalhq.io). One thing that drives me nuts about Kubernetes debugging is the number of steps it takes to go from an application issue to its underlying kubernetes root cause.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...
We will pay an hourly rate for this person's time.
Looking for DevOps/SRE engineers that can beta test Chip getchip.ai [video]
Anomaly detection: business metrics vs. system metrics?
Recently, I ran into someone at a conference who had a major incident: a config change caused a revenue drop. Their RED/system metrics didn’t catch it because they were all static-threshold alerts and siloed from the business signals, so engineers didn't discover the actual revenue impact until much later.What may have been helpful is anomaly detection directly on their business metrics —...