Reading Up on Observability and Monitoring

Sure, monitor it, but what we really need to know is what the data is, if it’s really the data we want, and the event the data is relevant to

우리가 정말로 알아야 하는 것(데이터가 무엇인지, 정말 우리가 원하는 데이터인지, 데이터와 관련있는 이벤트인지)을 모니터링하라.

Monitor everything”. Dude, you can’t. You can’t. People waste so much time doing this that they lose track of the critical path, and their important alerts drown in fluff and cruft. In the chaotic future we’re all hurtling toward, you actually have to have the discipline to have radically fewer paging alerts … not more. Request rate, latency, error rate, saturation. Maybe some end-to-end checks that stress critical Key Performance Indicator (KPI) code paths.

모든 것을 감시해. "야, 할 수 없어. 너 할 수 없어" ....

observability is a superset of monitoring…

관측 가능성은 모니터링의 수퍼셋이다.

I Monitor you, but you make yourself Observable.

나는 너를 모니터링하지만, 너는 스스로를 관찰할 수 있게 만든다.

cookk / docs

Reading Up on Observability and Monitoring #9