New Icinga Installation

Icinga 2 Core
#1

Hello all.
I’m trying to migrate a ICINGA install from one VM to another.
This is because the source was installed by a partner and we would like to migrate to a new VM with all the OS updates and ICINGA updates and gather more knowledge of the plataform.
So far I’ve managed to install the latest ICINGA in a new VM perfectly following this guide:

Please note, that I don’t mind installing the agent in all my monitored hosts to migrate the new ICINGA.

So I have a couple of questions:

  • After the install, do I have to run icinga2 node wizard to setup the Master? If so, why when I do that the Icinga Server disappears from the hosts? (If I don’t I get the error critical/cli: Ticket salt (–salt) must be specified.) when trying to create the ticket for the host.

  • To monitor Windows VM’s should I use Powershell plugins (as I’ve read here somewhere) or do I use the agent as I did with the old install?

  • I’ve noticed that in my old install I have zones configured. Where can I configure that? Is it during the Master setup?

  • Is PNP still the best way to get metrics from hosts?

  • Can I configure https for icingaweb2 portal?

  • Why in the setup there was no need to use SSL (should I?) and is there a problem that I did not select UTF8 for the DB?

Basically, I’m a bit lost from where to go from after the initial install, can anyone advise or provide some help?

Thank you.

#2

Hello @samotelf,
Did you run the Icinga2 node wizard yet? That should be one of the first steps in setting up a new Icinga2 Master server (I did not see that step in the blog post your provided). After the the node wizard is finished, then add monitoring check for the Master sever for services (CPU, Disk, Memory, etc…). You should always monitor your monitoring server. :slight_smile:

Once you configured your Master server correctly than think about how you want your zones configured. Start with the basic, one master and one zone. Review this, https://icinga.com/docs/icinga-2/latest/doc/06-distributed-monitoring/#master-with-agents

Than add the Icinga2 agent software on your Linux or Windows servers to get monitored.

I hope this helps
A

#3

This is because the node wizard will stop including the example configuration from the /etc/icinga2/conf.d directory.
I would also suggest you check the docs posted by @aclark6996

This is entirely up to you :smiley: You could use the agent, the new Icinga for Windows. If the agent is already installed on the servers you could connect them to the new master by running the node wizard of the agent again.

What kind of zones do you mean? Satellite zones, other global zones?

I would say no. I would go for either graphite or influxdb+grafana.

Yes. The simple way would be to enable ssl in your webserver and just rewrite the http calls to https.
Example for apache2 running on Ubuntu/Debian

sed -i '/DocumentRoot/a\
\
                # Redirect to Subfolder icingaweb2\
                RedirectMatch ^\/$ \/icingaweb2\/' /etc/apache2/sites-available/default-ssl.conf

sed -i '/DocumentRoot/a\
\
        # Rewrite to HTTPS\
        RewriteEngine On\
        RewriteCond %{HTTPS} off\
        RewriteRule ^\/?(.*)$ https:\/\/%{HTTP_HOST}\/$1 [R=301,L]' /etc/apache2/sites-available/000-default.conf

systemctl restart apache2.service

This will leave you with a simple https setup, you will need to change the ssl certificate in your webserver with one mathcing the website/hostname.

Don’t think so, the icinga-ido db does not need the UTF-8 encoding afaik.

#4

Thank you so much for your reply.
Will do as sson as I get to the office again.

#5

Thank you so much for your reply.
As soon as I get to work tomorrow I’ll investigate the zones topic and will reply if you don’t mind.