f7cb850f8d
* Updated docker-compose.yml Added one more Vmstorage to compose and pointed vmselect and vminsert to it. * Update prometheus.yml According to requested changes for new vmstorage * Update docker-compose Added port mapping * Updated docker-compose Set same ports for both storages * Update prometheus.yml Changed target for vmstorage1 * Updated docker compose Changed the flags for vmstorage1 * Update docker compose Changed flags for vmisert and vmselect to point to vmstorage1 * Update docker compose Made the vmstorage names uniform * Update prometheus.ymk * Update docker-compose.yml Removed additional flags as they are using default values. * Update prometheus.yml Put vmstorage targets under the same job * Update prometheus.yml Changed targets format * Update docker-compose.yml Set two different volumes for every vmstorage node * Update deployment/docker/prometheus.yml * Apply suggestions from code review Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com> |
||
|---|---|---|
| .. | ||
| base | ||
| builder | ||
| provisioning | ||
| alertmanager.yml | ||
| alerts.yml | ||
| docker-compose.yml | ||
| Makefile | ||
| prometheus.yml | ||
| 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.
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.
alertmanager
AlertManager accepts notifications from vmalert and fires alerts.
All notifications are blackholed according to alertmanager.yml config.
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