grafana: the published vhost refuses /metrics
Grafana runs with metrics.enabled and no basic_auth_*, so its Prometheus exposition was served to any anonymous client of grafana.<swarm> through the published vhost's `location "/"`. Add an exact-match `= /metrics` location returning 403 there. The loopback `grafana-metrics` vhost and the collector's scrape of it are unchanged. Comments on the metricsPort option and the loopback vhost now state that the published vhost refuses /metrics; the gateway doc says the same. A module-eval case pins the refusing location and that `/` still proxies.
This commit is contained in:
parent
eba6428b6b
commit
6c9c2cef45
4 changed files with 28 additions and 3 deletions
|
|
@ -72,7 +72,9 @@ in
|
|||
{option}`services.hyperhive.swarm.otel.scrapeTargets` has: those
|
||||
targets are trusted by *proximity* rather than by credential.
|
||||
Deliberately **not** the published `grafana.<domain>` vhost, which
|
||||
would put an authorization decision in front of a scrape.
|
||||
would put an authorization decision in front of a scrape: that vhost
|
||||
answers `/metrics` with 403, because Grafana serves it without
|
||||
authentication.
|
||||
|
||||
The number itself is arbitrary and free today;
|
||||
`state/eval-port-collisions.sh` is what keeps it that way, since a
|
||||
|
|
|
|||
Loading…
Reference in a new issue