[go: nahoru, domu]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose metrics on providers state #10376

Open
2 tasks done
the-nando opened this issue Jan 23, 2024 · 4 comments
Open
2 tasks done

Expose metrics on providers state #10376

the-nando opened this issue Jan 23, 2024 · 4 comments
Labels
area/middleware/metrics kind/proposal a proposal that needs to be discussed.

Comments

@the-nando
Copy link
the-nando commented Jan 23, 2024 •
edited
Loading

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?

It would be nice to have metrics to track issues with Providers, under a new space traefik_provider_, e.g. traefik_provider_errors_total{provider="consulCatalog"} x to be able to monitor errors like:

{"level":"error","msg":"Provider connection error failed to get consul catalog data: Get 
\"https://127.0.0.1:8501/v1/catalog/services?stale=\": remote error: tls: bad certificate, retrying in 
615.460936ms","providerName":"consulcatalog","time":"2024-01-19T07:04:38Z"}

At the moment it's not possible to monitor natively such failures. This is similar to #10236 but for another domain.
@jspdown jspdown self-assigned this Jan 25, 2024
@jspdown
Copy link
Contributor
jspdown commented Jan 29, 2024

Hello @the-nando 👋 And thanks for your interest in Traefik.

Could you explain a bit more your use case for this new metric? Especially, why monitoring these from filtered logs (filtered with the providerName field) is not enough?

@the-nando
Copy link
Author

Hi @jspdown 😄 The use case is to monitor providers health / status with Prometheus. Tailing the logs is a possible solution but it requires external tooling / exporters which may not be available, and since Traefik already exports Prometheus metrics it should be possible to have them exported natively without much change.

@jspdown
Copy link
Contributor
jspdown commented Feb 1, 2024

Thanks for the explanation.

We’re unsure about the use case and the traction it will receive. We are going to leave the status as kind/proposal to give the community time to let us know if they would like this idea.
We will reevaluate as people respond.

@jspdown jspdown added kind/proposal a proposal that needs to be discussed. area/middleware/metrics and removed status/0-needs-triage labels Feb 1, 2024
@jspdown jspdown removed their assignment Feb 1, 2024
@ygersie
Copy link
ygersie commented Feb 1, 2024

I would definitely like to add here that it makes sense traefik exposes error rates on provider issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/middleware/metrics kind/proposal a proposal that needs to be discussed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jspdown @ygersie @traefiker @the-nando