SystemAdministration/Icinga: Difference between revisions
| Line 42: | Line 42: | ||
'''server definitions''' | '''server definitions''' | ||
Each server has a file in /etc/icinga/objects/servers/ which looks something like: | |||
<pre> | |||
define host{ | |||
use generic-host ; Name of host template to use | |||
host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS). | |||
alias carbon ; A shortname | |||
address carbon.li694-22 ; The server's address. | |||
} | |||
</pre> | |||
Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22: | |||
<code>/etc/icinga/objects/servers/ $ '''cp carbon.cfg example.cfg'''</code> | |||
Once that's done, you can either edit the file manually with the editor of your choice or use sed: | |||
<code>/etc/icinga/objects/servers/ $ '''sed -i 's/carbon/example/g' example.cfg'''</code> | |||
Revision as of 21:01, 13 April 2014
Sentinel: Icinga / Server & Services Monitoring
introduction
note: base directory will be /etc/icinga/ unless stated otherwise
note2: These examples will use 'carbon.li694-22'
Access
Our Icinga installation is named 'Sentinel' which means "a soldier or guard whose job is to stand and keep watch", you can find Sentinel here and login with your Keberos username and password.
Kerberized SSH connections
We use AutoSSH to allow Icinga to connect to other nodes to execute commands and get services information back.
Internally, we can use Kerberos to jump from one host to another our Icinga installation requires HTTP Kerberos auth (via https) but we've also set up AutoSSH which allows our Icinga instance to connect to other nodes passwordless & ssh key-less to fetch information.
more information, show how we've setup the connections, etc
icinga.cfg
Information
objects
general information about objects
objects/templates
template information
objects/contacts
contacts & notifications
objects/groups
services groups
objects/servers
server definitions
Each server has a file in /etc/icinga/objects/servers/ which looks something like:
define host{
use generic-host ; Name of host template to use
host_name carbon.li694-22 ; The server hostname (ensure it's in our DNS).
alias carbon ; A shortname
address carbon.li694-22 ; The server's address.
}
Creating a new one (for instance, 'example.li694-22') should be straight forward, you simply copy carbon.li694-22 to example.li64-22:
/etc/icinga/objects/servers/ $ cp carbon.cfg example.cfg
Once that's done, you can either edit the file manually with the editor of your choice or use sed:
/etc/icinga/objects/servers/ $ sed -i 's/carbon/example/g' example.cfg