You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doesn't look like this has been asked here before. One thing my team is looking for is the ability to specify histogram buckets when registering a histogram. This can currently be done at the exporter level, but there are a few reasons why this would be useful at the registration level. One reason being ease of configuration. A library should be able to suggest an appropriate bucket distribution that a consumer can then accept by default or override. This would also provide a unified interface for exporters to support which can help with making exporters more compatible with each other. Not sure exactly what the api should look like, perhaps:
describe_histogram!("my_hist","histogram with exponential buckets").with_exp_buckets(0.1,1.5,25);
The text was updated successfully, but these errors were encountered:
This is not the first time this request has been made, but in general, I've consciously avoided providing an API like this because it forces particular decisions around using histograms that I believe are better left as an exporter concern.
At a high level, doing this right now would mean changing the recorder API in a way that I'm not willing to do. This change would only benefits Prometheus users, and that's too much of an idiosyncrasy to bake into the core API. I do have thoughts/plans around a future API change to support for generic/arbitrary metric metadata, one that could potentially support defining exporter-specific details that doesn't force the API to take on such Prometheus-specific details... but that's a ways off.
This is hopefully something that can be addressed before that by Prometheus finally releasing native histogram support as GA.
Doesn't look like this has been asked here before. One thing my team is looking for is the ability to specify histogram buckets when registering a histogram. This can currently be done at the exporter level, but there are a few reasons why this would be useful at the registration level. One reason being ease of configuration. A library should be able to suggest an appropriate bucket distribution that a consumer can then accept by default or override. This would also provide a unified interface for exporters to support which can help with making exporters more compatible with each other. Not sure exactly what the api should look like, perhaps:
The text was updated successfully, but these errors were encountered: