search

open-telemetry / opentelemetry-operator

Kubernetes Operator for OpenTelemetry Collector
Apache License 2.0
1.18k stars 420 forks source link

Auto-instrumentation doesn't work as expected #2959

Closed Sotatek-GiangPham2 closed 2 months ago

Sotatek-GiangPham2 commented 4 months ago

Hi everyone,

I recently deployed a application nodejs, and setup Opentelemtry-operator and Jaeger to trace latency of my application. I read carefully docs, so i configurate successfuly init instrumentation into application. But when i check logs of collector and Jaeger UI, i can't see anything metrics (i curl API application before). I feel a bit strange, do I have to write anything else in my code? But i used auto-instrumentation. Hope everyone support!

Thanks Giang

image image Information for my appilication image

yuriolisa commented 4 months ago

@Sotatek-GiangPham2, could you please confirm if your Jaeger endpoint configured on exporters is correct? Also, note that you configured only traces pipeline, which will send only traces. If you intend to export metrics and logs, please ensure the exporter and pipeline configurations accordingly.

Sotatek-GiangPham2 commented 4 months ago

@yuriolisa Thanks you so much, i fixed this errors.

By the way, if you mind if I ask more about python and go auto-instrumentation. I deployed a simple application by python or go ( a hello-world api), i can easy insert instrumentation into pod and reach all information need tracing at jaeger. But when i use a complicated application of my project, i can't reach tracing information.

I know it's a stupid question but I don't understand why it happens to my two projects go and python. Hope you can suggest it help me. Thanks you

Giang

jaronoff97 commented 2 months ago

@Sotatek-GiangPham2 please reach out in the CNCF slack if you have any trouble with autoinstrumentation for your applications and need some debugging help. Closing this for now.