feat: Add labels for label-based metric scraping #132
Closed
dannygroenewegen
wants to merge 1 commits from
eCommons/traefik:metrics-internal-network into master
pull from: eCommons/traefik:metrics-internal-network
merge into: :master
:master
:rate-limits
:MAINTENANCE
:forwarded-headers
:adding-matrix-room
:pgsql-port-open
:access-log
:anubis-metrics
:trust-forward-header
:large-uploads
:anubis-log-level
:compose.matrix
:garage
:chore-5.0.0+v3.6.10
:feat-release-notes-next
:add-onion-support
:remove-default-timeout
:feat-pull-request-template
:improve-docs
:anubis
:sixsmith-v3-update-only
:feature/irc
:revert-logmaxAge
:qbit
:feature/v3
:error-pages-again
:metrics
:basic-auth
:error-messages-attempt
:error-pages-attempt
:minecraft
:forward-auth-2
:error-pages
:rejig-compose-vars
:self-signed
No labels
Milestone
No items
No Milestone
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
decentral1se (d1)
fauno (fauno)
javielico (Javielico)
jjsfunhouse
kawaiipunk (KawaiiPunk)
knoflook
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
renovate-bot (Comrade Renovate Bot)
simon
stevensting
trav (Trav Fryer)
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/traefik#132
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We're upgrading to monitoring-ng recipe to support label based metrics discovery.
This PR adds prometheus.io labels to compose.metrics.yml so monitoring-ng can auto-discover and scrape Traefik's metrics on the internal network when enabled.
abra.shNice!
Lgtm
Actually on second thought. Why is this not reachable to the outside? I think if the server has that port open the metrics endpoint will be reachable from the outside
Binding to :8082 inside the container isn't the same as exposing it. Traefik only listens on that port for its own networks (proxy and internal). It only becomes reachable from the outside if it's added to a service's
ports:list. Only 80/443 are published in compose.yml. I also checked every other compose.*.yml overlay and none of them adds 8082 toports:either.So, :8082 is only reachable by other containers on the proxy or internal networks.
Thanks for reconfirming!
One final task: can you bump the trafeik yanl Version to 35?
f946692234toad565ee9c9Rebased and updated the config version to v35. I think this is because you're planning to also merge #128 ? But just to check: #126 updated the config to v33, but this hasn't been released yet. So #128 and this PR could also be merged while staying on v33, right? And then, when released, there is a config update from v32->v33 containing all three of these changes?
merged in #132
Pull request closed