Martin Kuba

Would there be any challenges with specifying some resource attributes as identifying (immutable) and some as descriptive (mutable) (as discussed in https://github.com/open-telemetry/opentelemetry-specification/issues/1298)? Are there any backends that actually use all...

@arminru > If the proposed browser.platform was kept despite duplicating os.name, its presence would be sufficient without having to capture a user agent. In some browsers (older versions of Chromium,...

> So browser.platform would also be left empty in this case since the sentiment is to not impose the requirement of user-agent parsing on instrumentation, right? Yes, I don't think...

> Is it right that session id is part of the Resource? It is an attribute that applies to all telemetry coming out of the application. It does not change...

Thanks to @alolita and @qhanam for putting this proposal together! A lot has been discussed already; let me add just a few thoughts for further consideration... ### Sampling One topic...

What would be the best next steps to move this discussion forward? Would it make sense to create a new SIG?

@dyladan @pichlermarc The codecov check was failing, so I added one more test just to make sure that lower coverage is not caused by this change. Now the HttpsInstrumentation integration...

@jwatte I have started looking at this, and I am not seeing a significant overhead when making ~1000 fetch calls. Can you please provide a little more details on how...

That is correct - I am interested in working on this along with a prototype for the Events API.

I put this aside while the API was being discussed, and I have opened a [draft implementation of the API](https://github.com/open-telemetry/opentelemetry-js/pull/3117).