ada18cd963
* dashboards/vmagent: shuffle panels for better visibility More important error/dropped panels were moved higher on the main row. Network usage panel moved to Resource usage row. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: add Troubleshooting row to show top 5 instances/jobs by churn rate New panels are supposed to show top 5 jobs or targets which generate the most of the churn rate. They were placed into a new row "Troubleshooting". Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: add panels for showing persistent queue saturation New panels were added to Torubleshooting row to show the persistent queue saturation. The corresponding alerts were added and linked to these panels as well. Signed-off-by: hagen1778 <roman@victoriametrics.com> * dashboards/vmagent: add alert "RejectedRemoteWriteDataBlocksAreDropped" New alert suppose to send a notification when vmagent starts to drop data blocks rejected by configured remote write destiantion. Signed-off-by: hagen1778 <roman@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