Joshua MacDonald

(I could not attend the Spec SIG yesterday and the recording is not yet available.) From the discussion above, looks like we're still debating what to call this attribute and...

Can we explicitly state that this applies to resources too? I believe that span attributes and resources (which are only specified in the proto, currently) are specified with the same...

In #579, Tigran's example seems to contain a use-case. The resource of "application B" is a set of key-value attributes.

When W3C adds a randomness flag to the trace flags, OTel spans will immediately want to know whether the flag was set, e.g., https://github.com/w3c/trace-context/pull/468 We need this information. My opinion...

@dashpole I anticipate users might react to the new metric attributes in their Prometheus data and come to request an option to disable these attributes, in exchange for the risk...

The way I see this matter, it's not that we have a problem with any one of the underlying mechanisms -- the span processor, the span exporter, and the span...

Note [OTel-Go has a variant type for its `Attribute` value](https://github.com/open-telemetry/opentelemetry-go/blob/392a44fa464d1fcad3a11257cee3d447e506d39c/attribute/value.go#L32). Surely this can be fixed in Go with a custom solution.

@hdost Acknowledging your point, we have to be careful how we describe these changes before the next release. Also we did not write a Changelog entry in #270, which led...

I strongly suspect this is due to particular data points causing an unrecoverable error that looks recoverable. This requires some kind of never-succeeding request to explain, but the sidecar logic...

This is the function that never returns: ``` // sendSamples to the remote storage with backoff for recoverable errors. func (s *shardCollection) sendSamplesWithBackoff(client StorageClient, samples []*monitoring_pb.TimeSeries) { backoff := s.qm.cfg.MinBackoff...