Aliaksandr Valialkin
|
96342f1422
|
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:54 +03:00 |
|
Aliaksandr Valialkin
|
d0bf4393a9
|
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:25 +03:00 |
|
Aliaksandr Valialkin
|
0eac538fc8
|
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:25 +03:00 |
|
Aliaksandr Valialkin
|
f334908c22
|
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:55:25 +03:00 |
|
Aliaksandr Valialkin
|
947bc16f8c
|
app/vmselect/promql: use dynamic limit on memory for concurrent queries
|
2019-06-12 23:18:23 +03:00 |
|
Aliaksandr Valialkin
|
bdf696ef18
|
all: fix misspellings
|
2019-05-25 21:51:24 +03:00 |
|
Aliaksandr Valialkin
|
24578b4bb1
|
all: open-sourcing cluster version
|
2019-05-23 00:25:38 +03:00 |
|
Aliaksandr Valialkin
|
1836c415e6
|
all: open-sourcing single-node version
|
2019-05-23 00:18:06 +03:00 |
|