-
Notifications
You must be signed in to change notification settings - Fork 161
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
Add troubleshooting page #128
Comments
cc @pgadige |
Thank you @jpkrohling ! I've begun working on it. Will get more inputs before making a PR. |
https://medium.com/jaegertracing/help-something-is-wrong-with-my-jaeger-installation-68874395a7a6 @jpkrohling your blog can go into this doc |
Would a reference to the blog post be better, or do you think that duplicating the content is worth it? |
Let’s start with the link so that we at least have a page in the docs. Longer term I think it would be better to have the content in the docs directly so that other people could edit it. |
Looking at the doc, I think one other aspect people often have issues with is why the connections are not succeeding. We obviously cannot write an exhaustive troubleshooting for this, but perhaps there are some common mistakes? I think one of them is people forget that when running in the container, the |
Requirement - what kind of business use case are you trying to solve?
We are seeing a lot of “cannot see spans” questions. Internally we have a troubleshooting guide we should make public to assist users with troubleshooting.
Convert blog post linked from https://www.jaegertracing.io/docs/1.13/troubleshooting/ to the actual docs
The text was updated successfully, but these errors were encountered: