github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-02-19 15:30:17 +00:00
Code Issues Projects Releases Packages Wiki Activity

all: rename Extended PromQL to PromQL extensions

Browse source
This commit is contained in:
Aliaksandr Valialkin 2019-12-12 19:25:45 +02:00
parent bf8cf77694
commit b238997a84
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
app/vmselect/promql/aggr.go
View file

@ -27,7 +27,7 @@ var aggrFuncs = map[string]aggrFunc{
"topk": newAggrFuncTopK(false), "topk": newAggrFuncTopK(false),
"quantile": aggrFuncQuantile, "quantile": aggrFuncQuantile,
// Extended PromQL funcs // PromQL extension funcs
"median": aggrFuncMedian, "median": aggrFuncMedian,
"limitk": aggrFuncLimitK, "limitk": aggrFuncLimitK,
"distinct": newAggrFunc(aggrFuncDistinct), "distinct": newAggrFunc(aggrFuncDistinct),

2
docs/CaseStudies.md
View file

@ -30,7 +30,7 @@ Numbers:
* Enough head room/scaling capacity for future growth, up to 100M active time series. * Enough head room/scaling capacity for future growth, up to 100M active time series.
* Ability to split DB replicas per workload. Alert queries go to one replica, user queries go to another (speed for users, effective cache). * Ability to split DB replicas per workload. Alert queries go to one replica, user queries go to another (speed for users, effective cache).
> Optimizing for those points and our specific workload VictoriaMetrics proved to be the best option. As an icing on a cake we’ve got an [extended PromQL](https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/ExtendedPromQL) - `default 0` and `histogram` are my favorite ones, for example. What we specially like is having a lot of tsdb params easily available via config options, that makes tsdb easy to tune for specific use case. Also worth noting is a great community in [Slack channel](http://slack.victoriametrics.com/) and of course maintainer support. > Optimizing for those points and our specific workload VictoriaMetrics proved to be the best option. As an icing on a cake we’ve got [PromQL extensions](https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/ExtendedPromQL) - `default 0` and `histogram` are my favorite ones, for example. What we specially like is having a lot of tsdb params easily available via config options, that makes tsdb easy to tune for specific use case. Also worth noting is a great community in [Slack channel](http://slack.victoriametrics.com/) and of course maintainer support.
Alex Ulstein, Head of Monitoring, Wix.com Alex Ulstein, Head of Monitoring, Wix.com

2
docs/ExtendedPromQL.md
View file

@ -1,4 +1,4 @@
# Extended PromQL # PromQL extensions
VictoriaMetrics supports [standard PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/) VictoriaMetrics supports [standard PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/)
including [subqueries](https://prometheus.io/blog/2019/01/28/subquery-support/). including [subqueries](https://prometheus.io/blog/2019/01/28/subquery-support/).

2
docs/Home.md
View file

@ -3,7 +3,7 @@
* [Quick start](Quick-Start) * [Quick start](Quick-Start)
* [`WITH` templates playground](https://play.victoriametrics.com/promql/expand-with-exprs) * [`WITH` templates playground](https://play.victoriametrics.com/promql/expand-with-exprs)
* [Grafana playground](http://play-grafana.victoriametrics.com:3000/d/4ome8yJmz/node-exporter-on-victoriametrics-demo) * [Grafana playground](http://play-grafana.victoriametrics.com:3000/d/4ome8yJmz/node-exporter-on-victoriametrics-demo)
* [Extended PromQL](ExtendedPromQL) * [PromQL extensions](ExtendedPromQL)
* [Single-node version](Single-server-VictoriaMetrics) * [Single-node version](Single-server-VictoriaMetrics)
* [FAQ](FAQ) * [FAQ](FAQ)
* [Cluster version](Cluster-VictoriaMetrics) * [Cluster version](Cluster-VictoriaMetrics)