runtime performance metrics
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
What do we need for introspection and metrics?
I propose the following events:
- 'queued' - on request queued
- 'running' - on request running
- 'complete'- on request complete
- 'failed' - on request failed
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
No source file, test, or entry point is named. Start by reading the proposed event list and linked discussion #673; done requires an agreed introspection and metrics scope covering queued, running, complete, and failed events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100