Difference between revisions of "Mesh/Monitoring"

From Sudo Room
Jump to navigation Jump to search
Line 17: Line 17:


== Sensu ==
== 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 ==
== Icinga ==

Revision as of 10:12, 25 July 2014

See Also: Technical Documentation

Max has been working on monitoring statistics from with the wifi router using collectd and RRD.

Max discussed with ChrisJ about system wide monitoring... recommends Icinga.

RRD

collectd

Sensu

See our notes about the Sensu install: 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

Interesting article: [Setting up Icinga on a Debian Server to Remotely Monitor an OpenWrt Router]

Icinga is a Nagios fork which, as of Fall 2013, has more development involvement. Icinga is the central system that pings other systems like openWRT. Icinga gathers the data and can track and send notifications when values drift beyond normal tolerances. On the remote hosts it is required to install nrpe and a basic set of nrpe plugins. The article referenced above shows how it is possible to install nrpe on openwrt through the openwrt web interface. After that one can ssh into the router and configure it.

Once the router is configured it is necessary to configure the central Icinga server with:

  • the IP address of each node it will track
  • the host groups
  • the services that are to be monitored.

OpenWRT Package: nrpe

Package: nrpe
Version: 2.12-4
Depends: libc, librt, libpthread, libopenssl, libwrap
Source: feeds/packages/admin/nrpe
SourceFile: nrpe-2.12.tar.gz
SourceURL: @SF/nagios
Section: admin
Architecture: ib42x0
Installed-Size: 19018
Filename: nrpe_2.12-4_ib42x0.ipk
Size: 19801
MD5Sum: f36019344c747a1e88f5aab50776bd4e
Description:  The NRPE addon is designed to allow you to execute Nagios plugins on
 remote Linux/Unix machines.  The main reason for doing this is to allow
 Nagios to monitor "local" resources (like CPU load, memory usage, etc.)
 on remote machines.  Since these public resources are not usually
 exposed to external machines, an agent like NRPE must be installed on
 the remote Linux/Unix machines.

Charting

Graphite

Graphene

Cricket