mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-01 14:47:38 +00:00
40 lines
2.2 KiB
Markdown
40 lines
2.2 KiB
Markdown
---
|
|
sort: 26
|
|
---
|
|
|
|
# Managed VictoriaMetrics
|
|
|
|
VictoriaMetrics is a fast and easy-to-use monitoring solution and time series database.
|
|
It integrates well with existing monitoring systems such as Grafana, Prometheus, Graphite,
|
|
InfluxDB, OpenTSDB and DataDog - see [these docs](https://docs.victoriametrics.com/#how-to-import-time-series-data) for details.
|
|
|
|
The most common use cases for VictoriaMetrics are:
|
|
* Long-term remote storage for Prometheus;
|
|
* More efficient drop-in replacement for Prometheus and Graphite
|
|
* Replacement for InfluxDB and OpenTSDB, which uses lower amounts of RAM, CPU and disk;
|
|
* Cost-efficient alternative for DataDog.
|
|
|
|
We are glad to announce the availability of Managed VictoriaMetrics
|
|
at AWS Marketplace - [try it right now](https://aws.amazon.com/marketplace/pp/prodview-4tbfq5icmbmyc)!
|
|
|
|
Managed VictoriaMetrics allows users running VictoriaMetrics at AWS without the need to perform typical
|
|
DevOps tasks such as proper configuration, monitoring, logs collection, access protection, software updates,
|
|
backups, etc.
|
|
|
|
We run Managed VictoriaMetrics instances in our environment at AWS while providing easy-to-use endpoints
|
|
for data ingestion and querying. And the VictoriaMetrics team takes care of optimal configuration and software
|
|
maintenance.
|
|
|
|
Managed VictoriaMetrics comes with the following features:
|
|
|
|
* It can be used as a Managed Prometheus - just configure Prometheus or vmagent to write data to Managed VictoriaMetrics and then use the provided endpoint as a Prometheus datasource in Grafana;
|
|
* Every Managed VictoriaMetrics instance runs in an isolated environment, so instances cannot interfere with each other;
|
|
* Managed VictoriaMetrics instance can be scaled up or scaled down in a few clicks;
|
|
* Automated backups;
|
|
* Pay only for the actually used compute resources - instance type, disk and network.
|
|
|
|
See more about Managed VictoriaMetrics in the following articles:
|
|
* [Managed VictoriaMetrics announcement](https://victoriametrics.com/blog/managed-victoriametrics-announcement)
|
|
* [Pricing comparison for Managed Prometheus](https://victoriametrics.com/blog/managed-prometheus-pricing/)
|
|
* [Monitoring Proxmox VE via Managed VictoriaMetrics and vmagent](https://victoriametrics.com/blog/proxmox-monitoring-with-dbaas/)
|
|
|