2021-09-01 07:25:07 +00:00
# Docker compose environment for VictoriaMetrics
2022-09-21 08:48:38 +00:00
Docker compose environment for VictoriaMetrics includes VictoriaMetrics components,
[Alertmanager ](https://prometheus.io/docs/alerting/latest/alertmanager/ )
and [Grafana ](https://grafana.com/ ).
2021-09-01 07:25:07 +00:00
2022-09-21 08:48:38 +00:00
For starting the docker-compose environment ensure you have docker installed and running and access to the Internet.
2022-12-06 06:05:31 +00:00
**All commands should be executed from the root directory of [the repo ](https://github.com/VictoriaMetrics/VictoriaMetrics ).**
2021-09-01 07:25:07 +00:00
2022-12-06 06:05:31 +00:00
To spin-up environment for single server VictoriaMetrics run the following command:
2022-09-21 08:48:38 +00:00
```
make docker-single-up
```
2021-09-01 07:25:07 +00:00
2022-12-06 06:05:31 +00:00
To shut down the docker-compose environment for single server run the following command:
2022-09-21 08:48:38 +00:00
```
make docker-single-down
```
2021-09-01 07:25:07 +00:00
2022-09-21 08:48:38 +00:00
For cluster version the command will be the following:
```
make docker-cluster-up
```
2022-12-06 06:05:31 +00:00
To shut down the docker compose environment for cluster version run the following command:
2022-09-21 08:48:38 +00:00
```
make docker-cluster-down
```
## VictoriaMetrics single server
VictoriaMetrics will be accessible on the following ports:
* `--graphiteListenAddr=:2003`
* `--opentsdbListenAddr=:4242`
* `--httpListenAddr=:8428`
The communication scheme between components is the following:
2022-12-06 06:05:31 +00:00
* [vmagent ](#vmagent ) sends scraped metrics to `single server VictoriaMetrics` ;
* [grafana ](#grafana ) is configured with datasource pointing to `single server VictoriaMetrics` ;
* [vmalert ](#vmalert ) is configured to query `single server VictoriaMetrics` and send alerts state
2022-09-21 08:48:38 +00:00
and recording rules back to it;
2022-12-06 06:05:31 +00:00
* [alertmanager ](#alertmanager ) is configured to receive notifications from `vmalert` .
2022-09-21 08:48:38 +00:00
2023-09-26 08:50:10 +00:00
To access Grafana use link [http://localhost:3000 ](http://localhost:3000 ).
2022-09-21 08:48:38 +00:00
To access [vmui ](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#vmui )
use link [http://localhost:8428/vmui ](http://localhost:8428/vmui ).
2023-09-26 08:50:10 +00:00
To access `vmalert` use link [http://localhost:8428/vmalert ](http://localhost:8428/vmalert/ ).
2022-09-21 08:48:38 +00:00
## VictoriaMetrics cluster
2022-12-06 06:05:31 +00:00
VictoriaMetrics cluster environment consists of `vminsert` , `vmstorage` and `vmselect` components.
2023-09-26 08:50:10 +00:00
`vminsert` has exposed port `:8480` , access to `vmselect` components goes through `vmauth` on port `:8427` ,
and the rest of components are available only inside the environment.
2022-09-21 08:48:38 +00:00
2021-09-01 07:25:07 +00:00
The communication scheme between components is the following:
2022-12-06 06:05:31 +00:00
* [vmagent ](#vmagent ) sends scraped metrics to `vminsert` ;
* `vminsert` forwards data to `vmstorage` ;
2023-09-26 08:50:10 +00:00
* `vmselect` s are connected to `vmstorage` for querying data;
* [vmauth ](#vmauth ) balances incoming read requests among `vmselect` s;
* [grafana ](#grafana ) is configured with datasource pointing to `vmauth` ;
* [vmalert ](#vmalert ) is configured to query `vmselect` s via `vmauth` and send alerts state
2022-12-06 06:05:31 +00:00
and recording rules to `vminsert` ;
* [alertmanager ](#alertmanager ) is configured to receive notifications from `vmalert` .
2021-09-01 07:25:07 +00:00
2023-09-26 08:50:10 +00:00
To access Grafana use link [http://localhost:3000 ](http://localhost:3000 ).
2022-09-21 08:48:38 +00:00
2023-09-26 08:50:10 +00:00
To access [vmui ](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#vmui )
use link [http://localhost:8427/select/0/prometheus/vmui/ ](http://localhost:8427/select/0/prometheus/vmui/ ).
To access `vmalert` use link [http://localhost:8427/select/0/prometheus/vmalert/ ](http://localhost:8427/select/0/prometheus/vmalert/ ).
2022-09-21 08:48:38 +00:00
2021-09-01 07:25:07 +00:00
## vmagent
2022-12-06 06:05:31 +00:00
vmagent is used for scraping and pushing time series to VictoriaMetrics instance.
It accepts Prometheus-compatible configuration [prometheus.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/prometheus.yml )
with listed targets for scraping.
2021-09-01 07:25:07 +00:00
[Web interface link ](http://localhost:8429/ ).
2023-09-26 08:50:10 +00:00
## vmauth
[vmauth ](https://docs.victoriametrics.com/vmauth.html ) acts as a [balancer ](https://docs.victoriametrics.com/vmauth.html#load-balancing )
to spread the load across `vmselect` 's. [Grafana ](#grafana ) and [vmalert ](#vmalert ) use vmauth for read queries.
vmauth config is available [here ](ttps://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/auth-cluster.yml )
2021-09-01 07:25:07 +00:00
## vmalert
2023-02-16 18:25:10 +00:00
vmalert evaluates alerting rules [alerts.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts.yml )
2022-12-06 06:05:31 +00:00
to track VictoriaMetrics health state. It is connected with AlertManager for firing alerts,
2021-09-01 07:25:07 +00:00
and with VictoriaMetrics for executing queries and storing alert's state.
[Web interface link ](http://localhost:8880/ ).
## alertmanager
AlertManager accepts notifications from `vmalert` and fires alerts.
2023-02-16 18:25:10 +00:00
All notifications are blackholed according to [alertmanager.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alertmanager.yml ) config.
2021-09-01 07:25:07 +00:00
[Web interface link ](http://localhost:9093/ ).
## Grafana
To access service open following [link ](http://localhost:3000 ).
2022-09-21 08:48:38 +00:00
Default credential:
2021-09-01 07:25:07 +00:00
* login - `admin`
* password - `admin`
Grafana is provisioned by default with following entities:
2022-09-21 08:48:38 +00:00
* `VictoriaMetrics` datasource
* `VictoriaMetrics - cluster` datasource
* `VictoriaMetrics overview` dashboard
* `VictoriaMetrics - cluster` dashboard
* `VictoriaMetrics - vmagent` dashboard
* `VictoriaMetrics - vmalert` dashboard
2023-02-16 18:25:10 +00:00
Remember to pick `VictoriaMetrics - cluster` datasource when viewing `VictoriaMetrics - cluster` dashboard.
2023-08-03 08:21:18 +00:00
## Alerts
See below a list of recommended alerting rules for various VictoriaMetrics components for running in production.
Some of the alerting rules thresholds are just recommendations and could require an adjustment. The list
of alerting rules is the following:
* [alerts-health.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts-health.yml ):
alerting rules related to all VictoriaMetrics components for tracking their "health" state;
* [alerts.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts.yml ):
alerting rules related to [single-server VictoriaMetrics ](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html ) installation;
* [alerts-cluster.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts-cluster.yml ):
alerting rules related to [cluster version of VictoriaMetrics ](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html );
* [alerts-vmagent.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts-vmagent.yml ):
alerting rules related to [vmagent ](https://docs.victoriametrics.com/vmagent.html ) component;
* [alerts-vmalert.yml ](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/alerts-vmalert.yml ):
alerting rules related to [vmalert ](https://docs.victoriametrics.com/vmalert.html ) component;
Please, also see [how to monitor ](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#monitoring )
VictoriaMetrics installations.
2023-09-01 08:45:43 +00:00
## VictoriaLogs server
VictoriaLogs will be accessible on the following port: `--httpListenAddr=:9428`
[Fluent Bit ](https://docs.fluentbit.io/manual ) is used to send logs to VictoriaLogs instance.
Fluent Bit is configured to send logs from running containers to VictoriaLogs instance.
Additionally, it is configured to listen for syslog logs on port `5140` and send them to VictoriaLogs instance.
To access VictoriaLogs UI use link [http://localhost:9428/select/vmui/ ](http://localhost:9428/select/vmui/ ).
Please, also see [how to monitor ](https://docs.victoriametrics.com/VictoriaLogs/#monitoring )
VictoriaLogs installations.
