-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
otel python auto instrumentation #3598
Comments
@swiatekm @TylerHelmuth @opentelemetrybot can any of you guys help me on this? |
@pmcollins can you help me on this? |
Do you actually mean the operator version here, or the Helm Chart version? |
@swiatekm its the helm chart version this is how i have done my setup-- helm install opentelemetry-operator open-telemetry/opentelemetry-operator --namespace opentelemetry-operator --create-namespace --set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" otel-collector.yaml ---otel collector deployment ---apiVersion: opentelemetry.io/v1beta1 instrumentation,yaml ---instrumentation for collector deployment---apiVersion: opentelemetry.io/v1alpha1 dotnet:env:- name: OTEL_EXPORTER_OTLP_ENDPOINTvalue: http://otel-collector:4318go:env:- name: OTEL_EXPORTER_OTLP_ENDPOINTvalue: http://otel-collector:4318again i changed the instrumentation.yaml apiVersion: opentelemetry.io/v1alpha1 apacheHttpd:configPath: /usr/local/apache2/confimage: ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.3version: "2.4"dotnet: - tracecontext
and i have added these annotations before adding this envi variables
|
Component(s)
collector, auto-instrumentation
What happened?
Description
Steps to Reproduce
Expected Result
Actual Result
I'm setting up distributed tracing and end-to-end transaction monitoring for my services, which are hosted in an AKS (Azure Kubernetes Service) cluster and built using the Python framework. Since we use a microservices architecture, I'm implementing OpenTelemetry (OTel) with auto-instrumentation. This involves deploying the OTel Operator in AKS along with an OTel Collector and using Jaeger for tracing and ELK as backend storage
As part of the setup, I added the necessary Python-related annotations to enable tracing for four of my services. However, while I can see trace data for two of the services, the other two are not sending any data. Instead, I see an error message:
Could not find the ORIG_HANDLER or _HANDLER in the environment variables. This instrumentation requires the OpenTelemetry Lambda extension installed.
Since our environment is in Azure and not AWS, I don't understand why this error is appearing. What could be causing this issue, and how can I resolve it?
Kubernetes Version
1.29.5
Operator version
0.76.0
Collector version
latest
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: