You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently also playing around with opentelemetry instrumentations in combination with NestJS applications in a Kubernetes environment.
Here's what I've learned so far:
Yes, there is an @opentelemetry/instrumentation-nestjs-core package. It allows you to instrument your node application manually using the SDK or by using the Node auto-instrumentations.
However, I was not able to get the Kubernetes based node auto-instrumentation to work with an existing NestJS docker container. In theory this should use the instrumentation linked above (which works when added to the application/image directly).
I've given up on the opentelemetry-operator instrumenations for now and have decided to "embed" the SDK-based auto-instrumentations in my NestJS application.
Component(s)
auto-instrumentation
Describe the issue you're reporting
We are trying the Kubernetes operator for auto instrumentation using opentelemetry.
followed this document https://opentelemetry.io/docs/kubernetes/operator/automatic/
We added the below annotation in our Nestjs application deployment manifest.
instrumentation.opentelemetry.io/inject-nodejs: "true"
The same configurations worked for Nodejs applications and others, but for the NestJs application, it does not generate traces and spans.
I didn't find any documentation for NestJs auto instrumentation
The text was updated successfully, but these errors were encountered: