4 ms·
Indeed, the three legs (metrics, logs, traces) of OpenTelemetry's telescope. https://opentelemetry.io https://opentelemetry.io
by waffletower 3y ago
Indeed, the three legs (metrics, logs, traces) of OpenTelemetry's telescope. https://opentelemetry.io https://opentelemetry.io
- candiddevmike 3y agoSomething missing from OTel IMO is a standard way of linking all three together. It seems like an exercise left to the reader, but I feel like there should be standard metadata for showing a relationship between traces, metrics, and logs. Right now each of these functions is on an island (same with the tooling and storage of the data, but that's another rant).
- discodachshund 3y agoIsn't that the trace ID? For metrics, it's in the form of exemplars, and for logs it is the log context
- candiddevmike 3y agoThat might be dependent on the library then, there isn't an official OTel Go logging library yet. Seems you have to add the trace ID exemplars manually too
- phillipcarter 3y agoGo is behind several of the languages in OTel right now. Just a consequence of a very difficult implementation and its load-bearing nature as being the language (and library) of choice for CNCF infrastructure. If you use Java or .NET, for example, it's quite fleshed out.
- jen20 3y agoOne would hope that there will not _be_ an Open Telemetry logging library for Go. Unlike last time there was a thread about this, there is now a standard - `slog` in the stdlib.