-
Notifications
You must be signed in to change notification settings - Fork 626
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
Using AWS resource detector with auto-instrumentation #2370
Comments
I did a little digging and I think I might see what's going on: Looking at the code, the auto-instrumentation looks for resource detectors registered under the "opentelemetry_resource_detector" namespace: I see that the Azure resource detectors have been registered using that entry point here: opentelemetry-python-contrib/resource/opentelemetry-resource-detector-azure/pyproject.toml Lines 30 to 32 in 24eadcf
So a corresponding change would need to be made to the sdk-aws pyproject.toml file here: opentelemetry-python-contrib/sdk-extension/opentelemetry-sdk-extension-aws/pyproject.toml Lines 29 to 32 in 24eadcf
I was able to confirm this by adding the following line to my Dockerfile, which writes the expected section to the package entrypoints:
Using a fake
|
Describe your environment Describe any aspect of your environment relevant to the problem, including your Python version, platform, version numbers of installed dependencies, information about your cloud hosting provider, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main.
Running a basic Flask application instrumented using opentelemetry-instrument in Docker python:3.12.2-slim. Set environment variable
OTEL_EXPERIMENTAL_RESOURCE_DETECTORS=aws_ecs
.Dependency versions:
Steps to reproduce
Describe exactly how to reproduce the error. Include a code sample if applicable.
Run
docker-compose up -d
with entrypointopentelemetry-instrument flask run --host=0.0.0.0 --port=5000
What is the expected behavior?
What did you expect to see?
Start up using ECS resource detector
What is the actual behavior?
What did you see instead?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: