Source

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><htmlxmlns="http://www.w3.org/1999/xhtml"><head><metaname="author"content="Basho Technologies"/><metaname="description"content="riak - a decentralized key value store - basho technologies"/><metaname="keywords"content="riak nosql decentralized distributed key value store"/><metahttp-equiv="content-type"content="text/html;charset=utf-8"/><linkrel="stylesheet"href="css/style-1c.css"type="text/css"/><title>Riak - Setup</title></head><body><divid="content"><h1><spanclass="hr"></span><ahref="/">riak</a></h1><ulid="top"><li><ahref="/">Home</a></li><li><ahref="http://bitbucket.org/justin/riak/">Source Code</a></li><li><ahref="edoc/index.html">API Docs</a></li><li><ahref="faq.html">FAQ</a></li><li><ahref="contact.html">Contact</a></li></ul><divid="intro"><p>Events in Riak</p></div><divid="left"><h3>Event-Driven (not interrupt-driven) Operations</h3><p>One of the most difficult things about operating a distributed system is extracting useful and actionable intelligence from all of the many possible sources of data at hand. Sometimes it's hard to find all the logs and information you need; at other times you're drowning in log files and still can't figure out what to do.</p><p>Riak gives you flexibility and power in gathering the data you need for effective monitoring, debugging, and operations.</p><p>Using a simple event-handler API, you can write a very small module declaring exactly what information you want -- pattern-matching by node, code module, or specific event type -- and whatever you want to do with that information -- log to a file, interact with your monitoring dashboard of choice, or arbitrary other activity. You can then attach that event listener to any node in your cluster and all matching events, no matter where they occur, will be forwarded to the listener so that you can take action.</p><p>Riak comes with a simple catch-all event listener that hears every single event in the cluster and logs them out to a named file. That can be useful, but more importantly it can serve as an example of the simplicity of the event interface.</p><br/></div><divid="right"></div><divid="footer"></div></div><script type="text/javascript">vargaJsHost=(("https:"==document.location.protocol)?"https://ssl.":"http://www.");document.write(unescape("%3Cscript src='"+gaJsHost+"google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));</script><script type="text/javascript">try{varpageTracker=_gat._getTracker("UA-10051263-1");pageTracker._trackPageview();}catch(err){}</script></body></html>