Aliaksandr Valialkin
|
5a4675c528
|
app/vmselect/prometheus: do not return time series with empty list of datapoints from /api/v1/query_range
This matches Prometheus behaviour.
This should fix https://github.com/jacksontj/promxy/issues/329
|
2020-07-20 15:31:21 +03:00 |
|
Aliaksandr Valialkin
|
25f80d320b
|
app/vmselect/prometheus: do not adjust last points in time series with timestamps exceeding the current time
Such timestamps usually mean that the query contains `offset`.
See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/625
|
2020-07-14 12:52:16 +03:00 |
|
Aliaksandr Valialkin
|
acf828a759
|
app/vmselect/prometheus: small fixes on top of 8bb762124a
|
2020-07-05 18:17:06 +03:00 |
|
faceair
|
8bb762124a
|
fix adjust last points avoid influence earlier value (#606)
|
2020-07-05 17:56:54 +03:00 |
|
Aliaksandr Valialkin
|
7b5168adfb
|
app/vmselect/promql: remove NaNs from /api/v1/query_range output like Prometheus does
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/153
|
2019-08-20 23:01:41 +03:00 |
|
Aliaksandr Valialkin
|
54bd21eb4a
|
app/vmselect/prometheus: convert negative times to 0, since they arent supported by the storage
|
2019-07-11 17:07:20 +03:00 |
|
Aliaksandr Valialkin
|
40a6c0d672
|
app/vmselect/prometheus: typo fix
|
2019-07-07 23:34:23 +03:00 |
|
Aliaksandr Valialkin
|
1371024747
|
app/vmselect/prometheus: handle minTime and maxTime values that may be set by Promxy or Prometheus client
Fixes https://github.com/VictoriaMetrics/VictoriaMetrics/issues/88
|
2019-07-07 21:53:48 +03:00 |
|