VictoriaMetrics/deployment/docker/vm-datasource/docker-compose.yml

services:
  grafana:
    container_name: grafana
    image: grafana/grafana:10.4.2
    depends_on:
      - "victoriametrics"
    ports:
      - 3000:3000
    volumes:
      - grafanadata:/var/lib/grafana
      - ./provisioning/datasources/victoriametrics-datasource/single.yml:/etc/grafana/provisioning/datasources/single.yml
      - ./provisioning/dashboards:/etc/grafana/provisioning/dashboards
      - ./provisioning/plugins/:/var/lib/grafana/plugins
      - ./../../dashboards/vm/victoriametrics.json:/var/lib/grafana/dashboards/vm.json
      - ./../../dashboards/vm/vmagent.json:/var/lib/grafana/dashboards/vmagent.json
      - ./../../dashboards/vm/vmalert.json:/var/lib/grafana/dashboards/vmalert.json
    environment:
      - "GF_INSTALL_PLUGINS=https://github.com/VictoriaMetrics/victoriametrics-datasource/releases/download/v0.10.1/victoriametrics-datasource-v0.10.1.zip;victoriametrics-datasource"
      - "GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS=victoriametrics-datasource"
    networks:
      - vm_net
    restart: always
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113 2024-01-22 14:45:31 +00:00			`services:`
			`grafana:`
			`container_name: grafana`
deployment: set consistent Grafana version for VM datasource env Signed-off-by: hagen1778 <roman@victoriametrics.com> 2024-06-25 11:57:52 +00:00			`image: grafana/grafana:10.4.2`
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113 2024-01-22 14:45:31 +00:00			`depends_on:`
			`- "victoriametrics"`
			`ports:`
			`- 3000:3000`
			`volumes:`
			`- grafanadata:/var/lib/grafana`
deployment: separate datasource between single and cluster versions (#7119) Before, single and cluster deployments were provisioned with both Grafana datasources: single and cluster. But this resulted into a problem: single DS didn't work for cluster and vice versa. See https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7113 This PR splits datasource file into 2 files: single and cluster. Now, these files are separately provisioned to single and cluster deployments correspondingly. Signed-off-by: hagen1778 <roman@victoriametrics.com> 2024-09-27 17:08:05 +00:00			`- ./provisioning/datasources/victoriametrics-datasource/single.yml:/etc/grafana/provisioning/datasources/single.yml`
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113 2024-01-22 14:45:31 +00:00			`- ./provisioning/dashboards:/etc/grafana/provisioning/dashboards`
			`- ./provisioning/plugins/:/var/lib/grafana/plugins`
			`- ./../../dashboards/vm/victoriametrics.json:/var/lib/grafana/dashboards/vm.json`
			`- ./../../dashboards/vm/vmagent.json:/var/lib/grafana/dashboards/vmagent.json`
			`- ./../../dashboards/vm/vmalert.json:/var/lib/grafana/dashboards/vmalert.json`
			`environment:`
deployment/docker: update datasource versions to the latest releases (#7396) ### Describe Your Changes Updated the versions of the data sources to the latest releases ### Checklist The following checks are mandatory: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). 2024-10-30 21:18:38 +00:00			`- "GF_INSTALL_PLUGINS=https://github.com/VictoriaMetrics/victoriametrics-datasource/releases/download/v0.10.1/victoriametrics-datasource-v0.10.1.zip;victoriametrics-datasource"`
deployment/docker: clean up loading of victoriametrics-datasource (#5793) Currently the docker-compose examples for loading `victoriametrics-datasource` uses 2 environment variables: - `GF_ALLOW_LOADING_UNSIGNED_PLUGINS` - `GF_DEFAULT_APP_MODE` I believe both of the env vars are trying to achieve the same thing. `GF_DEFAULT_APP_MODE` disables code signing for all plugins and `GF_ALLOW_LOADING_UNSIGNED_PLUGINS` intends to disable code signing for just `victoriametrics-datasource`. Keeping the scope narrowed to just `victoriametrics-datasource` would be preferable in this case. Unfortunately `GF_ALLOW_LOADING_UNSIGNED_PLUGINS` is misspelled. According to [grafana docs](https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#override-configuration-with-environment-variables), the format is supposed to be `GF_<SectionName>_<KeyName>`. In other words the current env var is missing the section name. This PR proposes to: 1. fix the typo 2. remove the global disablement of code signing Alternatively, if you prefer to keep codesigning disabled globally, please remove `GF_ALLOW_LOADING_UNSIGNED_PLUGINS` env var as it confuses things 2024-02-20 13:31:15 +00:00			`- "GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS=victoriametrics-datasource"`
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113 2024-01-22 14:45:31 +00:00			`networks:`
			`- vm_net`
			`restart: always`