Difference between revisions of "Mesh/Monitoring"

Jump to navigation Jump to search

Mesh/Monitoring (view source)

Revision as of 23:36, 4 December 2014

1,125 bytes removed ,  23:36, 4 December 2014
no edit summary
Line 3: Line 3:
[[Category:Monitoring]]
[[Category:Monitoring]]
[[Category:Technical]]
[[Category:Technical]]
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.


== Monitoring Server ==
== Monitoring Server ==
Line 23: Line 19:


== List of hosts ==
== List of hosts ==
Running nmap (09.18.2014) to see if I can find a list of hosts which we might want to be monitored...
Run nmap (09.18.2014) to see a list of hosts which we might want to monitor...


Most of these are probably laptops connected to the internet.
Most of these are probably laptops connected to the internet.
<pre>
nmap -sn 192.168.50.0/24
cjefferies$ nmap -sn 192.168.50.0/24
Starting Nmap 6.46 ( http://nmap.org ) at 2014-09-18 22:04 PDT
Nmap scan report for 192.168.50.6
Host is up (0.099s latency).
Nmap scan report for 192.168.50.15
Host is up (0.062s latency).
Nmap scan report for 192.168.50.20
Host is up (0.063s latency).
Nmap scan report for 192.168.50.39
Host is up (0.13s latency).
Nmap scan report for 192.168.50.49
Host is up (0.087s latency).
Nmap scan report for 192.168.50.60
Host is up (0.011s latency).
Nmap scan report for 192.168.50.61
Host is up (0.022s latency).
Nmap scan report for 192.168.50.86
Host is up (0.034s latency).
Nmap scan report for 192.168.50.87
Host is up (0.047s latency).
Nmap scan report for 192.168.50.88
Host is up (0.047s latency).
Nmap scan report for 192.168.50.100
Host is up (0.00025s latency).
Nmap scan report for 192.168.50.101
Host is up (0.096s latency).
Nmap done: 256 IP addresses (12 hosts up) scanned in 23.23 seconds
</pre>


* 192.168.50.15 - monitoring server
* 192.168.50.15 - monitoring server
Line 76: Line 44:
** pw: secret
** pw: secret


=== 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 ==
Line 100: Line 55:
* the services that are to be monitored.
* the services that are to be monitored.


=== OpenWRT Package: nrpe ===
== Icinga 2 ==
Icinga 2 is a rewrite of Icinga with a cleaner implementation and configuration structure.  It will be able to run SNMP calls to nodes which run mini-snmpd and be able to send performance data to charting apps like graphite.
 
 
== OpenWRT Package: nrpe ==
<pre>
<pre>
Package: nrpe
Package: nrpe
Line 122: Line 81:
</pre>
</pre>


== Icinga 2 ==
See Install notes at: [[Icinga 2]]
Icinga 2 is a rewrite of Icinga with a cleaner implementation and configuration structure. It will be able to run SNMP calls to nodes which run mini-snmpd and be able to send performance data to charting apps like graphite.
 
== 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".


See Install notes at: [[Icinga 2]]


== Charting ==
== Charting ==
Retrieved from "https://sudoroom.org/wiki/Special:MobileDiff/9042"

Navigation menu