opentelemetry-ext-js
opentelemetry-ext-js copied to clipboard
aspecto-io
Request: upstream kafkajs instrumentation
Can I request to add kafkajs instrumentation (opentelemetry-instrumentation-kafkajs) module to OpenTelemetry Meta Packages for Node (https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/README.md#supported-instrumentations).
A lot of users use kafkajs with node.js application in K8s and do not want to modify their source code or their application image with a tracing.js while instrumenting it with OpenTelemetry. The OpenTelemetry operator provides a way to achieve that. However it can instrument only the supported node.js packages mentioned at https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/README.md#supported-instrumentations.
As kafkajs is not included in the above list, there is no way to instrument kafka calls made by node.js using kafkajs framework. The only way to instrument such kafka call is to add a tracing.js into the application image and not use Opentelemetry operator to inject instrumentation. However, most of the times, it is a bit cumbersome.
Hey - we seem to have similar ask - there are a few instrumentations contained in this repo (e.g. elasticsearch, kafkajs, typeorm, sequelize...) that could be moved to corresponding OpenTelemetry js instrumentation modules. We (Splunk) would be willing to do the majority of the work as long the repo owners are ok with this
@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. If Splunk is willing to help, this can really boost the effort, as currently no one actively maintains this repo.
@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. If Splunk is willing to help, this can really boost the effort, as currently no one actively maintains this repo.
Hey Thanks for context and clarification - yes we would like to help with this - I have already asked a few people contributing to JS to look into this. Hopefully soon some PRs will be created and we can coordinate around that or if You feel something more is necessary let me know. Thanks!