Difference between revisions of "Mesh/Monitoring"

Mesh/Monitoring (view source)

1,377 bytes added , 09:12, 25 July 2014

188

edits

@@ Line 17: / Line 17: @@
 == Sensu ==
-[[Sensu Page]]
+See our notes about the Sensu install: [[Mesh/Sensu_Page | Sensu Page]]
+=== About Sensu - From Sensu site ===
+Sensu is often described as the "monitoring router". Essentially, Sensu takes the results of "check" scripts run across many systems, and if certain conditions are met; passes their information to one or more "handlers". Checks are used, for example, to determine if a service like Apache is up or down. Checks can also be used to collect data, such as MySQL query statistics or Rails application metrics. Handlers take actions, using result information, such as sending an email, messaging a chat room, or adding a data point to a graph. There are several types of handlers, but the most common and most powerful is "pipe", a script that receives data via standard input. Check and handler scripts can be written in any language, and the community repository continues to grow!
+Fun Sensu facts:
+* Written in Ruby, using EventMachine.
+* Has great test coverage with continuous integration via Travis CI.
+* Can use existing Nagios plugins.
+* Configuration is all in JSON.
+* Has a message-oriented architecture, using RabbitMQ and JSON payloads.
+* Packages are "omnibus", for consistency, isolation, and low-friction deployment.
+* Sensu is designed for modern infrastructures and to be driven by configuration management tools, designed for the "cloud".
 == Icinga ==