Icinga 2 is an open source tracking system which checks the availability of your network resources, notifies users of interruptions and produces efficiency data for reporting. Scalable and extensible, Icinga 2 can keep an eye on large, complex environments throughout several places.
Hosts and Services
Icinga 2 can be used to monitor the schedule of hosts and services. Services and hosts can be virtually anything which can be signed in some way:
Network services (HTTP, SMTP, SNMP, SSH, etc) :
-Routers or switches
-Temperature level sensing units
-Other regional or network-accessible services
Setting up Icinga 2
This chapter provides an introduction into finest practices for your Icinga 2 configuration. The setup files which are immediately created when installing the Icinga 2 plans are a good way to start with Icinga 2. The Language Reference chapter describes details on worth types (string, number, dictionaries, and so on) and the basic setup syntax.
Setup Best Practice
If you are prepared to set up additional hosts, services, alerts, reliances, and so on, you ought to think of the requirements first then choose for a possible strategy, click here.
There are many methods of producing Icinga 2 configuration objects:
Manually with your favored editor, for instance vi( m), nano, notepad, and so on
– A configuration tool for Icinga 2 e.g. the Icinga Director
Created by a configuration management tool such as Puppet, Chef, Ansible, and so on
– A custom-made exporter script from your CMDB or stock tool
– Then you must try to find the things specific configuration setting host_name and so on appropriately. You choose the “finest” design for setup files and directory sites. Ensure that the icinga2.conf configuration file includes them
In either method of choosing the right method you should additionally inspect the following:
– Exist any specific attributes describing the host/service you could set as vars custom qualities? You can later on use them for using assign/ignore rules, or export them into external interfaces
– Put hosts into hostgroups, services into servicegroups and utilize these characteristics for your use rules
– Usage templates to keep generic attributes for your things and apply rules making your configuration more legible. Information can be found in the using templates chapter
– Apply guidelines may overlap. Keep a main place (for services.conf, example or notifications.conf) storing the setup instead of specifying use guidelines deep in your setup tree
– Every plugin utilized as check, notification or occasion command needs a Command meaning. Additional information can be looked up in the check commands chapter
If you are preparing to use a distributed monitoring setup with customer, satellite and master installations take the setup location into account too. Everything set up on the master, synced to all other nodes? Or any particular local setup?