Lennart Koopmann

I spent my last evenings hacking on a new Graylog2 feature which will be very useful for running powerful analytics on your log messages: The Graylog2 Analytics Shell. The detailled description is in the wiki.

Use this shell to extract information from your log messages. I always like the use case of API monitoring. You could easily find out if that one call is still used by consumers - Or even which consumers are still using it with a simple distinct call:

all.distinct({_oauth_consumer_key}, processed_controller = /^PrivateMessages#.+/)

Watch the shell in action in this short screencast: (Try the full screen mode and HD video)

This is the first working implementation but there is still stuff missing. For example:

• Shell history available with up and down arrow keys
• Improved design and layout
• A history of count and distinct results
• Tab completion (ZOMG!!)
• Saving and sharing of commands
• Short names for streams, to avoid typing the raw stream ID

The shell will be included in the next version: 0.9.6

Post your comments here or discuss in the mailing list.

JMX provides an easy way to monitor your Java applications. In this guide I’ll show you how to use it to monitor values from inside your application. To learn what else you can do with JMX, take a look at the Java Management Extension article on Wikipedia.

The values to monitor are represented by MBean objects. Your MBeans will be organized by the MBeanServer.

Creating the MBeanServer will be our first step:

Read More