VictoriaMetrics/app
Ze'ev Klapow 8f33561797
fix le buckets when adjacent vmrange is empty (#4021)
There is a bug here where if you have a single bucket like:

foo{vmrange="4.084e+02...4.642e+02"} 2 123

The expected output is three le encoded buckets like:

foo{le="4.084e+02"} 0 123
foo{le="4.642e+02"} 2 123
foo{le="+Inf"} 2 123

This correctly encodes the start and end of the vmrange.
If however, the input contains the previous bucket, and that bucket is
empty then you only get the end le and +Inf out currently, i.e:

foo{vmrange="7.743e+05...8.799e+05"} 5 123
foo{vmrange="6.813e+05...7.743e+05"} 0 123

results in:

foo{le="8.799e+05"} 5 123
foo{le="+Inf"} 5 123

This causes issues when you go to compute a quantile because this means
that the assumed lower bound of the buckets is 0 and this we interpolate
between 0->end rather than the vmrange start->end as expected.
2023-03-27 18:06:08 -07:00
..
vmagent all: follow-up for 7a3e16e774 2023-03-12 01:19:55 -08:00
vmalert all: follow-up for 7a3e16e774 2023-03-12 01:19:55 -08:00
vmauth all: follow-up for 7a3e16e774 2023-03-12 01:19:55 -08:00
vmbackup app/vmbackup: simplify code a bit after 5ba347bd2c 2023-03-24 22:20:20 -07:00
vmbackupmanager doc: add vmbackupmanager monitoring section (#3605) 2023-01-05 16:49:59 -08:00
vmctl app/vmctl: skip series if measurement not found (#3869) 2023-02-27 12:04:48 -08:00
vmgateway docs: update command-line descriptions after 73256fe438 2023-01-27 00:01:14 -08:00
vminsert all: follow-up for 7a3e16e774 2023-03-12 01:19:55 -08:00
vmrestore all: run apk update && apk upgrade in base Alpine Docker image in order to get all the recent security fixes 2023-02-09 14:03:02 -08:00
vmselect fix le buckets when adjacent vmrange is empty (#4021) 2023-03-27 18:06:08 -07:00
vmstorage all: follow-up for 7a3e16e774 2023-03-12 01:19:55 -08:00
vmui security: bump go version to 1.20.2 (#3935) 2023-03-12 01:38:51 -08:00