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

Namerd access log #2255

Closed
chrisgoffinet opened this issue Mar 19, 2019 · 1 comment · Fixed by #2275
Closed

Namerd access log #2255

chrisgoffinet opened this issue Mar 19, 2019 · 1 comment · Fixed by #2275
Assignees

Comments

@chrisgoffinet
Copy link
Contributor

This is more of a feature request for providing better visibility into what's going on with Namerd. It would be helpful to implement an access log, so that we can see all the requests coming in. There have been cases where we've seen a flood of requests from Linkerd and haven't been able to understand why and what services caused the blip

@dadjeibaah
Copy link
Contributor

@chrisgoffinet, gonna be picking this up pretty soon. I had some questions about what you'd like to show for these access logs.

  • I presume that we are looking for access logs in the common log format. Is there additional information you'd want to see displayed from the incoming request?
  • Are these logs going to stdout? If so what log level is the most appropriate. Already, the TRACE log level is pretty noisy when looking at HTTP/2 related modules in Linkerd.
  • Another sort of related questions was, Are you thinking this would look like the h2AccessLogger for H2 routers?

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

Successfully merging a pull request may close this issue.

2 participants