VictoriaMetrics/deployment/docker/prometheus.yml

global:
  scrape_interval: 10s

scrape_configs:
  - job_name: 'vmagent'
    static_configs:
      - targets: ['vmagent:8429']
  - job_name: 'vmalert'
    static_configs:
      - targets: ['vmalert:8880']
  - job_name: 'vminsert'
    static_configs:
      - targets: ['vminsert:8480']
  - job_name: 'vmselect'
    static_configs:
      - targets: ['vmselect:8481']
  - job_name: 'vmstorage'
    static_configs:
      - targets: ['vmstorage-1:8482', 'vmstorage-2:8482']
all: open-sourcing cluster version 2019-05-22 23:23:23 +02:00			`global:`
deployment/docker: sync with master branch 2023-01-24 07:59:42 +01:00			`scrape_interval: 10s`
all: open-sourcing cluster version 2019-05-22 23:23:23 +02:00
			`scrape_configs:`
deployment/docker: replace Prometheus with vmagent (#635) * replace Prometheus with vmagent in docker compose env; * cluster dashboard: exclude vmagent from job list; * cluster dasbhoard: reference datasource var instead of datasource name. 2020-07-17 01:18:03 +02:00			`- job_name: 'vmagent'`
all: open-sourcing cluster version 2019-05-22 23:23:23 +02:00			`static_configs:`
deployment/docker: replace Prometheus with vmagent (#635) * replace Prometheus with vmagent in docker compose env; * cluster dashboard: exclude vmagent from job list; * cluster dasbhoard: reference datasource var instead of datasource name. 2020-07-17 01:18:03 +02:00			`- targets: ['vmagent:8429']`
Vmalert metrics update (#1580) * vmalert: remove `vmalert_execution_duration_seconds` metric The summary for `vmalert_execution_duration_seconds` metric gives no additional value comparing to `vmalert_iteration_duration_seconds` metric. * vmalert: update config reload success metric properly Previously, if there was unsuccessfull attempt to reload config and then rollback to previous version - the metric remained set to 0. * vmalert: add Grafana dashboard to overview application metrics * docker: include vmalert target into list for scraping * vmalert: extend notifier metrics with addr label The change adds an `addr` label to metrics for alerts_sent and alerts_send_errors to identify which exact address is having issues. The according change was made to vmalert dashboard. * vmalert: update documentation and docker environment for vmalert's dashboard Mention Grafana's dashboard in vmalert's README in a new section #Monitoring. Update docker-compose env to automatically add vmalert's dashboard. Update docker-compose README with additional info about services. 2021-08-31 11:28:02 +02:00			`- job_name: 'vmalert'`
			`static_configs:`
			`- targets: ['vmalert:8880']`
all: open-sourcing cluster version 2019-05-22 23:23:23 +02:00			`- job_name: 'vminsert'`
			`static_configs:`
			`- targets: ['vminsert:8480']`
			`- job_name: 'vmselect'`
			`static_configs:`
			`- targets: ['vmselect:8481']`
			`- job_name: 'vmstorage'`
			`static_configs:`
Updated docker-compose.yml (#1730) * 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> 2021-10-22 18:26:02 +02:00			`- targets: ['vmstorage-1:8482', 'vmstorage-2:8482']`