Log query and emit metrics for grpc request and multi-stage leaf stage #11838
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.
ServerQueryLogger
numResizes
into prometheus configresizeTimeMs
to be a meter instead of gaugepinot.server.query.log.maxRatePerSecond
to replace the deprecatedpinot.query.scheduler.query.log.maxRatePerSecond
(backward compatible)pinot.server.query.log.droppedReportMaxRatePerSecond
to configure the dropped log report frequencyRelease Notes
New config added for server:
pinot.server.query.log.maxRatePerSecond
: query log max rate (QPS, default 10K)pinot.server.query.log.droppedReportMaxRatePerSecond
: dropped query log report max rate (QPS, default 1)