Mesh/Monitoring - Revision history

Maxb: /* The Basics */

2015-12-30T20:36:09Z

The Basics

← Older revision		Revision as of 13:36, 30 December 2015
Line 3:		Line 3:
	[[Category:Monitoring]]		[[Category:Monitoring]]
	[[Category:Technical]]		[[Category:Technical]]

			This is all currently out of date. The currently implemented monitor server is running on VPS, which is tunneled into the network.
			It's running [https://monitor.sudomesh.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=45 Cacti] and [https://monitor.sudomesh.org/smokeping/smokeping.cgi?target=Mesh Smokeping] as well as gathering logs.

			When I have the time, I'll update the details here, but I've documented the setup as provisioning code here: https://github.com/max-b/mesh-playbooks - [[User:Maxb]]


	== The Basics ==		== The Basics ==

Chrisjx at 06:51, 20 February 2015

2015-02-20T06:51:32Z

← Older revision		Revision as of 23:51, 19 February 2015
Line 1:		Line 1:
	See Also: [[Mesh#Technical_Documentation \| Technical Documentation]], [[Mesh#Bandwidth Quotas \| Bandwidth Quotas]]		See Also: [[Mesh#Technical_Documentation \| Technical Documentation]], [[Mesh/Bandwidth Quotas \| Bandwidth Quotas]]

	[[Category:Monitoring]]		[[Category:Monitoring]]

Chrisjx at 06:49, 20 February 2015

2015-02-20T06:49:55Z

← Older revision		Revision as of 23:49, 19 February 2015
Line 1:		Line 1:
	See Also: [[Mesh#Technical_Documentation \| Technical Documentation]], [Mesh#[Bandwidth Quotas \| Bandwidth Quotas]]		See Also: [[Mesh#Technical_Documentation \| Technical Documentation]], [[Mesh#Bandwidth Quotas \| Bandwidth Quotas]]

	[[Category:Monitoring]]		[[Category:Monitoring]]

Chrisjx at 06:49, 20 February 2015

2015-02-20T06:49:15Z

← Older revision		Revision as of 23:49, 19 February 2015
Line 1:		Line 1:
	See Also: [[Mesh#Technical_Documentation \| Technical Documentation]]		See Also: [[Mesh#Technical_Documentation \| Technical Documentation]], [Mesh#[Bandwidth Quotas \| Bandwidth Quotas]]

	[[Category:Monitoring]]		[[Category:Monitoring]]

Chrisjx: /* Use It */

2014-12-05T08:18:00Z

Use It

← Older revision		Revision as of 01:18, 5 December 2014
Line 20:		Line 20:
	* login: sudoroom:sudomesh		* login: sudoroom:sudomesh

	Icinga:		Icinga web UI:
	* http://192.168.50.15/icinga2-classicui ~~- icinga web ui~~		* http://192.168.50.15/icinga2-classicui (login: icingaadmin:mojave)

	Charting:		Charting:
	* http://192.168.50.15/ ~~- graphite web ui~~		* Graphite - http://192.168.50.15/
	* http://192.168.50.15/grafana ~~- better dashboard charts~~		* Grafana - http://192.168.50.15/grafana
	* http://192.168.50.15/grafana/#/dashboard/db/sudomesh -works best in firefox~~...~~		* Mesh Charts - http://192.168.50.15/grafana/#/dashboard/db/sudomesh (works best in firefox)

	~~github~~ repo:		Github repo:
	* https://github.com/TinajaLabs/sudomesh_icinga		* https://github.com/TinajaLabs/sudomesh_icinga

Chrisjx: /* Use It */

2014-12-05T08:14:09Z

Use It

← Older revision		Revision as of 01:14, 5 December 2014
Line 22:		Line 22:
	Icinga:		Icinga:
	* http://192.168.50.15/icinga2-classicui - icinga web ui		* http://192.168.50.15/icinga2-classicui - icinga web ui

			Charting:
	* http://192.168.50.15/ - graphite web ui		* http://192.168.50.15/ - graphite web ui
			* http://192.168.50.15/grafana - better dashboard charts
			* http://192.168.50.15/grafana/#/dashboard/db/sudomesh -works best in firefox...

	github repo:		github repo:

Chrisjx at 08:10, 5 December 2014

2014-12-05T08:10:20Z

← Older revision		Revision as of 01:10, 5 December 2014
Line 35:		Line 35:
	* 192.168.50.15 - monitoring server		* 192.168.50.15 - monitoring server
	*		*

	~~== RRD ==~~
	* http://oss.oetiker.ch/rrdtool/
	* also look at whisper, a light weight rrd - http://graphite.wikidot.com/whisper
	*

	~~== collectd ==~~
	* http://collectd.org/

	== Icinga ==		== Icinga ==
	Interesting article: [[http://www.smallbusinesstech.net/more-complicated-instructions/nagios/setting-up-nagios-on-a-debian-server-to-remotely-monitor-an-openwrt-router Setting up Icinga on a Debian Server to Remotely Monitor an OpenWrt Router]]		Interesting article: [http://www.smallbusinesstech.net/more-complicated-instructions/nagios/setting-up-nagios-on-a-debian-server-to-remotely-monitor-an-openwrt-router 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.		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.
Line 56:		Line 48:
	== Icinga 2 ==		== 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.		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.

			See Install notes at: [[Icinga 2]]


Line 90:		Line 84:
	</pre>		</pre>

	~~See Install notes~~ at: ~~[[Icinga 2]]~~		== Alternative tools ==

			=== RRD ===
			* http://oss.oetiker.ch/rrdtool/
			* also look at whisper, a light weight rrd - http://graphite.wikidot.com/whisper
			*

			=== collectd ===
			* http://collectd.org/


	== Sensu - Deprecated ==		=== Sensu - Deprecated ===
	See our notes about the Sensu install: [[Mesh/Sensu_Page \| Sensu Page]]		See our notes about the Sensu install: [[Mesh/Sensu_Page \| Sensu Page]]

	Requires a client application service and not useful for our needs for monitoring mesh nodes...		'''Requires a client application service and not useful for our needs for monitoring mesh nodes...'''

	* The sensu web page can be accessed internally at:		* The sensu web page can be accessed internally at:
	** http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)		** http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)
Line 101:		Line 105:
	** pw: secret		** pw: secret

	=== About Sensu - From Sensu site ===		==== 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!		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!

Chrisjx: /* OpenWRT Package: nrpe */

2014-12-05T08:04:15Z

OpenWRT Package: nrpe

← Older revision		Revision as of 01:04, 5 December 2014
Line 58:		Line 58:


	== OpenWRT Package: nrpe ==		== Access to remote hosts ==
			Icinga can use various methods to monitor remote hosts, NRPE, SNMP, etc.

			=== IMCP ===
			The ping service; for determining if the host is reachable

			=== SNMP ===
			We will probably start off with simple SNMP monitoring. It return very basic info but it does not require too much setup on the remote hosts.

			=== OpenWRT Package: nrpe ===
			NRPE requires a daemon running on the remote host and a number of mostly bash scripts for specialized info. Bash scripts can be developed to read disk stats, memory usage, etc. There are about 30 scripts which come with NRPE.
	<pre>		<pre>
	Package: nrpe		Package: nrpe

Chrisjx: /* Charting */

2014-12-05T07:56:36Z

Charting

← Older revision		Revision as of 00:56, 5 December 2014
Line 122:		Line 122:

	==== Sample live charts rendered from Graphite ====		==== Sample live charts rendered from Graphite ====

	~~Round trip average ping over the last 2 hours:<br>~~
	http://192.168.50.15/render?width=400&from=-2hours&until=now&height=250&target=icinga.localhost.ping4.rta&_uniq=0.43809576937928796&title=icinga.localhost.ping4.rta&.png		http://192.168.50.15/render?width=400&from=-2hours&until=now&height=250&target=icinga.localhost.ping4.rta&_uniq=0.43809576937928796&title=icinga.localhost.ping4.rta&.png
			<br>Round trip average ping over the last 2 hours:

	=== Grafana ===		=== Grafana ===
Line 168:		Line 167:
	* http://cricket.sourceforge.net/		* http://cricket.sourceforge.net/
	*		*




	== motd ==		== motd ==

Chrisjx: /* Monitoring Server */

2014-12-05T07:53:07Z

Monitoring Server

← Older revision		Revision as of 00:53, 5 December 2014
Line 4:		Line 4:
	[[Category:Technical]]		[[Category:Technical]]

	== ~~Monitoring Server~~ ==		== The Basics ==
	See Also: [[Mesh/Icinga 2]]		See Also: [[Mesh/Icinga 2]]
	~~Installed on small~~ frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.
			=== The Hardware ===
			Small frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.

			=== The Software ===
	* OS: Linux monitor 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux		* OS: Linux monitor 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
	* Access:
	** monitor or monitor.local - (as of 10.30.2014, not accessible by this host name, perhaps dns is not correctly defined)
	** on 09.18.2014 - 192.168.50.15
	** login sudoroom:sudomesh

			=== Use It ===

			ssh to:
			* monitor or monitor.local - (as of 10.30.2014, not accessible by this host name, perhaps dns is not correctly defined)
			* 192.168.50.15
			* login: sudoroom:sudomesh

			Icinga:
	* http://192.168.50.15/icinga2-classicui - icinga web ui		* http://192.168.50.15/icinga2-classicui - icinga web ui
	* http://192.168.50.15/ - graphite web ui		* http://192.168.50.15/ - graphite web ui

	* github repo: https://github.com/TinajaLabs/sudomesh_icinga		github repo:
			* https://github.com/TinajaLabs/sudomesh_icinga

	== List of hosts ==		== List of hosts ==