Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-16 00:41:24 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
693d68f307
VictoriaMetrics/deployment/docker
History
Roman Khavronenko cae148d5c6
dashboards: cluster dashboard update (#3380) 
The purpose of the update is to make the dash more usable
for large installations with many instances. Panels which showed
metrics per-instance (Mem, CPU) now are showing metrics per-job or min/max/avg
aggregations in % instead. This supposed to help immediately to identify
resource shortage and remain usable for small and big installations.

For cases when detailed info is needed, to the bottom of the dashboard
a new row `Drilldown` was added. Panels like Mem or CPU now contain
a `data-link` named `Drilldown` (cis shown on line click) which takes
user to more detailed panel.

The change list is the following:
* bump Grafana version to 9.1.0;
* replace old "Graph" panel with "TimeSeries" panel;
* improve Uptime panel to show number of instances per job;
* show % usage of Mem and CPU instead of absolute values;
* `Caches` row was removed. All needed info for caches is now part of `Troubleshooting`;
* add `Drilldown` section for detailed resource usage;
* add Annotations for Alert triggers. Not all alerts are supposed to be displayed
on the dashboard, but only those with label `show_at: dashboard`.
See `alerts-cluster.yml` change.

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

Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-11-24 13:20:10 -08: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/provisioning/dashboards: sync with master branch after 5714a68ac6 2022-09-21 12:06:01 +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-cluster.yml dashboards: cluster dashboard update (#3380) 2022-11-24 13:20:10 -08:00
alerts-health.yml docker-compose: move TooManyLogs into vm-health alerts set (#3199) 2022-10-05 22:42:31 +03:00
alerts-vmagent.yml app/vminsert: add missing vm_relabel_config_* metrics after 03d88bc066 2022-11-22 00:48:13 +02:00
alerts-vmalert.yml vmalert: bump alerting rules evaluation interval to reasonable 30s (#3374) 2022-11-21 16:48:09 +02:00
alerts.yml docker-compose: move TooManyLogs into vm-health alerts set (#3199) 2022-10-05 22:42:31 +03:00
docker-compose-cluster.yml vmalert: add default list of alerting rules (#3373) 2022-11-21 16:09:47 +02:00
docker-compose.yml vmalert: add default list of alerting rules (#3373) 2022-11-21 16:09:47 +02:00
Makefile deployment/docker: update Go builder from v1.19.2 to v1.19.3 2022-11-05 10:19:24 +02:00
prometheus-cluster.yml deployment/docker: move cluster compose env to master branch (#3130) 2022-09-21 12:03:10 +03:00
prometheus.yml Monitoring cluster (#2191) 2022-02-15 11:57:58 +02:00
README.md deployment/docker: move cluster compose env to master branch (#3130) 2022-09-21 12:03:10 +03:00

README.md

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 this repo.

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

make docker-single-up

To shutdown 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 shutdown 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 VictoriaMetrics;
  • grafana is configured with datasource pointing to VictoriaMetrics;
  • vmalert is configured to query VictoriaMetrics and send alerts state and recording rules back to it;
  • alertmanager is configured to receive notifications from vmalert.

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

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

VictoriaMetrics cluster

VictoriaMetrics cluster environemnt 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 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.

To access vmalert via vmselect 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 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 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.