Severin Neumann

I updated the file with a lot of changes provided by everyone, thank you! I copied some of your wording, I restructured most of the text. Here are some of...

> I feel like this discussion is really talking about 2 separate things, and we should probably separate them into 2 separate oteps. > > 1. A _unique identifier_ for...

@rahuldimri are you still up for this?

Looks like this issue & #392 are related.

Will be fixed via #1694

This is a great summary, thanks for taking the time to write it down! I have a few remarks & questions: * Does RUM include Synthetic User Monitoring? Maybe "User...

>I agree with that. Maybe we could even model spans based on logs, to make the hypothetical "streaming SDK" the default (at least it sounds interesting as a thought experiment)....

From what I understand, there are now the following proposed solutions to cover RUM use cases with OpenTelemetry: # (1) Introducing a new Signal: RUM Event The initial proposal from...

@AaronCreighton , @mc-chaos : there's a SIG called "client side telemetry" which is looking into RUM & OpenTelemetry, if you're both not member there, I think bringing your ideas &...

following up on this. @austinlparker: do we want to keep those resources (presentation, glitch) updated/maintained? Is opentelemetry.io the right place to discuss or does this belong to open-telemetry/community? cc @cartermp...