open-telemetry / open-telemetry/opentelemetry-python-contrib
Trying to determine when SpanKind with AWS Lambda instrumentation would ever not be consumer or server
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
is there ever a time when the span kind would remain none?
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 with the linked lines 194-208 in opentelemetry/instrumentation/aws_lambda/init.py and trace how SpanKind is selected for AWS Lambda spans. Check the existing instrumentation tests for cases covering span kind; done should establish whether NONE is reachable and identify the needed behavior or test change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100