Query Frontend: add new field for dense native histogram format #6199
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.
What this PR does:
#6151 added support for Ruler to evaluate rules via sending gRPC requests to Query Frontend.
An issue we found out is that the current JSON format query response from Query Frontend doesn't allow Ruler to access the whole information of native histograms. As what Prometheus returns in its Query response is a more compact format of native histogram, not its full format.
With another in progress PR #5527, we can make it possible to return protobuf query response in Query Frontend through Querier. This could make it possible for Ruler to get the full representation of native histograms.
This PR adds a new
rawHistograms
field to Query Frontend protobuf. This field should never be set when using JSON codec and should be only used when using Protobuf codec asked by Ruler.Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]