Joshua MacDonald

We may wish to extend this issue to cover all OTLP features today, which may require an audit. I'm aware of Metric.Metadata which was added and we do not support...

Recommend changing the PR title to emphasize that this is being addressed for HTTP configurations, not gRPC. FYI the OTel-Arrow project also addressed this problem for itself internally on the...

Blocked by #13478

The TC accepts this issue and I have volunteered to act as sponsor. The topic of concurrent export is something I have a lot of experience with across OTel, and...

@XSAM This was discussed in the Spec SIG today. There appears to be not much support for binary-attribute values. I think it's bad for the users, but it's not so...

@open-telemetry/specs-logs-approvers @open-telemetry/specs-metrics-approvers @open-telemetry/specs-trace-approvers Please consider this updated OTEP. The changes I have applied: - The OTel group has already decided not to support byte-valued attributes: document this. (Tough!) - Specific...

@jsuereth and @reyang I appreciate the feedback. Both of you are, I think, suggesting to make UTF-8 validation an opt-in instead of an opt-out feature. I support that motion. The...

We think we can "hide" this detail in the implementation of hyper-edges and the dispatch strategy.

Related: https://github.com/open-telemetry/otel-arrow/pull/1295#discussion_r2457309517 In the OpenTelemetry Collector, note that fanout consumers in the Collector are "invisible", they do not make metrics IIUC. When a fanout consumer sits between a receiver and...

I don't think this corner-case is worth adding a new option to the histogram update operation, mainly because optionality is expensive in the OTel-Go API. I would prefer to add...