open-telemetry / open-telemetry/opentelemetry-python-contrib
Event loop metrics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem?
Cooperative multitasking works great until something doesn't cooperate. It is then critical to identify situations where the event loop becomes blocked for too long
Describe the solution you'd like
A histogram showing the event loop lag would be helpful
Describe alternatives you've considered
Implementing it myself
Additional context
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 reading the linked New Relic, OpenTelemetry JavaScript, and prom-client event-loop-lag implementations to compare how event-loop delay is measured and exposed. Define the histogram's lag measurement and metric behavior, then verify that the resulting event-loop lag metric is emitted as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100