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

optional to enable tracing for linkerd/namerd/namer/tracing requests #1348

Open
siggy opened this issue May 26, 2017 · 0 comments
Open

optional to enable tracing for linkerd/namerd/namer/tracing requests #1348

siggy opened this issue May 26, 2017 · 0 comments

Comments

@siggy
Copy link
Member

siggy commented May 26, 2017

linkerd currently disables tracing for its own internal requests involving linkerd, namerd, namers, and tracing. the intent is to keep a user's zipkin or tracing data strictly for their own service requests.

however, there are cases where tracing for these internal requests is useful. specifically, for debugging linkerd/namerd issues. propose adding a config option to enable tracing for internal requests. this change would probably start with a search for all calls to Trace.letClear.

Tim-Brooks pushed a commit to Tim-Brooks/linkerd that referenced this issue Dec 20, 2018
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

1 participant