Hi,
I was able to solve this one, too:
> 2) When I shutdown Icinga on the satellite, the master will show nothing in
> red.
I added to the master zone the following Service check:
object Service "cluster" {
check_command = "cluster"
check_interval = 5s
retry_interval = 1s
host_name =
Hi,
I was able to find an answer for this question:
1) I am not sure where I should place the ping4/6 checks. I want the
master to ping all hosts with address/address6 entries. I tried to add
these checks inside the master zone folder. The checks show up in
icingaweb2, but they are not sheduled
Hi Peter,
- comment the line saying 'include_recursive "conf.d"' at the end of
/etc/icinga2.conf
so there isn'a a mythical directory in the hierarchy that needs to be
kept empty. Things like that WILL backfire sooner or later when you
don't expect it.
it's a good point that it might be better
On Thursday 22 December 2016 at 10:54:59, broseth wrote:
> Dear All ,
>
> I am broseth . I want to install icinga2 for monitor my server and network
> device.
Please start a new thread if you wish to discuss a new topic.
> Could u give me the documentary ?
https://docs.icinga.com/icinga2/lates
Hi @ll,
I strongly opt for Peters approach, that's in fact how I configure all
my systems. The problem with conf.d is that it contains files provided
by upstream. Depending on your package manager the next upgrade might
re-create files you formerly deleted - and you're doomed.
Most package manage
, 2016 4:41 PM
To: Icinga User's Corner
Subject: Re: [icinga-users] Icinga2 best practices
On Thursday 22 December 2016 at 10:36:37, Peter Eckel wrote:
> Hi Antony,
>
> > - rename /etc/icinga2/conf.d to something like
> > /etc/icinga2/conf.d.dist (it doesn't really matte
On Thursday 22 December 2016 at 10:36:37, Peter Eckel wrote:
> Hi Antony,
>
> > - rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist
> > (it doesn't really matter what, just change its name)
> >
> > - create a new, empty /etc/icinga2/conf.d and leave it empty
>
> ... or, much
Hi Antony,
> - rename /etc/icinga2/conf.d to something like /etc/icinga2/conf.d.dist (it
> doesn't really matter what, just change its name)
>
> - create a new, empty /etc/icinga2/conf.d and leave it empty
... or, much more straightforward:
- comment the line saying 'include_recursive "conf.
Hi Antony,
these hints are very important for me. I was now able to change my setup with
your hints and the configuration is synced to the satellite. I was also able to
setup everything needed to execute the basic checks. I identifed a problem in
the Icinga log with the firewall preventing the
On Tuesday 20 December 2016 at 21:38:44, Volker Janzen wrote:
> I see. I just do not understand yet how new commands are added to a
> satellite. There must be some binary or script on the satellite that needs
> to be executed. Will this be configured on the master and/or satellite
> with top-down?
Hi,
> Am 20.12.2016 um 21:38 schrieb Volker Janzen :
>
> The host definition is done by the node wizard. I rewrote some parts of the
> configuration today for using the top-down approach. I now found that the
> master generated in /var/lib/icinga2 these files:
>
> ./api/zones/HOST/_etc/hosts.c
Hi,
> Am 20.12.2016 um 00:00 schrieb Antony Stone
> :
>
> See if this description helps:
thanks for your reply with this excellent explanation. It helps me to
understand the concept how Icinga works.
> Yes, I've seen the term used, I just wanted to stop you trying to find the
> Icinga2 Agent
Hi,
> Am 20.12.2016 um 00:04 schrieb Antony Stone
> :
>
> That's probably a pity, because I think auto-generation of cloud servers,
> including their own Icinga configuration, would be far better suited to
> bottom-
> up, and I also think delegated responsibility for server management,
> incl
Hi,
> Am 20.12.2016 um 00:29 schrieb Lee Clemens :
>
> I think it makes sense, as Director becomes more robust and the use of the
> various
> APIs should fit in neatly with automation/orchestration/cloud-based
> methodologies.
I'll give Director the next try when I can configure Icinga by han
On 12/19/2016 06:04 PM, Antony Stone wrote:
> On Monday 19 December 2016 at 23:56:44, Volker Janzen wrote:
>
>> I just read that the new 2.6 docs top-down is recommended and bottom up has
>> been deprecated.
>
> Oh, I know the docs (I read this bit when it was still 2.5) said that
> top-down
>
On Monday 19 December 2016 at 23:56:44, Volker Janzen wrote:
> I just read that the new 2.6 docs top-down is recommended and bottom up has
> been deprecated.
Oh, I know the docs (I read this bit when it was still 2.5) said that top-down
was far more commonly used, but I didn't know bottom-up had
On Monday 19 December 2016 at 23:38:57, Volker Janzen wrote:
> > then use the master -
> > client setup described in section 6 of the documentaton:
> >
> > https://docs.icinga.com/icinga2/latest/doc/module/icinga2/chapter/distrib
> > uted- monitoring
>
> I read this document, but I was a bit con
Hi,
> You _can_ do that, yes, but I think centrally-configured on the master, using
> top-down command endpoint (see above documentation), is best.
I just read that the new 2.6 docs top-down is recommended and bottom up has
been deprecated. I'm still on 2.5, but will upgrade soon and I think I
Hi,
> Better to remove NRPE and install Icinga on the VMs,
yes, I meant replacing NRPE by Icinga agent.
> 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
I read thi
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 sectio
Hi,
I'm new to Icinga. I like to migrate my Nagios to Icinga 2, because it fits my
needs better. I already did some initial tests and I have some questions about
doing things with Icinga in best practice.
I want to monitor > 10 virtual machines. I setup a Icinga master with
Icingaweb2.
My VMs
21 matches
Mail list logo
