We are a GIS platform-as-a-service company, connecting people, their location, their need at a particular time. We believe in developing rock solid, highly performing, scalable and stable platform for our customers.

Menu

Monthly Archives: October 2016

Sensu Setup

After a lot of research, we have realized that a good alternative to Nagios is Sensu. We did evaluate shinken, but the documentation sucks big time. Hence Sensu is a good alternative. Started off by watching some training videos on https://www.udemy.com/sensu-introduction

Once the training is thru the concepts are clear. Without the introduction the remainder of the session cannot be understood.

In my setup, I have 4 servers.

Proxy – This is my http proxy

This server will run the sensu-server, sensu-api, redis, dashboard and rabbitmq-server.

This server will test reachability to the RDS, Elastic Cache and the other servers in my setup (#2, #3 and #4)

Web Administration – This is my server that hosts the administration for my customer.

This server will serve as a sensu-client.

Web Services – This is my server that hosts the webservices for my Web Administration and Mobile applications.

This too will serve as the sensu-client.

RDS and Elastic Cache Services – This is the standard AWS services.

The Proxy server will test the reachability of RDS and Elastic Cache from time to time.

I’ll one more external server to check the reachability of the proxy from the network. Perhaps another AWS EC2 on a different setup.

Note, we also found that sensu-client takes up about 100Mb memory
to operate. And sensu-server and sensu-api takes up about 300Mb
to operate. So if you have a aws micro with apache, mysql, redis,
running Sensu full stack is a bad idea.

Now, to install sensu-client on the servers, run the following commands