Performance monitoring
Open
optimisation
- Dominant language
- Python
- Stars
- 30
- Forks
- 3
- Avg merge
- 9h 22m
- Merged PRs (30d)
- 40
Description
SKS says a key metric is:
How long does it take to go from clicking on an analysis template to the bottom output node grid coming up
We could possibly get this now from clever mining on NGINX logs, but another option is to track it with some kind of instrumentation.
Could then have a performance monitoring page etc
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. First clarify whether the metric should come from NGINX logs or application instrumentation, then define the monitoring page and the exact start and end events that determine when the work is done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100