-
Notifications
You must be signed in to change notification settings - Fork 218
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 StormHandler for logging #58
Add StormHandler for logging #58
Conversation
This reverts commit 4d63f72.
Conflicts: streamparse/__init__.py
Conflicts: streamparse/ipc.py
…with Python logging
I know logging is pretty boring stuff, but any thoughts on this? |
Oh, I missed this PR when it opened. Really like it, @dan-blanchard. I'll merge this soon. |
@msukmanowsky Can you give this a review? |
Big 👍 on this and falls under the "why didn't I think of that?" category. Thanks @dan-blanchard! |
Add StormHandler for logging
Now I've just got to add the same thing to IO::Storm using |
@codywilbourn I'm not sure if it was intentional, but you left this PR off the release notes for 1.1.0. It just seems like the kind of thing people might want to switch to using. 😄 |
Missed it looking over changes. Added to CHANGES.md as well as Github release notes. |
Thanks! |
I was updating a bunch of code to use Storm for logging instead of Python logging, and I was noticing a substantial performance degradation, since the logging level was only being checked on the Storm side.
This patch adds a
StormHandler
class that can be used to quickly update any Python code to send logging messages to Storm.