I'm confused now. What's the difference between logging and tracing? After reading more about tracing, the lines seem super blurry.
-
-
Replying to @yoshuawuyts
logging <-> metrics <-> tracing all seem like a spectrum. I've heard
@mipsytipsy say smart things about this but i can't recall where?1 reply 0 retweets 2 likes -
hi! :) logs are strings, and they have to be parsed, which is stupid and expensive. Structured logs, or events, are the future. As for
1 reply 0 retweets 5 likes -
..tracing, it generally means there is a unique request id (usually a header) which is attached to every log or event for that req
2 replies 0 retweets 3 likes -
Metrics, otoh, are typically a "dot" of info, not an event. Metrics usually report a detail over an interval of time and then squish it.
1 reply 0 retweets 2 likes -
Like, if the interval is per second, it may sample or average all the values seen over that second. The orig event is lost with its context
1 reply 1 retweet 2 likes -
Newer metrics stores try to compensate for this weakness by adding a limited # of "tags" to each metric. Works, but write amplification sux
1 reply 0 retweets 1 like -
They are basically trying to wrangle metrics back into something that feels like an event based system. Because those are better.
1 reply 0 retweets 1 like -
Distributed tracing and honeycomb are the only next gen observability approaches I know of. Tracing==depth first, honeycomb breadth first.
1 reply 0 retweets 2 likes -
(Does that answer your questions, or am I being that boring math teacher right now?
)1 reply 0 retweets 1 like
It totally does! Thanks heaps for answering :D
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.