This is the second of two parts. Read Part 1:
In Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with OpenTelemetry’s model of spans and traces. I’ll pick up where I left off by sharing another approach to make OpenTelemetry more ergonomic for JavaScript. I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today.
Now, as a…