create a working example of vector internal metrics monitoring

Signed-off-by: Jérémie Drouet <[email protected]>

Author: jdrouet

metric-monitoring/docker-compose.yml

@@ -0,0 +1,24 @@
+version: '3.9'
+
+services:
+  vector:
+    image: timberio/vector:latest-alpine
+    environment:
+      - LOG=info
+    networks:
+      - backend
+    volumes:
+      - ./vector:/etc/vector:ro
+
+  prometheus:
+    image: bitnami/prometheus:latest
+    networks:
+      - backend
+    ports:
+      - 9090:9090
+    volumes:
+      - ./prometheus/prometheus.yml:/opt/bitnami/prometheus/conf/prometheus.yml:ro
+
+networks:
+  backend: {}
+

metric-monitoring/prometheus/prometheus.yml

@@ -0,0 +1,27 @@
+# my global config
+global:
+  scrape_interval:     10s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
+  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
+  # scrape_timeout is set to the global default (10s).
+
+  # Attach these labels to any time series or alerts when communicating with
+  # external systems (federation, remote storage, Alertmanager).
+  external_labels:
+      monitor: 'vector-monitor'
+
+# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
+rule_files:
+  # - "first.rules"
+  # - "second.rules"
+
+# A scrape configuration containing exactly one endpoint to scrape:
+# Here it's Prometheus itself.
+scrape_configs:
+  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
+  - job_name: 'activity'
+
+    # metrics_path defaults to '/metrics'
+    # scheme defaults to 'http'.
+
+    static_configs:
+      - targets: ['vector:9090']

metric-monitoring/vector/vector.toml

@@ -0,0 +1,15 @@
+[sources.random]
+type = "demo_logs"
+format = "json"
+
+[sinks.blackhole]
+type = "blackhole"
+inputs = ["random"]
+
+[sources.internal_metrics]
+type = "internal_metrics"
+
+[sinks.prometheus]
+type = "prometheus_exporter"
+inputs = ["internal_metrics"]
+address = "0.0.0.0:9090"