Open
Conversation
Member
Author
|
This is a very preliminary attempt to use eliot for some logging that would be immediately useful to us. We still need to figure out what we want to do with the log messages (they currently go nowhere except in tests) and how we want to extend this logging to other parts of the system. |
Member
Author
|
Oh, bleh. Eliot doesn't support Python 2.6. |
Contributor
|
Do we need to still support Python 2.6? It's pining for fjords. :)
|
Member
Author
|
I've removed it from this branch, at least. We can decide later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our log messages are currently very ad-hoc and really hard to post-process in any useful way.
Using eliot we can log structured data that's a little harder for humans to read but much easier to reassemble into useful information about message flows and such.