github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-02-09 15:27:11 +00:00
Code Issues Projects Releases Packages Wiki Activity
VictoriaMetrics/deployment/docker
History
Aliaksandr Valialkin 0a420c4708
deployment/docker: pass -buildvs=false to go build for production builds 
This should resolve the `error obtaining VCS status: exit status 128` error
when the environment contains incorrect version of git or has incorrect access rights
to the directory with VictoriaMetrics source code.

See the following links for additional info:
- https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2508#issuecomment-1117126702 ,
- https://github.com/google/ko/issues/672
- https://github.com/golang/go/issues/49004
2022-05-11 13:57:59 +03: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 deployment/docker: upgrade Go builder for production builds from v1.17.7 to v1.18.0 2022-03-16 14:08:52 +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: added vmalert.proxyURL flag (#2549) 2022-05-06 17:34:09 +03:00
Makefile deployment/docker: pass -buildvs=false to go build for production builds 2022-05-11 13:57:59 +03: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

README.md

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