Moritz Lang
Moritz Lang
Yes, this does seem to be the cause! 👍 I haven't reproduced it yet but have a New Relic setup that I could try to use. However, given the OTel...
> One way could be to use a GRPC interceptor for this to populate the missing body so the rest of the OTLP-compliant codebase continues to function. WDYT? Sounds like...
Yeah, I guess we could bundle some of these in the library itself. I was now able to reproduce this issue with my NewRelic account and the Swift OTel Server...
> hb_id allows you to associate a trace entry with entries in your log. Isn't that what the metadata provider provided trace/span IDs already do?
`span_id` and `trace_id` are attached via the logging metadata handler from swift-otel. `hb_id` is not related to that. Log correlation works well with various observability tools.
> Sorry took so long to reply. > @adam-fowler Likewise 😅 > `hb_id` is used to identify log entries that belong to a single request regardless of whether you are...
> ... he already has an id attached to the logger, and considers hb_id as clutter. I think he just wants an option to not add it to the logger....
Thanks for sharing your use-case @joseph-newton-ck! 🙏 `http/protobuf` is definitely on our roadmap and will become the default in Swift OTel 1.0, which is on par with the OpenTelemetry specification....
`http/otlp+protobuf` and `otlp/http+json` exporters are now implemented in `1.0.0-alpha.1`.
> Will we still be able to use "trace id based sampling", eg trace only every 10th span? > @t089 Yes, "trace-id-ratio" is one of the samplers defined in the...