matomo-org / matomo-org/plugin-QueuedTracking
Could queuedtracking:monitor command also report number of requests processed per second?
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 87
- Forks
- 41
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 7
Description
Could queuedtracking:monitor command also report number of requests processed per second?
Currently output looks like this:
Queue is enabled
The command ./console queuedtracking:process has to be executed to process request sets within queue
Up to 16 workers will be used
Processor will start once there are at least 100 request sets in the queue
43970 (2863+2646+2970+2818+2724+2776+2608+2619+2874+2625+2788+2688+2457+2624+3050+2840) request sets left in queue. disabled used memory (disabled peak). 0 workers active.
It would be interesting if it could also say:
1,555 requests were processed in the last second
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
Start with the queuedtracking:monitor command and inspect how its current queue and worker status output is assembled. Trace where processed-request counts are available, then add a per-second rate to the report. Done means the command displays the processing rate alongside the existing queue status without disrupting the current output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100