VictoriaMetrics/app
Ze'ev Klapow 680a661ec0
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:04:29 -07:00
..
vmagent docs/vmagent.md: clarify that there is no need to specify multiple -remoteWrite.url options when writing data to a single VictoriaMetrics cluster when data replication is needed 2023-03-24 17:56:31 -07:00
vmalert app/vmselect: follow-up for 10ab086366 2023-03-27 15:11:42 -07:00
vmauth docs/vmauth.md: follow-up for 36edba9bfb 2023-03-24 17:56:59 -07:00
vmbackup app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows 2023-03-25 15:09:41 -07:00
vmbackupmanager doc: add vmbackupmanager monitoring section (#3605) 2023-01-05 16:49:59 -08:00
vmctl app/vmctl: follow up after aed59b9029 (#3983) 2023-03-21 09:26:26 -07:00
vmgateway app/vmgateway: add new flag doc 2023-02-27 11:18:37 -08:00
vminsert all: add Windows build for VictoriaMetrics 2023-03-19 23:28:26 -07:00
vmrestore app/{vmbackup,vmrestore}: publish vmbackup and vmrestore binaries for Windows 2023-03-25 15:09:41 -07:00
vmselect fix le buckets when adjacent vmrange is empty (#4021) 2023-03-27 18:04:29 -07:00
vmstorage all: add Windows build for VictoriaMetrics 2023-03-19 23:28:26 -07:00
vmui vmui: heatmap (#3780) 2023-03-26 00:31:21 -07:00