VictoriaMetrics/deployment/docker
Roman Khavronenko 3458a3d593
Monitoring cluster (#2191)
* dashboards: add `CPU percentage` panel for cluster dashboards

The new panel `CPU percentage` was added instead if adding a limit
to the existing `CPU` panel because dasbhoard may display big number
of components each with own limits. The separate panel should provide
a clear display of CPU load.

Signed-off-by: hagen1778 <roman@victoriametrics.com>

* dashboards: sync vmagent and vmalert changes from single version

Signed-off-by: hagen1778 <roman@victoriametrics.com>

* docker: remove unsupported param from vmagent config

Signed-off-by: hagen1778 <roman@victoriametrics.com>

* alerts: add `TooHighCPUUsage` alert for all VM components

Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-02-15 11:57:58 +02:00
..
base deployment/docker: embed tzdata into prod Go app instead of installing it into base docker image 2021-02-12 04:56:27 +02:00
builder adds CGO build for arm64 (#2102) 2022-02-08 16:26:55 +02:00
provisioning deployment/docker: replace Prometheus with vmagent (#635) 2020-07-17 02:18:03 +03:00
alertmanager.yml deployment: add vmalert+alertmanager services and list of default alerts for cluster version (#1187) 2021-04-05 22:29:04 +03:00
alerts.yml Monitoring cluster (#2191) 2022-02-15 11:57:58 +02:00
docker-compose.yml deployment/docker/docker-compose.yml: update Grafana from v8.3.4 to v8.3.5 2022-02-14 13:22:06 +02:00
Makefile adds release build for macos darwin amd64 and arm64 (#2185) 2022-02-14 17:42:33 +02:00
prometheus.yml Monitoring cluster (#2191) 2022-02-15 11:57:58 +02:00
README.md Vmalert metrics update (#1580) 2021-09-01 12:19:34 +03:00

Docker compose environment for VictoriaMetrics

To spin-up VictoriaMetrics cluster, vmagent, vmalert, Alertmanager and Grafana run the following command:

docker-compose up

For single version check docker compose in master branch.

VictoriaMetrics

VictoriaMetrics cluster in this environment consists of vminsert, vmstorage and vmselect components. Only vmselect has exposed port :8481 and the rest of components are available only inside of 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.

vmagent

vmagent is used for scraping and pushing timeseries 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 creds:

  • login - admin
  • password - admin

Grafana is provisioned by default with following entities:

  • VictoriaMetrics datasource
  • Prometheus datasource
  • VictoriaMetrics overview dashboard