Joshua MacDonald

This was discussed in today's Spec SIG. Would someone involved in the conversation today please post a summary of any decisions that were made?

@jack-berg -- @MrAlias asked for guidance on this topic in https://github.com/open-telemetry/opentelemetry-go/issues/3006#issuecomment-1189376884 I am aware of incompleteness in our specification around the appearance or disappearance of metrics from one collection to...

> What about using the timestamp of last collection as the start time? For push-based exporters, this works. For pull-based exporters, in the common case when there is only one...

@legendecas made an insightful remark here, https://github.com/open-telemetry/opentelemetry-js/issues/2997#issuecomment-1198923194, noting that temporality is irrelevant to this problem. Cumulative/Synchronous and Delta/Asychronous configurations both have the same problem. In both cases, a user may...

@MrAlias do you accept the current contents of this PR? I believe the goal of specifying a "DISABLED" variable with exactly one meaningful value ("true") was to avoid the [general...

The use-case where a single application is mounted on multiple (virtual host, root path) pairs seems pretty obscure to me, but not unreasonable.

The Aggregator interface that is currently described in the draft SDK specification and in the OTel-Go library does receive raw events. An aggregator that handles raw events and does not...

@cijothomas Mostly my response above was for your statement. @mxiamxia Given your requirements, it would be perhaps a little simpler to implement your own SDK, since it will do work...

I am conflicted about a few things here. We have @cnnradams working on an exemplars prototype, and I encouraged him to go a little further than simply capturing trace/span IDs...

In the discussion surrounding this issue, we debated the usefulness and meaningfulness of either having or not having a `direction` attribute vs having or not having independent metrics. The reason...