-
Notifications
You must be signed in to change notification settings - Fork 505
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
hard-to-understand error with non-existing namers #58
Comments
esbie
pushed a commit
that referenced
this issue
Mar 10, 2016
esbie
pushed a commit
that referenced
this issue
Mar 11, 2016
Tim-Brooks
pushed a commit
to Tim-Brooks/linkerd
that referenced
this issue
Dec 20, 2018
Previously `conduit inject` was configuring the proxy to log a lot of detail, most of which is probably shouldn't be relevant to Conduit users. Configure the proxy to log at the "info" level instead for the proxy itself, and the "warn" level for internal components of the proxy. Validated by manually doing a `conduit inject`, triggering some traffic, and inspecting the logs. Fixes linkerd#57
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you put a namer in the dtab that linkerd doesn't know about, you get the following behavior:
Ideally, the log message would be more informative. For the HTTP error, the 503 part is good, but ideally, the content would be either nothing or a more descriptive error message.
The text was updated successfully, but these errors were encountered: