Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prometheus is good, but it uses file operations on each middleware hook; that might become a bottleneck.
Suggested middleware uses similar metrics, but it keeps statistics in memory and may be queried by the simple task when needed.
As soon as a middleware instance starts within a worker process, requesting stats requires getting stats from each worker middleware instance.
I suggest starting an additional worker task inside middleware for a special pub-sub stat broker, so kiqing its task leads to execution on each main worker process, gathering all results together.
This pull request is just an idea implementation and includes:
I had to bump up the required mypy and black minimal versions to support modern generic syntax.
So I just share the idea of request-oriented statistics gathering via pub-sup broker.