List your extension on the OpenTelemetry Registry

[svrnm]

Hi @tbrockman,

thanks for creating this! As you noted in your README.md already the extension I created a while back is similar, but currently archived (see open-telemetry/opentelemetry-js-contrib#1152 for more details). Although possible now due to some underlying issues bing, I am currently leaning towards not bringing the extension in that repository back, but have other extensions (like yours) listed on the OpenTelemetry Registry and then from that archived plugin README linked. I hope this is also in your interest, if so would you mind adding your extension to the registry ?

I am one of the maintainers of the Website as well, so I can help you handling that. Afterwards I will link from the README of the old extension to the registry filtering down to browser extensions (which initially will only list your extension, but will allow us to list other extensions in the future as well).

Thank you for working on this once again!

Severin

[tbrockman]

Hey @svrnm! I've been meaning to reach out since I noticed you starred the repository, but life kept distracting me 😅. I'd be thrilled to add it to the registry, and I'm really glad that you appreciate the extension!

If you also have any ideas/wisdom for interesting ways to leverage the data emitted by the extension or features to add to the extension in general, I'd be eager to hear them as well (as I'm not sure the current Grafana demo or extension preview is as compelling as it could be).

[svrnm]

Hey @tbrockman, the extension was one of my first contributions to the otel project and then as well life and other parts of the otel project kept me distracted and with the long standing issue with webpack I never got back to it, so I am happy that you tackled that!

I had some ideas what to do over time with that extension. You addressed some of them already (e.g. the option to turn on/turn off certain instrumentations, etc.), but here are a few more

• Option to pick version of OpenTelemetry JS SDK, this can come helpful when you try to find a bug in a version
• An "advanced configuration" space where one can write JavaScript to configure the instrumentation in more details
• Although possible with a separate extension: auto-refreshing the page, especially not time-based but "beacon-based", so whenever enough telemetry is submitted the page reloads, this helps to creates big amounts of data

There are many more but I have to think about that, will keep you posted!

[svrnm]

Thanks for adding this to the otel registry!