-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Native Histogram Support #5907
Comments
Just double checking, I see we are adding native histogram support to query, receiver and sidecar in #6032.
Updated: NVM I think we need additional support for those components. Most of our code are assuming XOR encoding or Aggr encoding only. |
IIUC, only query frontend, Compactor and Ruler needs to support Native histograms? I am wondering if we need to do anything specific in Ruler or it works out of the box by updating the Prometheus dependency. I guess the latter. |
I also think it's the latter, but we will double check and add an e2e test for rulers. |
Downsampling and compaction is blocked by a bug we hit in Prometheus regarding appending histograms to open chunks during compaction, which should be fixed by prometheus/prometheus#12185. |
Ruler does not work with native histograms out of the box. thanos/pkg/promclient/promclient.go Lines 483 to 486 in 5d5d39a
We will look into using the GRPC query API for the ruler so we directly get |
We have PRs now for all components. I just added the last one for rule. |
Is your proposal related to a problem?
Experimental native histogram support was released with Prometheus v0.40.x. #5896 updated Thanos to Prometheus v0.40.1 but without implementing native histograms.
I propose the implementation of native histogram support (behind a feature flag) as a next step in follow up PR(s).
Describe the solution you'd like
We need to go through all Thanos components and check what needs to be changed for native histogram support. So far we identified the following changes are required (list will be updated on new findings):
For each component we need to make sure to have tests in place after implementation and e2e test for functionality provided by multiple components (e.g. ingestion, querying, etc.).
The text was updated successfully, but these errors were encountered: