More metrics
This commit is contained in:
parent
358b344916
commit
ca9fed7b67
5 changed files with 60 additions and 19 deletions
|
@ -1099,7 +1099,7 @@ If a non-200 HTTP status code is returned or if the returned `health` field is `
|
|||
|
||||
See [Installation for Docker](install.md#docker) for an example of how this could be used in a `docker-compose` environment.
|
||||
|
||||
## Metrics
|
||||
## Monitoring
|
||||
If configured, ntfy can expose a `/metrics` endpoint for [Prometheus](https://prometheus.io/), which can then be used to
|
||||
create dashboards and alerts (e.g. via [Grafana](https://grafana.com/)).
|
||||
|
||||
|
@ -1108,7 +1108,7 @@ listen address. Metrics may be considered sensitive information, so before you e
|
|||
doing, and/or secure access to the endpoint in your reverse proxy.
|
||||
|
||||
- `enable-metrics` enables the /metrics endpoint for the default ntfy server (i.e. HTTP, HTTPS and/or Unix socket)
|
||||
- `metrics-listen-http` exposes the metrics endpoint via a dedicated [IP]:port. If set, this option implicitly
|
||||
- `metrics-listen-http` exposes the metrics endpoint via a dedicated `[IP]:port`. If set, this option implicitly
|
||||
enables metrics as well, e.g. "10.0.1.1:9090" or ":9090"
|
||||
|
||||
=== Using default port
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue