-
Notifications
You must be signed in to change notification settings - Fork 0
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
Hook in some basic logging to the service #20
base: main
Are you sure you want to change the base?
Conversation
93f9dff
to
2c05483
Compare
Better clock Co-authored-by: David Genord II <david@collectiveidea.com>
8670c69
to
4336d84
Compare
Ha, Ruby 3.4 build fails because the default hash to_s has changed:
I'm a fan. |
Hash#to_s changed between version creating diffrent string output.
Way simpler than how I was doing this. Still can't decide what else to put in the logs, if anything.
4c4b16b
to
9727aa3
Compare
This reverts commit 4336d84. No longer needed, so let's go back.
We don't need this change anymore, so go back.
bbf59a3
to
350fc13
Compare
* Add it at the top of the middleware stack. * Inherit from Leverage Rack::CommonLogger though we don't use common log format. * Improve handling of response output in when log_level is :debug
350fc13
to
3e2eba2
Compare
Refactored to use a Rack middleware and it is nicer for the common case. The ability to show the response in |
If you're using gzip/deflate, the current |
* Move out of the Logger so we can output the response even when the actual response is gzip/brotli. * Output Twirp objects rather than protobuf/json for readability.
c3313f4
to
e068abb
Compare
Another day, another update. I'm now logging the Twirp object if you set Using the Twirp object seems nice. While it can be fun to see the protobuf object in the logs, it really isn't handy. @albus522 / @darronschall I'm happy with how this all works now. Happy to bikeshed about what format the logs take. I don't actually have opinions there. |
67242fa
to
156e101
Compare
Refactor tests as the block syntax makes checking a little different. Ensure we have a test for exception_raised logging.
156e101
to
02bbbce
Compare
Improved the logs a bit, and I'm liking where it has landed. Now, Only thing left to bikeshed is the log messages themselves. ;) |
First attempt at outputting in some better logging. Not sure what exactly we want to output yet, but throwing this out as an initial idea.