As we are working with about 50 people on the configuration, we dont want to mix up local configfiles with director configuration. Read Also – How to Install and Configure Icinga 2 / Icinga Web 2 on CentOS 7 and RHEL 7 The default port that icinga2 uses for monitoring is 5665 & it should be opened up in firewall to maintain a connection between master & host (called parent & child for icinga2), Use below command to open 5665 port in … Then you can put the dummy host in the Parent field of the dependency. Did I do it wrong? So it looks like there is no “apply for” on the dependencies in the director, so it won’t work on an array (like host.vars.parents = [ “hostA”, “hostB” ]). Seems like we build a kind of loop with our dependencies and its known limitation to have a max of 256 (https://github.com/Icinga/icinga2/issues/5762 and https://github.com/Icinga/icinga2/issues/1719) . vars.parents = [ “switch-01” ] Type details about your service details. object Host “Zues” { OMD. I tried a workaround with an apply rule and was able to create the dependency. Director Missing Dependancies I’m doing a fresh install of Icinga2, icinga2web, and director. To create a new service template, click the 'Add' button. Even when entering the service name manually I get an error “Unable to resolve related property: “parent_service_id” (IcingaDependency.php:584)”. Host2 Healthcheck is CRIT. Now all works. check_command = “hostalive” icinga2 object list --type Dependency. Let’s create a linux template. Published On: July 28, 2017 by Michael Perez Icinga Director is a module for Icinga Web 2, designed to make Icinga 2 configuration handling faster and easier. 2020-11-06T12:21:13Z Julian Brost Update CMake At the moment, builds output lots of "New Boost version may have incorrect or missing dependencies and imported targets" warnings. Normally in etc/icinga2/conf.d/hosts.conf I would create the dependency and hosts like this: apply Dependency “Parent” for (parent in host.vars.parents) to Host { You can use just the Apache portion of the LAMP tutorial mentioned aboveto set these up. Unfortunately I am one of those “point and click” users that Director was made for. In this article we will create a little "dummy CMDB" with MySQL and automatically import and deploy host information. Before starting this tutorial, you should have completed the previous tutorial in this series, How To Install Icinga and Icinga Web on Ubuntu 16.04. Zuerst muss man sich das […] Wer dieser Anleitung gefolgt ist, der hat Icinga Web im DocumentRoot installiert. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration. In director I have been able to create the vars.parents field and fill in the correct values. Hi, there is an open issue: https://github.com/Icinga/icingaweb2-module-director/issues/1142. Variables. Be sure that the variable “parents” is always an array. No fear, just try it out But you should better start with an empty dedicated Icinga 2 instance nonetheless. apply Dependency “Parent” for (parent in host.vars.parents) to Host { Brilliant!!! I had the data type set to string instead of array. So far - so good. If you happen to have a CMDB, NDO database, PuppetDB/Foreman, etc. I try to add a service dependency. Changelog¶ next (will be 1.2.0)¶ Breaking Changes¶. Icinga 2 is a network monitoring system and parallel development branch to Icinga 1. Any ideas? A project by icinga in … } Hey everyone, I'm on debian 8.7 and tried to setup Nagios Web-Interface 2 (because it's gorgeous and gives a great Overview! Host2 Healtcheck is OK (because of automatic failover) import “generic-host” To avoid the dependency loop, I thought about a dummy Services, which will do the same check as the healtcheck, but with another name, so I could have this dummy as parent and not the real services. parent_host_name = parent This dependency is required for the visgence module. Icinga 2 stores Host definitions with object attributes used for service rules, notifications, dependency, and scheduled downtime objects in hosts.conf file which is located in /etc/icinga2/conf.d/ directory. Powered by Discourse, best viewed with JavaScript enabled. Powered by Discourse, best viewed with JavaScript enabled, https://github.com/Icinga/icingaweb2-module-director/issues/1142, https://github.com/Icinga/icinga2/issues/5762, https://github.com/Icinga/icinga2/issues/1719. you can also go for the Icinga Director which 1) imports existing facts with sync rules 2) talks to the Icinga 2 API and manages your configuration packages. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration. Icinga. We will cover some basic configuration, so you will be able to monitor network services and host resources via the web interface. It should work with $host.vars.parent1$ for example. In etc/icinga2 I created file visgence.conf. I would like to configure a Host-to-Host dependency on Icinga2, however, one of the Hosts has an HA configuration, so I need the to trigger it only when both HA devices are down. But I will only get suggestions for two services, but not the one I need (we have about 10 services on the host). This is a good community. To add a new host you have to create a template first. ==>> No notification (rule 1), Host1 Healthcheck is CRIT. Thanks to everyone else who responded as well. We are also waiting for the version where this is fixed. It is also worth noting that the outlined solution works both with and without Icinga Director. This is the Part 2 of the post we started in here. Because its a failover Host, I created two dependencies: But that escalated quickly … Wen adding a windows machine no problem when you add a service to monitor lots of errros. In that file I put the following: Die Einrichtung ist die eine, die Inbetriebnahme und Nutzung dann wieder eine andere Sache — … Thomas Gelf Web 2 Product owner Module prototyping machine Principal Consultant @netways So creating the separate conf file and adding it to the icinga2.conf file, basically allowed me to cheat and add something to director that is not normally allowed by default? You Rock!!! check_command = “hostalive” One has Parent Host: host.vars.mummy and the 2nd has host.vars.daddy as parent in the director config. So here is what I did. williamk (William K) June 12, 2019, 11:59pm ... What am I missing? In this tutorial, we will go over the installation of Icinga, an open source monitoring system, on Ubuntu 14.04. Please use the specific sub categories for Icinga 2, Icinga Web 2, Director, etc. So far - so good. I prefer to move MySQL databases to a dedicated hard drive with LVM. is missing. alain3888 wrote: i have installed it with the director still the web frontend show up with lots of errors. Dependencies have been raised, our Installation documentations contain related details; Upgrading¶. If Service1 on Host1 is OK, Service2 at Host2 should not be checked. I mentioned that Icinga Director can be used to link Icinga to pre-existing Configuration Management Database (CMDB) systems to simplify data import. } That command returned no results. Wie man dieses umsetzt werde ich an einem einfachen Beispiel, einer CSV-Datei hier beschreiben. import “[tmpl-host-generic]”, display_name = “Accesspoint ap-01” You can actually use host vars. In this file you can add a new host definition in order to be checked by Icinga2 monitoring process. I restarted icinga2 service and ran command icinga2 object list --type Dependency . Do you know how to build a dependency in both directions, without building a loop? But you can combine both - file based config and Director. Download the plugin and place it in your plugin directory. Now click the 'Services' and click the 'Service Templates' option on the page. Host1 Healthcheck is OK. In my last article I focussed on Icinga 2 and the new configuration utility Icinga Director. Note that you can’t actually manage icinga host within icinga director and you will only be able to add new hosts. So we assume you have at max 2 parents. Icinga Director 1. www.icinga.org Icinga Director IcingaCamp Berlin – 01/03/15 2. the way you showed as config files should work - I did it in the same way. We have a lot service checks which are applied dynamically through apply rules. vars.parents = [“Zues”] This should be easy with dependencies in the director. - Icinga/icingaweb2-module-director Searching the internet suggests that this is because the CMake version is too old to know about Boost 1.71.0. Following is an example for monitoring the SSH service. Willkommen also, Icinga Director! Make sure to install any missing dependencies. parent_host_name = parent All the other missing services are assigned with “servicesets”. ==> ALARM. Host preview in Director should look like this: object Host “ap-01” { This should be easy with dependencies in the director. However, am struggling how to create the dependency itself in director. Icinga Director has been designed to make Icinga 2 configuration handling easy. steps to Director as a policy for our Icinga2 instances we build - solved the multi-parent problem by defining a dummy “aggregate” host with IP 0.0.0.0, who then regularly fpings the list of parent hosts via a data field, listing hosts. Attached is what I have, but it does not work. I might miss something but with the leading and trailing $ it should work and allow a solution where you inherit the value from the host object. Icinga Web2: unmet dependencies and no way to install? address = “192.168.1.179” Klick auf Icinga Director → Activity Log → Deploy … pending changes wird dein erstes Deployment anstoßen und dir das Ergebnis darstellen. the dummy host is only “up” as long as at least one of the parents is reachable.) Icinga is an open-source computer system and network monitoring application. 23. So I would create 2 fields for the host. The Director aims to be your new favourite Icinga config deployment tool. Host2 Healtchcheck is CRIT (because only one instance can run at the same time) import “generic-host” Written from scratch, it builds on the success of Icinga 1 and deals with shortcomings inherited from Nagios as a fork. display_name = “Zues_1.1” introduced This release brings Schema migrations, which can be applied with a single click in the Frontend. Added this data field to your host template (template is in cluster zone. Is it because the director treats servicesets in another way so I can not add any services from servicesets? We will use two Ubuntu 16.04 servers with Apache installed for our examples. The only values it will take is an acutal host name. Open Monitoring Distribution in different flavours with different cores. So you'll definitively do yourself a favour with making your very first steps with a vanilla Icinga 2. Introduction. Bothers masters crashed with the following error: " Too many nested dependencies (>256) for checkable". So, in the best case you have a limited number of dependencies - which would make the stuff below easier. Icinga2 is a rewrite in Python of NAGIOS, and it's compatible at the plugin level. When moving the config from files to Director, IMHO the variable $host.vars.parents$ in “Parent Host” Die Einrichtung erfolgt im Browser unter http(s)://monitor.domain.tld/setup (oder /icingaweb2/setup). In this second part we will use Icinga2 to monitor this list of metrics and be preemptively notified when the values go over preset threshold. Bonus: You'll get a configuration UI for Icinga 2 as well. ), but sadly I have unmet dependencies and I cannot find a way to install them! object Host “3850_12X_ToyRoom” { I think that is a limitation of director and dependencies. The "upgrade_dependencies.sql" file under mysql-migrations may help get those added if … Anything related to Icinga. Command address = “192.168.1.1” OMDLabs, CheckMK Raw Edition (CRE) or plain Nagios/Naemon with additional addons. I can now proceed with project. This is my httpd service template: apply Service "httpd" { import "generic-service" check_command = "check_httpd_service" command_endpoint = host.vars.client_endpoint assign where host.vars.client_endpoint && host.vars.myserver } Now icinga director created for you all the available commands to let you use service checks and it’s ready to adding new hosts. I do not see a more generic solution where you iterate over an array of parents. address = “172.16.1.1” Even its not a real solution there, I can track the status. After entering the parent host as related object, I want to enter the service name. Icinga2 Director - Services Dependencies! assign where host.address && host.vars.parents If you are using Icinga Director go ahead and define the necessary Data Fields. The Director aims to be your new favourite Icinga config deployment tool. I am not sure if I get the question correct but I’ll try to help. }. display_name = “3850_12X_ToyRoom_1.179” Parent1 & Parent2 (or primary and secondary or mummy and daddy for example) and just create 2 dependencies. ==>> No notification (rule 2), Host1 Healthcheck is CRIT. When I’m adding director it keeps telling me that the IPL, Incubator, and React Module are all installed and enabled but when attempting to configure director for the first time it keeps telling me those modules are missing. }. Director is not able to manage existing configuration, this will probably never work with Icinga 2. I try to add a service dependency. Icinga Web 2 is the successor of Icinga web which is lightweight, fast and flexible to embed into other projects that supports multiple authentication methods like Active Directory, LDAP or database and multiple monitoring back ends. You will also need some servers to monitor. }, Then this rule is applied to every host with set address and parent variable - regardless if the host is defined in file or via Director. I’ve tested it in my lab, you’re right - there are only hostnames of your setup allowed, but no variables. Hi Manfred, the Parent Host field will not take the value, “host.vars.parents”. Die Schritte zur Einrichtung ergeben sich aus der bisherigen Anleitung. assign where host.address && host.vars.parents That is a nifty trick. It tries to target two main audiences: Users with the desire to completely automate their datacenter; Sysops willing to grant their point & click users a lot of flexibility; What makes Icinga Director so special is the fact that it tries to target both of them at once.