From bf8cf7769499f399ff4d4d0adecb0d56c7ebb9cd Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 12 Dec 2019 14:54:37 +0200 Subject: [PATCH] docs: sync with master branch --- docs/CaseStudies.md | 2 +- docs/Single-server-VictoriaMetrics.md | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/CaseStudies.md b/docs/CaseStudies.md index 6e25aaa89b..ec46f5eb4c 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 - `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 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. Alex Ulstein, Head of Monitoring, Wix.com diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 0c9acc487c..241af1b334 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -510,7 +510,8 @@ before actually deleting the metrics. Send a request to `http://:8428/api/v1/export?match[]=`, where `` may contain any [time series selector](https://prometheus.io/docs/prometheus/latest/querying/basics/#time-series-selectors) -for metrics to export. The response would contain all the data for the selected time series in [JSON streaming format](https://en.wikipedia.org/wiki/JSON_streaming#Line-delimited_JSON). +for metrics to export. Use `{__name__!=""}` selector for fetching all the time series. +The response would contain all the data for the selected time series in [JSON streaming format](https://en.wikipedia.org/wiki/JSON_streaming#Line-delimited_JSON). Each JSON line would contain data for a single time series. An example output: ```