swarm-otel: scrape VictoriaMetrics through its published name
The store's own /metrics was scraped over loopback, declared under deploy.victoriametrics.enable, so a collector on another host never had a job for it. Declare it as a published target on every host instead, keyed on swarm.victoriametrics.domain, and serve it on the metrics vhost behind the existing authz subrequest. Authelia's per-target rules (one collector rule, then deny) now cover it too. The loopback entry goes, so a single-host swarm scrapes the store once.
This commit is contained in:
parent
6d42abb285
commit
338a767a61
4 changed files with 80 additions and 21 deletions
|
|
@ -172,8 +172,9 @@ Neither container is reachable except through the gateway: both bind
|
|||
loopback, and VictoriaMetrics authenticates nothing itself. The
|
||||
`metrics.<swarm-domain>` vhost forwards only the store's read API (the
|
||||
Prometheus query, series, label and metadata routes, plus the vmui web UI)
|
||||
without a credential. It forwards the collector's OTLP push only with an
|
||||
authelia token, and refuses every other path, the store's write and admin
|
||||
without a credential. It forwards the collector's OTLP push, and the
|
||||
collector's scrape of the store's own `/metrics`, only with an authelia
|
||||
token, and refuses every other path, the store's write and admin
|
||||
API included, with 403. The bare domain redirects to vmui.
|
||||
|
||||
### Logs (VictoriaLogs)
|
||||
|
|
|
|||
Loading…
Reference in a new issue