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

Investigate config options in filecoin to send traces to external Jaeger service #846

Closed
eefahy opened this issue Aug 31, 2018 · 2 comments
Assignees

Comments

@eefahy
Copy link
Contributor

eefahy commented Aug 31, 2018

No description provided.

@anorth
Copy link
Member

anorth commented Apr 8, 2019

I believe we're exploring different tracing options now. Can we close this one?

@frrist
Copy link
Member

frrist commented Apr 8, 2019

I think we will ultimately end up using Jaeger to view the traces we capture. The current exploration has been related to instrumentation, libp2p has decided to use Opencensus. Filecoin is using Opencensus as well.

I think this issue could be re-titled to: "As a user I can configure my filecoin node to export traces to a tracing client". The issue could then remain in the backlog or icebox, depending on priority of tracing in filecoin, which is currently unclear.

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

No branches or pull requests

5 participants