If you’re not familiar with graylog2 yet, from the graylog website:
Graylog2 is an open source log management solution that stores your logs in MongoDB. It consists of a server written in Java that accepts your syslog messages via TCP, UDP or AMQP and stores it in the database. The second part is a web interface that allows you to manage the log messages from your web browser.
Although many of the common uses for graylog are for error tracking – and you’ll find a rack adapter that can automatically push your errors to your graylog, I intend to share how i’m using graylog in a different way.
Beyond Tracking Exceptions
I wanted a way to track business events but in a way that wouldn’t require much infrastructure to be written, I also
didn’t want the system to stop working in the event of that infrastructure to be down.
Using graylog, I got the server side with its analytics capable front-end for free. I also benefited from the graylog protocol being UDP to assure that my system and the business event tracking system don’t influence eachother.
Having this kind of front-end was certainly a big plus: