chipfixer

awesome! Let me know what you think.

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.

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.

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?