News for hackers. Stuff that matters.

chipfixer

awesome! Let me know what you think.
Re:Connecting Kubernetes dependencies to application telemetry on Friday September 11, 2026 @06:57PM (#49666574)
So if there is a spike on say errors, you do a group by pod, click on the pod in the legend, see the k8s neighborhood which means discover the pod --> config map association. You see the config map and all the recent updates to it, and can even diff them like code.

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.

Re:Connecting Kubernetes dependencies to application telemetry on Wednesday September 09, 2026 @04:21PM (#49633632)
Are you saying that if everything became an event, its easier to correlate because the event is more free form and it's easier to add custom metadata?

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...

( Read More... | 4 comments | 2 points | on HN )
We are a startup working on Chip - a monitoring agent that integrates out of the box with OTEL. We are looking for SREs/Devs that can simulate real world scenarios for Chip to detect and keep us honest about the effectiveness of our tool.

We will pay an hourly rate for this person's time.

Yup, no amount or type of anomaly detection can fix the culture. That said, in this case, maybe one reason it may be hard is the devs weren't the ones owning what the job did in production?

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 —...

( Read More... | 3 comments | on HN )