From fa97c66c8b0541d9c2ff20a08eca43b1e51ea9e6 Mon Sep 17 00:00:00 2001 From: Matthias Wirth Date: Fri, 15 Nov 2024 10:13:45 +0100 Subject: [PATCH] fix prometheus port description remove unused PROMETHEUSPORT env var from readme --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index de1b926..a4bb066 100644 --- a/README.md +++ b/README.md @@ -131,8 +131,8 @@ The general principle behind the port numbering, is: | `31004/tcp` | MLATHUB Beast protocol input | | `31005/tcp` | MLATHUB Beast protocol output | | `31006/tcp` | MLATHUB Beast-reduce protocol output | -| `9273/tcp` | Prometheus web interface with data from `readsb` | -| `9274/tcp` | Prometheus web interface with data from `Telegraf` | +| `9273/tcp` | Prometheus http endpoint with data from `telegraf` | +| `9274/tcp` | Prometheus http endpoint with data from `readsb` | | `80/tcp` | Tar1090 (map) web interface | Any of these ports can be made available to the host system by using the `ports:` directive in your `docker-compose.yml`. The container's web interface is rendered to port `80` in the container. This can be mapped to a port on the host using the docker-compose `ports` directive. In the example [`docker-compose.yml`](docker-compose.yml) file, the container's Tar1090 interface is mapped to `8080` on the host system, and ports `9273-9274` are exposed as-is: @@ -907,7 +907,6 @@ In order for Telegraf to serve a [Prometheus](https://prometheus.io) endpoint, t | Variable | Description | | ------------------- | ------------------------------------------------------------------------ | | `PROMETHEUS_ENABLE` | Set to `true` for a Prometheus endpoint on `http://0.0.0.0:9273/metrics` | -| `PROMETHEUSPORT` | TCP port for the Prometheus endpoint. Default value is `9273` | ### Output from Ultrafeeder to InfluxDBv2