-
Notifications
You must be signed in to change notification settings - Fork 141
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.
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
Tracing Implementation #63
Comments
Tracing is global config in v2. This is prime candidate for feature dev. We can add this config into the helm chart, and have traefik do all the heavy lifting! |
@SantoDE What did you think about configuring tracing? Did we want to do something like the current traefik helm chart for tracing?
It might be nice to have consistency, and its not a bad way of organizing it? @mmatur did you have any recommendations/suggestions? |
@dtomcej during my research about competitors I can see that all of major competitors install by default prometheus, grafana and jaeger. And the mesh is configure automatically by default. But yeah we need to be able to customize these settings. If we want to propose a helm chart installation we have to as closer as we can of traefik helm configuration. |
Yeah, I agree. Most competitors just do all of that by default. I really like the idea to have it customizable tough. It just gives you more control about your desired state. |
Ok, I will open tickets to implement those into the helm chart! |
Closed by #79 |
How did we want to implement tracing?
Not sure how tracing is implemented in Traefik v2
The text was updated successfully, but these errors were encountered: