VictoriaMetrics/deployment/docker

Docker compose environment for VictoriaMetrics

Docker compose environment for VictoriaMetrics includes VictoriaMetrics components, Alertmanager and Grafana.

For starting the docker-compose environment ensure you have docker installed and running and access to the Internet. All commands should be executed from the root directory of the repo.

To spin-up environment for single server VictoriaMetrics run the following command:

make docker-single-up

To shut down the docker-compose environment for single server run the following command:

make docker-single-down

For cluster version the command will be the following:

make docker-cluster-up

To shut down the docker compose environment for cluster version run the following command:

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:

• vmagent sends scraped metrics to single server VictoriaMetrics;
• grafana is configured with datasource pointing to single server VictoriaMetrics;
• vmalert is configured to query single server VictoriaMetrics and send alerts state and recording rules back to it;
• alertmanager is configured to receive notifications from vmalert.

To access vmalert use link http://localhost:8428/vmalert.

To access vmui use link http://localhost:8428/vmui.

VictoriaMetrics cluster

VictoriaMetrics cluster environment consists of vminsert, vmstorage and vmselect components. vmselect has exposed port :8481, vminsert has exposed port :8480 and the rest of components are available only inside the environment.

The communication scheme between components is the following:

• vmagent sends scraped metrics to vminsert;
• vminsert forwards data to vmstorage;
• vmselect is connected to vmstorage for querying data;
• grafana is configured with datasource pointing to vmselect;
• vmalert is configured to query vmselect and send alerts state and recording rules to vminsert;
• alertmanager is configured to receive notifications from vmalert.

To access vmalert use link http://localhost:8481/select/0/prometheus/vmalert.

To access vmui use link http://localhost:8481/select/0/prometheus/vmui.

vmagent

vmagent is used for scraping and pushing time series to VictoriaMetrics instance. It accepts Prometheus-compatible configuration prometheus.yml with listed targets for scraping.

Web interface link.

vmalert

vmalert evaluates alerting rules alerts.yml to track VictoriaMetrics health state. It is connected with AlertManager for firing alerts, and with VictoriaMetrics for executing queries and storing alert's state.

Web interface link.

alertmanager

AlertManager accepts notifications from vmalert and fires alerts. All notifications are blackholed according to alertmanager.yml config.

Web interface link.

Grafana

To access service open following link.

Default credential:

• login - admin
• password - admin

Grafana is provisioned by default with following entities:

• VictoriaMetrics datasource
• VictoriaMetrics - cluster datasource
• VictoriaMetrics overview dashboard
• VictoriaMetrics - cluster dashboard
• VictoriaMetrics - vmagent dashboard
• VictoriaMetrics - vmalert dashboard

Remember to pick VictoriaMetrics - cluster datasource when viewing VictoriaMetrics - cluster dashboard.

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: alerting rules related to all VictoriaMetrics components for tracking their "health" state;
• alerts.yml: alerting rules related to single-server VictoriaMetrics installation;
• alerts-cluster.yml: alerting rules related to cluster version of VictoriaMetrics;
• alerts-vmagent.yml: alerting rules related to vmagent component;
• alerts-vmalert.yml: alerting rules related to vmalert component;

Please, also see how to monitor VictoriaMetrics installations.

VictoriaLogs server

VictoriaLogs will be accessible on the following port: --httpListenAddr=:9428

Fluent Bit 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/.

Please, also see how to monitor VictoriaLogs installations.