open-telemetry / open-telemetry/opentelemetry-python-contrib
Heroku Dyno Metadata Not available
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Describe your environment
Python and library versions
Python 3.10.5
opentelemetry-exporter-otlp==1.19.0
opentelemetry-api==1.19.0
opentelemetry-instrumentation-flask==0.40b0
opentelemetry-instrumentation-sqlalchemy==0.40b0
opentelemetry-instrumentation-requests==0.40b0
opentelemetry-instrumentation-urllib3==0.40b0
Platform: Heroku
Steps to reproduce
Set OTEL_RESOURCE_ATTRIBUTES = cloud.provider=heroku
What is the expected behavior?
Traces tagged with heroku dyno metadata: https://opentelemetry.io/docs/specs/otel/resource/semantic_conventions/cloud_provider/heroku/
What is the actual behavior?
No metadata in traces
Additional context
I am trying to set the heroku metadata values in my traces but it doesn't seem to be working.
All I get is cloud.provider=heroku
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Heroku resource semantic conventions linked in the issue and the OTEL_RESOURCE_ATTRIBUTES example. Compare the expected Heroku dyno attributes with the attributes present in traces, then verify that the requested metadata is available after the change using the listed OpenTelemetry Python packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100