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.

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

Feature: Tracing providers #28

Closed
heitorlessa opened this issue May 4, 2020 · 1 comment
Closed

Feature: Tracing providers #28

heitorlessa opened this issue May 4, 2020 · 1 comment

Comments

@heitorlessa
Copy link
Contributor

Ability to switch Tracing providers while keeping the same UX

@heitorlessa
Copy link
Contributor Author

After research, all tracers have distinct initialization, nomenclature (some OpenTracing, some unique to them like X-Ray), and not all of them handle async, thread-safe operations the same way.

To support this, it'd mean bringing lots of complexity to maintain, and unknown bugs. Customers can choose not to use the Tracer middleware if they already have their own Tracer provider.

Closing as we will not implement and will instead provide X-Ray escape hatches to customers, and simplify Tracer scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant