Mesh/Sensu Page - Revision history

Chrisjx: /* Basics */

2014-09-19T17:19:02Z

Basics

← Older revision		Revision as of 10:19, 19 September 2014
Line 15:		Line 15:
	Installed on small frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.		Installed on small frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.
	* Debian		* Debian
			* monitor.local - (not accessible by this host name, perhaps dns is not correctly defined)
	* 192.168.42.65		* 192.168.42.65
	* ~~monitor~~.~~local~~ - ~~(not accessible, perhaps dns is not correctly defined)~~		** This box has been inconsistent re: dhcp addressing...
			** on 09.18.2014 - 192.168.50.15
	* user sudoroom:sudomesh		* user sudoroom:sudomesh
	* The sensu web page can be accessed internally at:		* The sensu web page can be accessed internally at:

Chrisjx: /* Things to do */

2014-08-01T17:09:00Z

Things to do

← Older revision		Revision as of 10:09, 1 August 2014
Line 40:		Line 40:
	## install Redis</s>		## install Redis</s>
	# config monitoring for internal PCs and/or other instances - see issues, below		# config monitoring for internal PCs and/or other instances - see issues, below
			# look at defining Handler Sets
	# configure a set of checks to perform		# configure a set of checks to perform
	## set up monitoring for switches - maybe?		## set up monitoring for switches - maybe?

Chrisjx: /* Things to do */

2014-08-01T16:54:47Z

Things to do

← Older revision		Revision as of 09:54, 1 August 2014
Line 43:		Line 43:
	## set up monitoring for switches - maybe?		## set up monitoring for switches - maybe?
	## install mini-snmpd (http://wiki.openwrt.org/doc/howto/snmp.server) on mesh nodes and configure a server side check to access nodes via snmp directly. Should be no other node/client side requirement.		## install mini-snmpd (http://wiki.openwrt.org/doc/howto/snmp.server) on mesh nodes and configure a server side check to access nodes via snmp directly. Should be no other node/client side requirement.
			# install [https://beingasysadmin.wordpress.com/2014/05/20/uchiwa-awesome-dashboard-for-sensu/ Uchiwa dashboard]
	# install sensu advanced admin page (https://github.com/sensu/sensu-admin)		# install sensu advanced admin page (https://github.com/sensu/sensu-admin)
	# install/build handlers for email, sms notifications		# install/build handlers for email, sms notifications

Chrisjx: /* Sensu Config Files */

2014-08-01T08:12:40Z

Sensu Config Files

← Older revision		Revision as of 01:12, 1 August 2014
Line 52:		Line 52:
	/etc/sensu/conf.d/		/etc/sensu/conf.d/

	api.json		=== api.json ===
	<pre>		<pre>
	{		{
Line 65:		Line 65:
	</pre>		</pre>

	dashboard.json		=== dashboard.json ===
	<pre>		<pre>
	{		{
Line 77:		Line 77:
	</pre>		</pre>

	rabbitmq.json		=== rabbitmq.json ===
	<pre>		<pre>
	{		{
Line 95:		Line 95:
	</pre>		</pre>

	client.json		=== client.json ===
	<pre>		<pre>
	{		{
Line 106:		Line 106:
	</pre>		</pre>

	server.json		=== server.json ===
	<pre>		<pre>
	oops...		oops...
	</pre>		</pre>

	check_cron.json		=== check_cron.json ===
	<pre>		<pre>
	{		{

Chrisjx: /* Sensu Config Files */

2014-08-01T08:11:35Z

Sensu Config Files

← Older revision		Revision as of 01:11, 1 August 2014
Line 124:		Line 124:
	}		}
	</pre>		</pre>

			== Tricks, Things to know ==
			* EMBEDDED_RUBY=true in /etc/default/sensu - this makes ruby available for the omnibus install of sensu. Always do this on fresh installs of sensu omnibus.

	== Issues ==		== Issues ==

Chrisjx: /* Basics */

2014-08-01T08:08:30Z

Basics

@@ Line 23: / Line 23: @@
 ** pw: secret
 * github repo: not yet. soon.
 == Things to do ==

Chrisjx: /* Basics */

2014-08-01T06:44:47Z

Basics

← Older revision		Revision as of 23:44, 31 July 2014
Line 18:		Line 18:
	* monitor.local - (not accessible, perhaps dns is not correctly defined)		* monitor.local - (not accessible, perhaps dns is not correctly defined)
	* user sudoroom:sudomesh		* user sudoroom:sudomesh
	* The sensu web page can be accessed internally at: http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)		* The sensu web page can be accessed internally at:
			** http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)
			** user: admin
			** pw: secret
	* github repo: not yet. soon.		* github repo: not yet. soon.

Chrisjx at 18:40, 25 July 2014

2014-07-25T18:40:06Z

← Older revision		Revision as of 11:40, 25 July 2014
Line 1:		Line 1:
	See Also: [[Mesh/Monitoring#Sensu \| Monitoring]]		See Also: [[Mesh/Monitoring#Sensu \| Monitoring]]

	notes about the install and config of a sudomesh monitoring server...		notes about the install and config of a sudomesh monitoring server - ChrisJ project, chris@freeranger.com

	Read all about Sensu here: http://sensuapp.org/docs/0.12/guide		Read all about Sensu here: http://sensuapp.org/docs/0.12/guide

			The main reason for doing this is to be able to monitor the mesh nodes for performance, up/down status, etc. The concept is to be able to use the light-weight mini-snmpd daemon on the mesh nodes and use sensu to perform checks and gather performance statistics. The statistics will be used to track performance for ongoing improvements in mesh node software.

			As a start, we will track some internal machines, get comfortable with that, then move on to the nodes.

	[[Category:Monitoring]]		[[Category:Monitoring]]
Line 15:		Line 19:
	* user sudoroom:sudomesh		* user sudoroom:sudomesh
	* The sensu web page can be accessed internally at: http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)		* The sensu web page can be accessed internally at: http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)
			* github repo: not yet. soon.

	== Things to do ==		== Things to do ==
Line 23:		Line 28:
	# config monitoring for internal PCs and/or other instances - see issues, below		# config monitoring for internal PCs and/or other instances - see issues, below
	# configure a set of checks to perform		# configure a set of checks to perform
	## set up monitoring for switches?		## set up monitoring for switches - maybe?
	## install mini-snmpd (http://wiki.openwrt.org/doc/howto/snmp.server) on mesh nodes and configure a server side check to access nodes via snmp directly. Should be no other node/client side requirement.		## install mini-snmpd (http://wiki.openwrt.org/doc/howto/snmp.server) on mesh nodes and configure a server side check to access nodes via snmp directly. Should be no other node/client side requirement.
	# install sensu advanced admin page (https://github.com/sensu/sensu-admin)		# install sensu advanced admin page (https://github.com/sensu/sensu-admin)

Chrisjx: /* Things to do */

2014-07-25T18:29:10Z

Things to do

← Older revision		Revision as of 11:29, 25 July 2014
Line 17:		Line 17:

	== Things to do ==		== Things to do ==
	# <s>install sensu server</s> Â¤		# <s>install sensu server
			## set up SSL certificates
			## install/config RabbitMQ
			## install Redis</s>
	# config monitoring for internal PCs and/or other instances - see issues, below		# config monitoring for internal PCs and/or other instances - see issues, below
	# configure a set of checks to perform		# configure a set of checks to perform
Line 26:		Line 29:
	# hook up performance data to charts		# hook up performance data to charts
	# configure RabbitMQ admin web		# configure RabbitMQ admin web

	~~Â¤ = done...~~

	== Sensu Config Files ==		== Sensu Config Files ==

Chrisjx at 18:22, 25 July 2014

2014-07-25T18:22:53Z

← Older revision		Revision as of 11:22, 25 July 2014
Line 3:		Line 3:
	notes about the install and config of a sudomesh monitoring server...		notes about the install and config of a sudomesh monitoring server...

	Read all about it here: http://sensuapp.org/docs/0.12/guide		Read all about Sensu here: http://sensuapp.org/docs/0.12/guide

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