mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-18 22:52:11 +01:00
6b97044d8a
- moved files from root to VictoriaMetrics folder to be able to mount operator docs and VictoriaMetrics docs independently - added ability to run website locally The following checks are **mandatory**: - [ ] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/).
39 lines
2.2 KiB
Markdown
39 lines
2.2 KiB
Markdown
---
|
|
sort: 1
|
|
weight: 1
|
|
title: Overview of Managed VictoriaMetrics
|
|
menu:
|
|
docs:
|
|
parent: "managed"
|
|
weight: 1
|
|
aliases:
|
|
- /managed-victoriametrics/overview.html
|
|
---
|
|
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.
|
|
|
|
Managed VictoriaMetrics allows users to run Enterprise version of VictoriaMetrics, hosted on AWS, without the need to perform typical
|
|
DevOps tasks such as proper configuration, monitoring, logs collection, access protection, software updates,
|
|
backups, etc. [Try it right now](https://cloud.victoriametrics.com/signUp?utm_source=website&utm_campaign=docs_overview)
|
|
|
|
We run Managed VictoriaMetrics deployments in our environment on AWS and provide easy-to-use endpoints
|
|
for data ingestion and querying. 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;
|
|
* Built-in [Alerting & Recording](https://docs.victoriametrics.com/managed-victoriametrics/alertmanager-setup-for-deployment/#configure-alerting-rules) rules execution;
|
|
* Hosted [Alertmanager](https://docs.victoriametrics.com/managed-victoriametrics/alertmanager-setup-for-deployment/) for sending notifications;
|
|
* Every Managed VictoriaMetrics deployment runs in an isolated environment, so deployments cannot interfere with each other;
|
|
* Managed VictoriaMetrics deployment can be scaled up or scaled down in a few clicks;
|
|
* Automated backups;
|
|
* Pay only for the actually used resources - compute, storage, traffic.
|