Monitoring demystified: A guide for logging, tracing, metrics

Re:Monitoring demystified: A guide for logging, tracing, met... by dkarl on Friday July 31, 2020 @10:24AM (#24008833)

I agree with this wholeheartedly. You can even define a standard and let downstream services opt in over time. Simple wins like this should not be put off because "someday" we're going to implement a complex distributed tracing solution.

[ Parent | on HN ]

Re:Monitoring demystified: A guide for logging, tracing, met... by dillonmckay on Friday July 31, 2020 @11:07AM (#24009343)

So, in terms of full implementation, is the constraint the dev time to implement, or getting various factions to agree to something?

I guess, is it political, or technical?

Asking for a friend.

Thanks!

[ Parent | on HN ]

Re:Monitoring demystified: A guide for logging, tracing, met... by nitrogen on Friday July 31, 2020 @11:50AM (#24009895)

Often it's political, but political friction can feed into technical friction if there are also a half dozen different half wrappers around half-baked HTTP libraries. Also, if someone has included OpenTracing as a shadow library in a company-wide library (JVM territory), but you want it as a top-level dependency, you have to write translators.

[ Parent | on HN ]