Re:All you need is Wide Events, not "Metrics, Logs and Traces"
by jimbobimbo on Tuesday February 27, 2024 @10:17PM
(#39533542)
It exactly is a structured log or log in open telemetry.
To make it easier for myself, I think of spans also as structured logs with a schema that everyone had agreed on, which make it possible to trace requests across multiple services/clients. It's probably more than that, but I don't need academic precision to see how this is more useful during livesite investigations than simply querying logs with unaligned schemas.
Re:All you need is Wide Events, not "Metrics, Logs and Traces"
by isburmistrov on Wednesday February 28, 2024 @08:00AM
(#39537277)
Yes, structured log exactly. Why I prefer "wide event" as a term because it has this "wide" component that serves for 2 purposes:
- it highlights the intention of storing as much context as possible - it also hints on the implementation for a system that would serve them. One likely need to use columnar storage to store wide events, there is no way around it
But just a personal preference in the end.
If you want a point-and-click interface to log searching I agree that some percentage of people like to start there (and I think splunk may even have that too), so I'm not opposed to it existing at all, but I feel very strongly that having the more sophisticated capabilities if you want to move beyond a point-click is a requirement.