Skip to content

Log grpc write error #37

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

Merged
merged 2 commits into from
Sep 30, 2016
Merged

Log grpc write error #37

merged 2 commits into from
Sep 30, 2016

Conversation

jml
Copy link
Contributor

@jml jml commented Sep 29, 2016

We had a production incident where we couldn't readily identify the cause of 500s because we weren't logging them. This hopefully fixes that.

@juliusv
Copy link
Contributor

juliusv commented Sep 29, 2016

👍 but it actually got changed back to plain proto-over-HTTP by Tom a while ago, but some gRPC naming stuck around. Maybe rename that and the error message?

@jml
Copy link
Contributor Author

jml commented Sep 29, 2016

I couldn't think of a good name, so I deleted the type and shuffled things around a bit. @juliusv, let me know what you think.

@juliusv
Copy link
Contributor

juliusv commented Sep 29, 2016

👍 though the whole thing should be refactored again to use parseRequest for its boilerplate like the other proto-over-HTTP endpoints and as it was before gRPC was introduced: https://github.com/weaveworks/prism/blob/a5213bc48e8558355c0d3ec6c429aeec4ccb30e7/server.go

But maybe in another PR...

@jml jml merged commit 91a7f7d into master Sep 30, 2016
@jml jml deleted the focused-logging branch September 30, 2016 10:26
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 this pull request may close these issues.

2 participants