We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Trace-level logging in the proxy is useful for debugging. Currently to achieve this, users redeploy the proxy with logging turned up: #2703 (comment)
Introduce a CLI command that provides trace-level information from a specific proxy:
# linkerd trace [flags] (RESOURCE) linkerd trace po/pod-foo-bar linkerd trace -n emojivoto deploy/web
This command could follow a similar model to tap, and would complete the linkerd metrics command nicely.
linkerd metrics
The text was updated successfully, but these errors were encountered:
Related to #2005.
Sorry, something went wrong.
No branches or pull requests
Summary
Trace-level logging in the proxy is useful for debugging. Currently to achieve this, users redeploy the proxy with logging turned up:
#2703 (comment)
Proposal
Introduce a CLI command that provides trace-level information from a specific proxy:
# linkerd trace [flags] (RESOURCE) linkerd trace po/pod-foo-bar linkerd trace -n emojivoto deploy/web
This command could follow a similar model to tap, and would complete the
linkerd metrics
command nicely.The text was updated successfully, but these errors were encountered: