Bogdan Drutu
Bogdan Drutu
@jack-berg depends how you read: > The log attribute model MUST support [any type](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#type-any), a superset of [standard Attribute](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/README.md#attribute), to preserve the semantics of structured attributes emitted by the applications....
I am not the biggest expert, but I feel at least some are recoverable, and some are contextual (example auth when passing auth tokens from the client). >If you're suggesting...
> it switches proto-go from the slim package to the standard one for one this is required because the slim version does not have the grpc generated code, so I...
>I was following configretry, which appears to be exporterhelper-specific but resides in /config. For one thing, I would like to be able to experiment with completely replacing exporterhelper. I should...
This is done.
I do agree that in some scenarios like sidecar maybe skipping this is the right thing, but if we have a "standalone service" which is not a proxy/lb/sidecar, would be...
> This can be achieved by utilizing tracestate. Also tracestate approach is better (as discussed today at the meeting) in another use case where "proxy" service retries and want to...
@SergeyKanzhelev ping on this
I think, we could consider also to allow views to read from `Baggage` to determine attributes.
@Oberon00 who is "I" in this example "instrumentation author"? "application owner"?