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

tracer: option to use multiple exporters instead of just one #181

Open
odeke-em opened this issue May 24, 2018 · 6 comments
Open

tracer: option to use multiple exporters instead of just one #181

odeke-em opened this issue May 24, 2018 · 6 comments

Comments

@odeke-em
Copy link
Member

I am just wrapping up some presentations and noticed that currently all the signatures require just one exporter, unless am mistaken. I'd like to use Zipkin, Stackdriver Tracing and Jaeger at the same time.

I believe I should be able to register infinitely many exporters and have the same data exported to each one of them -- as this accomplishes one of the benefits of OpenCensus i.e. multiplicity of backends and no single vendor lock-in.

Thank you.

@chingor13
Copy link
Member

I would suggest creating a MultiExporter that implements the base exporter interface and accepts many exporters in the constructor.

@liyanhui1228 liyanhui1228 self-assigned this May 25, 2018
@liyanhui1228
Copy link
Contributor

@chingor13 Thanks for the suggestion!

@odeke-em
Copy link
Member Author

Great suggestion @chingor13, thank you! Thank you @liyanhui1228 too for taking this on!

@flands
Copy link
Collaborator

flands commented Nov 13, 2018

@liyanhui1228 any update on this? very much needed. /cc @c24t

@c24t
Copy link
Member

c24t commented Nov 14, 2018

@flands I put up an exploratory PR at #397, if this approach works for you we can get (something like) it merged in later.

@flands
Copy link
Collaborator

flands commented Nov 14, 2018

@c24t thanks! I will try it out and let you know.

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

No branches or pull requests

5 participants