A tool to help you parse your log files, written in Python. The goal was to make a tool that will do the grunt work of following your logs in realtime, and to be easily be extended via plugins. Check out our tech blog post on why we wanted Parsible herehttp://tech.yipit.com/2012/08/03/parsible-straightforward-log-parsing/.
There are a few core ideas we tried to bring together in Parsible:
Plugins: We wanted to make the parsers, processors, and outputs all customizable and easy to write. All plugins are autodiscovered on startup and have a very simple format for connecting them together.
Real Time: Parsible will tail your log file as the lines come in, we opted away from a stateful approach where new lines are read in batches since we feel it simplifies the flow and reduces complexity.
Batch Processing: Parsible has a switch to modify the behavior so that it acts like a standard parser. Instead of tailing from the end of the file, it will start at the beginning and exit once it has reached the last line.
Generators: Log files can get big, really big. By leveraging generators Parsible can keep it's memory footprint small and independent of the size of log file. There is no hard restriction on memory, disk, or CPU usage, so be careful when writing your custom plugins.
System Conventions: Since Parsible works with logs it is wise to follow Linux logging conventions. Parsible integrates easily with logrotate.
Parsers: We wanted to make it easy to write custom parsers for whatever type of log file you may be reading. Your custom parser has to follow a few conventions. A simple nginx parser has been included as an example.
Your parser should live inside of the
Your parsing function should start with
parse_, take for example the included nginx parser which contains a function called
The parsing method signature should take one parameter which will consist of one line from the log file. You may parse the line however you see fit, we opted for a regex implementation since it fits nicely with our dictionary output format and we expect our nginx log data to be well structured.
The parsing method can output whatever you like, as it will be fed directly into the processing functions. In our case we found that a dictionary works very well as lightweight storage for the parsed data although this is not required as you get to write the processing functions as well.
Errors from a
parsemethod are swallowed by the same try/except block that handles
processmethods due to lazy evaluation. Currently there is no recording of these occurrences although this behavior can be easily modified.
Processors: Once a line of log data is parsed it is time to do something useful with it. You can have your processors do whatever you wish, although it is suggested that they remain stateless so that you don't have any lingering effects from feeding on large log files over the course of a day. Some sample
process methods can be found in
Your processors should live inside of the
Your parsing function should start with
process_so that the autoloader can find it. For example the sample processor contains functions called
Your parsing method can take in whatever you please. The output of your parsing function will be fed directly to each processor that Parsible was able to discover.
Outputting from parsing methods is up to you. The suggested flow is that you import any output functions you wish to use directly and call them as needed.
Any errors from a
processmethod are currently swallowed and left untracked, although it is very simple to modify this behavior if desired.
Outputs: Output functions are given their own directory to simplify the structure of Parsible. The output functions should be called directly by your code in your
process methods, but it is cleaner to logically separate them inside the plugin system for clarity. Parsible will not attempt to run any
output functions directly. For some example
output functions check out
Log Rotate: We like our code to play nice with our systems, especially for a program like Parsible.
Parsible creates a PID file in
/tmp/parsible.pidso that it is easy to find with other programs.
Parsible reloads the log file on receipt of the USR1 signal. This makes it easy to work with inside of logrotate scripts.
Here is our
logrotate script before Parsible:
postrotate [ ! -f /var/run/nginx.pid ] || kill -USR1 `cat /var/run/nginx.pid` endscript
postrotate [ ! -f /var/run/nginx.pid ] || kill -USR1 `cat /var/run/nginx.pid`; \ [ ! -f /tmp/parsible.pid ] || kill -USR1 `cat /tmp/parsible.pid` endscript
If you don't care to set up
logrotate does not apply, just use
--auto-reload True and it will try to reload the log file after 10 seconds of inactivity.
- Clone Parsible
- Write your parser (or use one someone else wrote!)
- Figure out how you want to process your log lines and write some processors
- Set up any outputs you want to use
- Run it! (We keep ours running under
supervisord, although we have not had issues with crashes.)
parsible.py --log-file /var/log/mylog --pid-file /tmp/parsible.pid --parser parse_nginx
To add debug messages regarding errors that my have been swallowed by Parsible add the
--debug True option to your command line arguments. This can be relatively verbose since it can create multiple messages per processed line so it is not the recommended production configuration.
To enable batch processing mode, just append
--batch-mode True to your command line invocation and Parsible will act as a standard parser that exits at the end of the file. This can be useful for backfilling data or doing ad hoc analysis of old files.
- Python 2.7+ (due to argparse)
- Some tasty logs
Parsible does not gaurantee that every line of your log file will get parsed. When it is first started Parsible seeks to the end of the log file. Additionally, whenever the
USR1 signal is received Parsible will attempt to load the file at the configured location. There is no logic to make sure the current file is fully parsed before switching. This can lead to some lines not being processed during the switchover. If this is a major issue for you please feel free to submit a feature request.
Although Parsible is designed to be lightweight it does not gaurantee it. User created plugins have no restrictions on their behavior and can monopolize resources as they see fit.
Parsible grabs a 'line' based on the return of file.readline(). This means it usually won't handle multiline exceptions very well. Feel free to request the feature if you want it added.
The mispelling of the name of the project is intentional (vs Parsable)
If you are interested in contributing to Parsible here are the steps:
- fork Parsible from here: http://github.com/Yipit/parsible
- Clone your fork
- Hack away
- If you are adding new functionality, document it in the README
- If necessary, rebase your commits into logical chunks, without errors
- Push the branch up to GitHub
- Send a pull request to the Yipit/parsible project.
- We'll take a look and try to get your changes in!
None for now, but feel free to check the commit history!