Aliaksandr Valialkin
|
74c0fb04f3
|
app/vmselect/promql: consistency renaming: candlestick -> rollup_candlestick
|
2019-06-29 03:13:02 +03:00 |
|
Aliaksandr Valialkin
|
796b010139
|
app/vmselect: add candlestick(m[d]) func for returning open, close, low and high rollups on the given time range d
This function is frequently used in financial apps. See https://en.wikipedia.org/wiki/Candlestick_chart
|
2019-06-27 18:46:13 +03:00 |
|
Aliaksandr Valialkin
|
feacfffe89
|
app/vmselect/promql: increase default value for -search.maxPointsPerTimeSeries from 10k to 30k
This may be required for subqueries with small steps. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/77
|
2019-06-24 22:53:18 +03:00 |
|
Aliaksandr Valialkin
|
61926bae01
|
app/vmselect/promql: adjust the provided window only for range functions with dt in denominator
This should fix range function calculations such as `changes(m[d])` where `d` is smaller
than the scrape interval.
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/72
|
2019-06-23 19:27:31 +03:00 |
|
Aliaksandr Valialkin
|
9e1119dab8
|
app/vmselect/promql: ajdust data model to the model used in Prometheus
Do not take into account data points on the range `[timestamp .. timestamp+step)`
when calculating value on the given `timestamp`.
Use only data points from the past when performing these calculations like Prometheus does.
This should reduce discrepancies between results returned by VictoriaMetrics
and results returned by Prometheus.
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/72
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/71
|
2019-06-21 21:54:48 +03:00 |
|
Aliaksandr Valialkin
|
beb479b8f1
|
app/vmselect/promql: use dynamic limit on memory for concurrent queries
|
2019-06-12 23:18:44 +03:00 |
|
Aliaksandr Valialkin
|
54fb8b21f9
|
all: fix misspellings
|
2019-05-25 21:51:11 +03:00 |
|
Aliaksandr Valialkin
|
1836c415e6
|
all: open-sourcing single-node version
|
2019-05-23 00:18:06 +03:00 |
|