Skip to content

Commit 089f0b6

Browse files
committed
Minor cleanup of docs
1 parent 5d75f2f commit 089f0b6

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

docs/observability/setup/telemetry.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,23 @@ Grafana Alloy is used to get telemetry. These features are configured by default
1212

1313
## How to get Telemetry
1414

15+
We have to run Grafana Alloy on every single VM to get telemetry.
16+
17+
Alloy is setup to push metrics to a central prometheus instance.
18+
1519
- Copy this docker compose file: [exporters.docker-compose.yml](../../../observability/examples/full/exporters.docker-compose.yml)
16-
- Edit the environment variables to point to your prometheus URL
17-
- Run `docker compose -f exporters.docker-compose.yml up -d ` on every VM you want metrics from
20+
- Edit the environment variables to point to your prometheus URL:
21+
22+
```yaml
23+
environment:
24+
- PROMETHEUS_URL=http://some-host:9090/prometheus # The URL that is running prometheus.
25+
- ALLOY_HOSTNAME=${ALLOY_HOSTNAME-localhost} # Used to add a label to metrics
26+
- ALLOY_IP_ADDRESS=${ALLOY_IP_ADDRESS-localhost} # Used to add a label to metrics
27+
```
28+
29+
Now you have the setup, you will have to run this on every VM you want metrics from. This is a good opportunity to look into orchestrating deployments from a central place.
30+
31+
- On each specific VM, run `docker compose -f exporters.docker-compose.yml up -d `
1832

1933

2034
### Elastic Search Metrics

0 commit comments

Comments
 (0)