Difference between revisions of "Mesh/Sensu Page"

From Sudo Room
Jump to navigation Jump to search
Line 14: Line 14:
* 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 at: http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)


== Things to do ==
== Things to do ==

Revision as of 10:45, 25 July 2014

See Also: Monitoring

notes about the install and config of a sudomesh monitoring server...

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

Basics

Installed on small frame Dell PC, service tag: 2FDSGC1, green tape with info on the front.

  • Debian
  • 192.168.42.65
  • monitor.local - (not accessible, perhaps dns is not correctly defined)
  • user sudoroom:sudomesh
  • The sensu web page can be accessed at: http://192.168.42.65:8080/# (as of 2014.07.25 no services defined)

Things to do

  1. config monitoring for internal PCs and/or other instances
  2. set up monitoring for switches?
  3. 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.
  4. install/build handlers for email, sms notifications
  5. hook up performance data to charts
  6. configure RabbitMQ admin web
  7. install sensu admin page

Sensu Config Files

Look for sensu config files in:

/etc/sensu/conf.d/

api.json

{
  "api": {
    "host": "localhost",
    "port": 4567,
    "user": "admin",
    "password": "secret"
  }
}

dashboard.json

{
  "dashboard": {
    "port": 8080,
    "user": "admin",
    "password": "secret"
  }
}

rabbitmq.json

{
  "rabbitmq": {
    "ssl": {
      "cert_chain_file": "/etc/sensu/ssl/cert.pem",
      "private_key_file": "/etc/sensu/ssl/key.pem"
    },
    "host": "monitor",
    "port": 5671,
    "vhost": "/sensu",
    "user": "sensu",
    "password": "secret"
  }
}

client.json

{
  "client": {
    "name": "monitor",
    "address": "192.168.42.65",
    "subscriptions": [ "all","webservers" ]
  }
}

server.json

oops...

check_cron.json

{
  "checks": {
    "cron_check": {
      "handlers": ["default"],
      "command": "/etc/sensu/plugins/check-procs.rb -p crond -C 1 ",
      "interval": 60,
      "subscribers": [ "webservers" ]
    }
  }
}

Issues

Installing Sensu on dev exit node

Trying to get the sensu client install on the dev exit node, exit1.sudomesh.org (192.157.221.200). Could not successfully run these commands as sudo:

notes from this page: http://sensuapp.org/docs/0.12/packages

wget -q http://repos.sensuapp.org/apt/pubkey.gpg -O- | sudo apt-key add - 
echo "deb     http://repos.sensuapp.org/apt sensu main" > /etc/apt/sources.list.d/sensu.list
apt-get update
apt-get install sensu