Joshua MacDonald

Sorry for the delay. > shouldn't be more overhead then passing attributes This issue was used to justify make attribute passing part of an optional pattern, so now passing attributes...

> Keep the current behavior of encoding non-UTF-8 strings as byte value Can we also specify that the OpenTelemetry Collector have an opt-in to support passing through invalid UTF-8? (This...

@pyohannes Would like to respond to https://github.com/open-telemetry/opentelemetry-specification/issues/3950#issuecomment-2020398102 which specifically uses Rust as an example. I have just been oncall this week and responded to an issue for telemetry data dropping...

@XSAM I would like to hear your thoughts on https://github.com/open-telemetry/oteps/pull/257, thanks.

@evan-bradley What do you think? This is a simple PR to add tracing to a critical component, and I have tried to explain that this is only one of the...

> Not yet, some of the answers to my comments I am unable to understand @bogdandrutu please clarify. I can't guess at which parts of this PR and the overall...

Disappointed.

I support the proposals in https://github.com/open-telemetry/opamp-spec/issues/16#issuecomment-983077725 that, roughly speaking, accepts OpAMP as a way to manage client SDKs by adding support for variable telemetry "schemas". Could we use the `schema_url`...

Could we agree on a transformation to turn invalid UTF-8 into valid UTF-8? Should we reject those strings?

I believe there's a question of what we actually want to have, here. The term `character` is reasonably well defined in relation to utf-8, [but it's not the same as...