News for hackers. Stuff that matters.

A comment on Tracing: Structured Logging, but better in every way. Parent comment

Re:Tracing: Structured Logging, but better in every way by candiddevmike on Wednesday September 20, 2023 @11:49AM (#37585710)
Something 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).
[ Parent | on HN ]
Re:Tracing: Structured Logging, but better in every way by discodachshund on Wednesday September 20, 2023 @11:57AM (#37585807)
Isn't that the trace ID? For metrics, it's in the form of exemplars, and for logs it is the log context
[ Parent | on HN ]
Re:Tracing: Structured Logging, but better in every way by candiddevmike on Wednesday September 20, 2023 @12:11PM (#37585993)
That 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
[ Parent | on HN ]
Re:Tracing: Structured Logging, but better in every way by phillipcarter on Wednesday September 20, 2023 @12:24PM (#37586177)
Go 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.
[ Parent | on HN ]
Re:Tracing: Structured Logging, but better in every way by jen20 on Wednesday September 20, 2023 @06:24PM (#37590976)
One 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.
[ Parent | on HN ]