Motti

If I understood [this](https://github.com/socketio/socket.io-website/issues/277) conversation correctly, potentially, a client could emit a `connection` event. So we should treat the `connection` as a reserved event only when instrumenting the `Server` instance...

after some trial and error I got the following startup code working, not sure if it works 100% yet ``` var tenants = GetTenants(); string currentTenantId = null; config.UseRestier(services =>...

The processor or's between all policies so for your use case you can have 2 separate policies one for latency and one for string attribute and you will get the...

@tim-oster @jpkrohling can we merge this? this will solve #13929

it looks like CrmSvcUtil is using the SdkMessage entity to generate actions, the SdkMessage name field contains the prefix of the publisher.

@akubik-splunk we started a process of moving all of the instrumentations over to the contrib repo. After the Aspecto acquisition this was stopped, but we do want to upstream these....

@akubik-splunk check out [instrumentation-migration.md](https://github.com/aspecto-io/opentelemetry-ext-js/blob/master/instrumentation-migration.md) this might help.

we just released a socket.io plugin [check it out](https://github.com/aspecto-io/opentelemetry-ext-js/tree/master/packages/instrumentation-socket.io)

> > we just released a socket.io plugin [check it out](https://github.com/aspecto-io/opentelemetry-ext-js/tree/master/packages/instrumentation-socket.io) > > Will this work with `ws` package? no, only with the `socket.io` package