Proposal to create a SIG for Real User Monitoring

[martinkuba]

Hello! I would like to propose that a new SIG is created for Real User Monitoring use cases.

The goal of this group, I think, should be standardizing how RUM data is represented, so that RUM instrumentation is portable across different backends/vendors.

Example use cases

• representing user session
• representing user interaction
• representing events with no duration (e.g. paint timing, network change event)

There is a recent OTEP proposal that attempts to address these use cases by introducing a new signal in the OpenTelemetry data model. Based on the comments on this proposal, there seems to be a number of different opinions on how it should be tackled.

There is also an existing Slack channel for client-side telemetry where some of this has also been discussed.

The immediate focus of this group would be

• decide whether a new signal is needed
• decide which signals make sense for different use cases
• define semantic conventions

If anyone else is interested, please comment.

[jkwatson]

Yes please!

[scheler]

Yes, please include me.

[stefaneberl]

Yes, please include me.

[rr0214]

yes, yes. I am interested.

[svrnm]

+1

[martinkuba]

I would like to propose meeting on Wednesdays 8am Pacific Time, which would work for European time zones. Please thumbs up if that works for you, or propose a different time.

[scheler]

8.30am PT is preferable for me (after the school drop off)

…

On Tue, Sep 14, 2021 at 5:00 PM Martin Kuba ***@***.***> wrote: I would like to propose meeting on *Wednesdays 8am Pacific Time*, which would work for European time zones. Please thumbs up if that works for you, or propose a different time. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#830 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVMH2EO7H7ZGQXP2GQJXJ3UB7O2DANCNFSM5DTNR2WQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[svrnm]

If the meeting is scheduled for longer than 1hr, 8:30am Wednesday would conflict with the JS SIG, that starts at 9am (not sure how many people are interested in both)

[jkwatson]

If the meeting is scheduled for longer than 1hr, 8:30am Wednesday would conflict with the JS SIG, that starts at 9am (not sure how many people are interested in both)

I would think that the overlap would be quite high, given the need for browser-based RUM.

[martinkuba]

1/2 hour weekly might be good enough, but a few other options I can think of

1. Thursdays 9am Pacific - would conflict with Java, Python, and Swift, but probably ok?
2. Tuesdays 10am - seems open, less ideal for EU folks
3. Mondays 10am - same as above

[jkwatson]

1. Thursdays 9am Pacific - would conflict with Java, Python, and Swift, but probably ok?

Conflicting with Java & Swift seems very problematic...given iOS and Android. ;)

[ssidhu-apm]

Very interested in joining. 8 / 8.30 am PT on Wednesdays for 30 minutes would be great (already added 👍 for both comments).

[ivomagi]

Interested in joining 8 or 830 AM PT on Wed would match my European calendar

[martinkuba]

Let's go with 8:30 on Wednesdays for 1/2 hour to start with. If we consistently need more time, then we can revisit.

[scheler]

Sounds good to me.

…

On Thu, Sep 16, 2021 at 10:03 AM Martin Kuba ***@***.***> wrote: Let's go with 8:30 on Wednesdays for 1/2 hour to start with. If we consistently need more time, then we can revisit. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#830 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVMH2AICLRRTG7F6RCFWEDUCIPOPANCNFSM5DTNR2WQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[martinkuba]

@tedsuo Would you be able to help us with putting this on the calendar?

[mtwo]

Creating this now

[mtwo]

Crap, we already have three meetings during that period and we only have three Zoom accounts. I'll contact the CNCF to make another account. For now I'm going to set the meeting to start at 9:00 so that it doesn't overlap.

[mtwo]

Done. We can adjust the time to 8:30 once we get more Zoom accounts.

[kalyansai99]

I am interested in joining too. Please include me. Thanks.

[jkwatson]

I am interested in joining too. Please include me. Thanks.

The meetings will be fully public, so feel free to join in! All are welcome.

[SergeyKanzhelev]

Crap, we already have three meetings during that period and we only have three Zoom accounts. I'll contact the CNCF to make another account. For now I'm going to set the meeting to start at 9:00 so that it doesn't overlap.

there are four accounts. Please check the document

[mtwo]

there are four accounts. Please check the document

Nice! I'll update this then. I've reduced my ask on #824 to only request one additional account.

[flands]

Hey folks -- can someone add this to the SIG table in the README?

[mtwo]

Created #879 to add this to the list