Joshua MacDonald

I referenced this from an OpenTelemetry metrics SDK issue in which we are looking to address the same problem. I started poking around hoping that DataDog had already set a...

@arbll The document linked above, which I believe you are quoting from, describes **naming tags**, i.e., the valid set of characters permissible in a tag **name**. Restricting tag names is...

Here is the specification I refer to: https://w3c.github.io/correlation-context/#value-format

I believe users should use Histogram instruments configured with Summary aggregators to achieve the desired outcome. Semantically, there is not a difference between the proposed Summary and the current Histogram...

@asafm I support letting each OTel SDK do what's natural for users as long as stays within the SDK. The SDK will likely have internal interfaces for representing Aggregators and...

One option that OpenTelemetry could explore after its 1.0 milestone, if there's interest, is to specify a Summary aggregation that closely matches the Prometheus definition that could be derived from...

Closing this as being accomplished through Links in the current spec.

Please explain why the `SpanKind` field does not satisfy this?

There is a lengthy discussion about this topic in https://github.com/open-telemetry/opentelemetry-specification/pull/2518#discussion_r881241625. In that comment, I propose that OTel is better off having string-valued attributes and 0/1-valued UpDownCounters to convey state sets....

@hardproblems responding to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/12300#issuecomment-1196158260 and https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/12300#issuecomment-1196171396 > This is kind of similar to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/11870. There seem to be use cases where for one reason or another, the sender's unique ID...