github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

Add Features section

Browse source
This commit is contained in:
Aliaksandr Valialkin 2018-10-13 01:33:14 +03:00 committed by GitHub
parent 9e6b341088
commit 3ad970addc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -1,6 +1,20 @@
## VictoriaMetrics - the best remote storage for Prometheus ## VictoriaMetrics - the best remote storage for Prometheus
### Note - VictoriaMetrics is in alpha stage at the moment
### 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.
- 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.
- 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.
### Useful links
* [Site](https://victoriametrics.com/) * [Site](https://victoriametrics.com/)
* [`WITH` templates playground](https://play.victoriametrics.com/promql/expand-with-exprs) * [`WITH` templates playground](https://play.victoriametrics.com/promql/expand-with-exprs)