From b238997a8493785fed1d00b9a04c03cb58d11e41 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 12 Dec 2019 19:25:45 +0200 Subject: [PATCH] all: rename `Extended PromQL` to `PromQL extensions` --- app/vmselect/promql/aggr.go | 2 +- docs/CaseStudies.md | 2 +- docs/ExtendedPromQL.md | 2 +- docs/Home.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/app/vmselect/promql/aggr.go b/app/vmselect/promql/aggr.go index ee9e6977e9..dcd2c499a0 100644 --- a/app/vmselect/promql/aggr.go +++ b/app/vmselect/promql/aggr.go @@ -27,7 +27,7 @@ var aggrFuncs = map[string]aggrFunc{ "topk": newAggrFuncTopK(false), "quantile": aggrFuncQuantile, - // Extended PromQL funcs + // PromQL extension funcs "median": aggrFuncMedian, "limitk": aggrFuncLimitK, "distinct": newAggrFunc(aggrFuncDistinct), diff --git a/docs/CaseStudies.md b/docs/CaseStudies.md index ec46f5eb4c..f96e446203 100644 --- a/docs/CaseStudies.md +++ b/docs/CaseStudies.md @@ -30,7 +30,7 @@ Numbers: * 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). -> 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 diff --git a/docs/ExtendedPromQL.md b/docs/ExtendedPromQL.md index e8fd955783..e9ac32fb64 100644 --- a/docs/ExtendedPromQL.md +++ b/docs/ExtendedPromQL.md @@ -1,4 +1,4 @@ -# Extended PromQL +# PromQL extensions VictoriaMetrics supports [standard PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/) including [subqueries](https://prometheus.io/blog/2019/01/28/subquery-support/). diff --git a/docs/Home.md b/docs/Home.md index e7ed7d48f6..bcb28f8389 100644 --- a/docs/Home.md +++ b/docs/Home.md @@ -3,7 +3,7 @@ * [Quick start](Quick-Start) * [`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) -* [Extended PromQL](ExtendedPromQL) +* [PromQL extensions](ExtendedPromQL) * [Single-node version](Single-server-VictoriaMetrics) * [FAQ](FAQ) * [Cluster version](Cluster-VictoriaMetrics)