-
Notifications
You must be signed in to change notification settings - Fork 40
Request: upstream kafkajs instrumentation #263
Comments
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. |
Hey |
@akubik-splunk check out instrumentation-migration.md this might help. |
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.
The text was updated successfully, but these errors were encountered: