Thank you so much Julius! I think this solution works great. Just what I
was looking for with recording rules.
On Monday, January 29, 2024 at 10:11:12 AM UTC-8 Julius Volz wrote:
> The buckets are differentiated via an "le" label (at least for the
> cumulative histogram variant, for a non-cumul
The buckets are differentiated via an "le" label (at least for the
cumulative histogram variant, for a non-cumulative one you can make up your
own bucket upper/lower bound label names), and time series are identified
by their metric name and label set. So the recording rules for the
different bucke
I like your approach Julius. But I have a question about all of the buckets
that I create. If I create all of the buckets with the same output metric
name, will each bucket overwrite the previous buckets? If not, will the
output metric name now be a histogram that contains all of the buckets?
T
For the histogram buckets, is your intention to have a few preconfigured
"age" buckets like 0s-15s, 0s-1m, 0s-5m, and so on (cumulative buckets, all
starting at 0, as in normal Prometheus histograms), and then a count for
how many timestamps you have that fall into each age bucket?
You could make
I have a metric I'm collecting which is a gauge vector of timestamps. I'd
like to take each one of those timestamps and subtract it from the time now
and turn it into a histogram. Can I do this with recording rules?
Right now I have a gauge vector of:
.
I'd like a histogram of [timeNow - timest
5 matches
Mail list logo
