mafintosh / mafintosh/event-loop-delay
emit a warning if the event loop delay is over a user-determined threshold.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Accumulated event loop delay is great if we need it for stats purposes, however it will always grow to infinity. In long-running processes, something that is more valuable is to know if the event loop delay grows over a given threshold, plus the latest, point-in-time delay.
This enables 503 protection like https://github.com/mcollina/loopbench/blob/master/example.js#L20-L23.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests; start by inspecting the repository's event-loop delay sampler and the linked loopbench example. Define the user threshold and point-in-time delay behavior, then verify that long-running processes receive the requested warning and current delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability-sre, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100