From f71a7110368c447e7a2a305e3ca937d4645bb577 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Sat, 13 Oct 2018 01:42:30 +0300 Subject: [PATCH] Fix urls to wiki pages --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 21c40dff9..ceba38c51 100644 --- a/README.md +++ b/README.md @@ -3,12 +3,12 @@ ### VictoriaMetrics features -- Simple configuration. Just copy-n-paste remote storage URL to Prometheus config and that's it! See [Quick Start](Quick-Start) for more info. +- Simple configuration. Just copy-n-paste remote storage URL to Prometheus config and that's it! See [Quick Start](https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Quick-Start) for more info. - Reduced maintenance overhead. Prometheus local storage retention may be set to the minimum possible value - `--storage.tsdb.retention=2h` - when using VictoriaMetrics remote storage. This effectively makes Prometheus stateless, so it may be run as a stateless service in Kubernetes / Docker. - Insertion rate scales to millions of metric values per second. - Storage scales to millions of metrics with trillions of metric values. - Wide range of retention periods - from 1 month to 5 years. Users may create different projects (aka `storage namespaces`) with different retention periods. -- Full [PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/) support. Additionally, VictoriaMetrics extends PromQL with useful features. See [Extended PromQL](ExtendedPromQL) for more details. +- Full [PromQL](https://prometheus.io/docs/prometheus/latest/querying/basics/) support. Additionally, VictoriaMetrics extends PromQL with useful features. See [Extended PromQL](https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/ExtendedPromQL) for more details. - Fast query engine. It excels on heavy queries over thousands of metrics with millions of metric values. - The lowest price on the market. We can afford this thanks to cost-effective VictoriaMetrics core. - The same remote storage URL may be used by multiple Prometheus instances collecting distinct metric sets, so all these metrics may be used in a single query (aka `global querying view`). This works ideally for multiple Prometheus instances located in different subnetworks / datacenters.