-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Native Histogram Support #3733
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
Comments
@f1ko , thanks for filing the feature request! Native histograms in Prometheus look promising. Let's wait until they are stabilized and become widely used and then think on how to integrate them into VictoriaMetrics. In the mean time it is recommended using VictoriaMetrics histograms instead. |
Hi! Looks like most of the format of native histograms has been stabilized at this point, and it's largely implementation details that remain. As Mimir now supports ingesting native histograms, and a few of the Prometheus projects now export them, would you consider implementing this prior to full stabilization on the Prometheus side? For context, we're exporting Prometheus metrics from a Rust app, and there aren't yet any ways to export either VictoriaMetrics histograms or Prometheus native histograms in Rust. We'll need to build support ourselves and would prefer to implement the latter for maximum flexibility long term. If VictoriaMetrics might support native histograms within a few months, we'd probably just deal with traditional histograms for a little bit longer. |
Actively using it with k6, waiting the VM supporting. |
Hello @valyala, In your previous comment on this thread, dated January 31, 2023, you mentioned that the proposal for native histograms in Prometheus seemed promising and it was worth waiting for their stabilization and widespread adoption. Given that a significant part of the native histogram format has now been stabilized, as noted in later comments, I am wondering if there are any plans to implement this functionality in VictoriaMetrics soon? This would be especially beneficial for users eager to leverage VictoriaMetrics with Prometheus's latest features. |
@valyala, really waiting for prometheus native histograms support in Victoria Metrics to ship k6 results, any updates here? |
More than two years passed since the introduction of native histograms in Prometheus, and they are still experimental:
The introduction of native histograms in Prometheus resulted in numerous issues and bugs at Prometheus source code. Some of them aren't fixed yet. Due to the facts above, our decision at VictoriaMetrics is to wait until native histograms become non-experimental feature in Prometheus. After that we are going to implement the following features:
We aren't going to add support for Prometheus native histograms storage at VictoriaMetrics, since we believe that VictoriaMetrics histograms are better on every aspect than Prometheus native histograms - they are compatible with Prometheus data model, they are stable since 2019, they can be exposed in plaintext exposition format at |
@valyala what is the expected timeframe for this? |
Is your feature request related to a problem? Please describe
Prometheus v2.40.0 introduces native histograms (as a new experimental feature).
Applications that already want to push native histogram metrics via remote write require an endpoint that support it.
To remain compatibility with Prometheus VictoriaMetrics shall support native histograms (once stable).
Although changes are still likely since it is not marked as stable yet some initial thought regarding the future implementation into VictoriaMetrics may be done already.
Tracking native histogram implementation on Prometheus can be done here.
Describe the solution you'd like
VictoriaMetrics shall support native histograms.
Describe alternatives you've considered
Using Prometheus with native histograms enabled as a remote write endpoint is a valid alternative for applications that require it although a bit expensive if VictoriaMetrics is already in use.
Additional information
No response
The text was updated successfully, but these errors were encountered: