New in icinga2. So may be the question is already answered or known to community.
I have installed a master icinga2 server on CentOS
I have installed client icinga2 agent on SUSE
I have graphite
I have director
Now before I ran the $icinga2 node wizard the master server server’s self monitoring was done by icinga2 automatically. But as soon as I ran that and changed it to master it stopped monitoring self.
Can you share any document which can help me to setup both agent and agentless monitoring.
Currently under /etc/icinga2/zones.d/master
I have 2 files
services.conf → Contains service defination
I guess you answered the last question of the node wizard with yes:
Do you want to disable the inclusion of the conf.d directory [Y/n]:
This removes the example config which is part of the package. Hence, the host is no longer “self monitored”. But this is ok as you want to use the director. Means start creating a host object for the master and create any required service objects.
Thank You. Understood why it removed the self monitoring. But on the Master Server since already icinga2 is installed as server - will I be installing another icinga2 as agent on the icinga2 master server ? My other servers have icinga2 agents configured
Also can we have both agentless and agent based monitoring in icinga2 at the same time? If yes do you have any step by step docs around it
No, you just need one icinga instance per node, one is configured as master and other are configured as clients. Have you already read this chapter? It’s a good starting point to get knowledge about the basics as it explains the concept and all details.
Sorry, but this is still a little unclear to me, despite me browsing through available docs.
I have already installed Icinga server on ServerX to remotely monitor other host services.
I also would like to setup 2nd pillar, which is client-based monitoring.
Can i create master node on the same ServerX then? Seems exclusion of conf.d directory makes it not possible.
Ah, sorry, I thought you were saying that you have ServerX running Icinga and
remotely monitoring other host services, but you were confused about the
definitions of Master, Satellite and Agent.
You’re right, the Master setup does disable the inclusion of conf.d in the
icinga.conf file, so you should move any configuration you have in there to
something under zones.d (I suggest something like /etc/icinga2/zones.d/master
since these will only be configuration files you have created for the master so
far), and then you create anything specific to the Agents under something along
the lines of /etc/icinga2/zones.d/agentone etc.
“Next, you need to define two zones. There is no naming convention, best
practice is to either use master, satellite/agent-fqdn or to choose region
names for example Europe, USA and Asia, though.”
Master zone name [master]: agentbased
Default global zones: global-templates director-global
Do you want to specify additional global zones? [y/N]: n
Do you want to disable the inclusion of the conf.d directory [Y/n]: y
i get service start failure (code=exited, status=139) with no trace of problems in logs…
I do not use Director, as the Linux server has no X module yet, just plain text
Therefore I think i can leave API disabled, which is a good news since it causes some memory violation 139 codes
Where should one search if Icinga is up and running but netstat shows no trace of listening on ports?
I reaused a thread, which i understand is not advised on this Forum, but am used to this approach to minimize number of threads…
Yes, I did run api setup, and the root password is stored properly in api-users.conf
Yes, I did run node wizard per below:
Master zone name [master]: agentbased
Default global zones: global-templates director-global
Do you want to specify additional global zones? [y/N]: n
Do you want to disable the inclusion of the conf.d directory [Y/n]: y
Afterwards, the content of zones.conf is:
/*
* Generated by Icinga 2 node setup commands
* on 2020-08-28 13:58:32 +0000
*/
object Endpoint "linuxserver.domain.com" { }
object Zone "agentbased" {
endpoints = [ "linuxserver.domain.com" ] }
object Zone "global-templates" {
global = true }
object Zone "director-global" {
global = true }
It’s not wanted and even turns into an disadvantage as users might have ignored this thread and you’ll get less attention.
Hmm, I’m getting more confused about your config (and this is one result of reusing a thread). You don’t need to run api setup and node wizard. Hence, I’d recommend to start a new thread and give more details about your setup and what you have already done.
