On Monday 19 December 2016 at 21:00:34, Volker Janzen wrote: > I want to monitor > 10 virtual machines. I setup a Icinga master with > Icingaweb2. > > My VMs currently run an NRPE server.
Better to remove NRPE and install Icinga on the VMs, then use the master - client setup described in section 6 of the documentaton: https://docs.icinga.com/icinga2/latest/doc/module/icinga2/chapter/distributed- monitoring > The VMs should get an Icinga agent instead when I migrate them from Nagios > to Icinga. Yes, except there is no Icinga "agent" - it's just Icinga. > I want the agents to be configured locally. Why? You _can_ do that, yes, but I think centrally-configured on the master, using top-down command endpoint (see above documentation), is best. Local configuration is much harder to manage and to keep consistent. > The master will not start ping checks, until I add address/adress6 entries > to the Host definition. Correct. If you don't specify the address of the host, the master has no idea what to ping... > The host definition for the connected agents has been auto-generated by what? > in the repository.d/hosts folder. I can add the address / address6 entries > there and after the config has been reloaded the master will ping the agent > hosts (seen by higher latency). Is it best practice to change the > autogenerated files or should I do this different? How are these files being auto-generated? What tool are you using for the auto-generation? > Icinga complains about syntax errors, when I add custom vars to the > autogenerated host objects, e.g. vars.os = Linux. That should be: vars.os = "Linux" Antony. -- There's a good theatrical performance about puns on in the West End. It's a play on words. Please reply to the list; please *don't* CC me. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
