search

open-telemetry / opentelemetry-specification

Specifications for OpenTelemetry
https://opentelemetry.io
Apache License 2.0
3.65k stars 871 forks source link

Representing Websocket traffic in Real User Monitoring #1683

Open ivomagi opened 3 years ago

ivomagi commented 3 years ago

What are you trying to achieve?

Even though websockets can be modelled as a CLIENT span much alike XHRs and fetches (connection open, eventually closes or errors), likely a more correct interpretation is a messaging system (PRODUCER & CONSUMER), though even this gets more complicated with some abstraction layers such as socket.io that can provide callbacks.

mottibec commented 3 years ago

Hey all. We are developing a socket.io instrumentation plugin at Aspecto atm. So we would love to participate in this discussion as it would help us write better instrumentation.

ivomagi commented 3 years ago

Hey all. We are developing a socket.io instrumentation plugin at Aspecto atm. So we would love to participate in this discussion as it would help us write better instrumentation.

@mottibec - I started the discussion with the interested parties in the CNCF OpenTelemetry Slack. You do not seem to be the member of this workspace, so if you would consider joining, follow the instructions at https://github.com/open-telemetry/community to participate.