Re: [Nagios-users] servicedependencies not working
Yeah I've been starting to play with using hostgroups to tie them together
since I can't really use hosts, but so far just limited on time due to
holidays, I hope to get more testing done this week but initial testing looks
like if I can specify the hostgroups in these configs then it works.
Dan
-Original Message-
From: Andreas Ericsson [mailto:a...@op5.se]
Sent: Friday, December 23, 2011 7:09 AM
To: Nagios Users List
Cc: Daniel Wittenberg
Subject: Re: [Nagios-users] servicedependencies not working
On 12/16/2011 04:38 AM, Daniel Wittenberg wrote:
I've started playing with making a bunch of dependencies and at first it
appeared to be working, right now I've got a pretty basic test setup. I've
added one service to be dependent on the other one, but it seems that the
freshness might be mucking with it. Two services below:
define service {
service_description base_log_checks
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3600
check_commandservice_is_
}
define service {
service_description nagios_cron
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3000
check_commandservice_is_stale
}
define servicedependency {
service_description nagios_cron
dependent_service_description base_log_checks
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
inherits_parent 1
}
What appears to happen is that I kill nsclient so nagios_cron starts
reporting stale at 3000 seconds, and the same for base_log_checks shortly
after. Then about every hour I get more stale soft alerts, and then after
the third try it goes to a HARD alert and I still get a ticket, though I'm
not sure why it's even checking if execution should be disable when
nagios_cron is in a warning state. But not only does the active checks
(service_is_stale) get executed but I'm also still getting notifications sent
after 3 attempts, so it doesn't really appear to be doing anything.
Unfortunately right now these servers are so busy it's hard to put them in
debug mode. Have I missed something obvious with these?
I must say though, with the size of your environment, it's quite possible that
just looking up the dependency takes longer than it does to just execute the
extra check. If you're looking to save time, that might well bite you in the
ass. It's something that will probably be improved til Nagios 4, but it will
require a change in Nagios' object structure, so we can't really do it without
upping the major version number :-/
--
Andreas Ericsson andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] servicedependencies not working
Adding in the hostgroups seems to get things working as I would expect. I
guess this is another case where active checks does not include those
performed by freshness checking. Even though I have execution_failure_criteria
set to not run on warning and critical, it seems freshness checks are still
performed. The good thing is this doesn't generate any alerts it just
clutters up the interface so if you are looking to see what's wrong in the
web gui you see lots of warnings associated with it when really the agent is
just down and we were already notified of that. So it would be nice if you
could have a setting that would tell it that freshness checks should be treated
the same way as active checks.
Dan
-Original Message-
From: Andreas Ericsson [mailto:a...@op5.se]
Sent: Friday, December 23, 2011 7:09 AM
To: Nagios Users List
Cc: Daniel Wittenberg
Subject: Re: [Nagios-users] servicedependencies not working
On 12/16/2011 04:38 AM, Daniel Wittenberg wrote:
I've started playing with making a bunch of dependencies and at first it
appeared to be working, right now I've got a pretty basic test setup. I've
added one service to be dependent on the other one, but it seems that the
freshness might be mucking with it. Two services below:
define service {
service_description base_log_checks
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3600
check_commandservice_is_
}
define service {
service_description nagios_cron
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3000
check_commandservice_is_stale
}
define servicedependency {
service_description nagios_cron
dependent_service_description base_log_checks
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
inherits_parent 1
}
What appears to happen is that I kill nsclient so nagios_cron starts
reporting stale at 3000 seconds, and the same for base_log_checks shortly
after. Then about every hour I get more stale soft alerts, and then after
the third try it goes to a HARD alert and I still get a ticket, though I'm
not sure why it's even checking if execution should be disable when
nagios_cron is in a warning state. But not only does the active checks
(service_is_stale) get executed but I'm also still getting notifications sent
after 3 attempts, so it doesn't really appear to be doing anything.
Unfortunately right now these servers are so busy it's hard to put them in
debug mode. Have I missed something obvious with these?
I must say though, with the size of your environment, it's quite possible that
just looking up the dependency takes longer than it does to just execute the
extra check. If you're looking to save time, that might well bite you in the
ass. It's something that will probably be improved til Nagios 4, but it will
require a change in Nagios' object structure, so we can't really do it without
upping the major version number :-/
--
Andreas Ericsson andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] servicedependencies not working
On 12/16/2011 04:38 AM, Daniel Wittenberg wrote:
I've started playing with making a bunch of dependencies and at first it
appeared to be working, right now I've got a pretty basic test setup. I've
added one service to be dependent on the other one, but it seems that the
freshness might be mucking with it. Two services below:
define service {
service_description base_log_checks
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3600
check_commandservice_is_
}
define service {
service_description nagios_cron
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3000
check_commandservice_is_stale
}
define servicedependency {
service_description nagios_cron
dependent_service_description base_log_checks
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
inherits_parent 1
}
What appears to happen is that I kill nsclient so nagios_cron starts
reporting stale at 3000 seconds, and the same for base_log_checks shortly
after. Then about every hour I get more stale soft alerts, and then after
the third try it goes to a HARD alert and I still get a ticket, though I'm
not sure why it's even checking if execution should be disable when
nagios_cron is in a warning state. But not only does the active checks
(service_is_stale) get executed but I'm also still getting notifications sent
after 3 attempts, so it doesn't really appear to be doing anything.
Unfortunately right now these servers are so busy it's hard to put them in
debug mode. Have I missed something obvious with these?
I must say though, with the size of your environment, it's quite possible that
just looking up the dependency takes longer than it does to just execute the
extra check. If you're looking to save time, that might well bite you in the
ass. It's something that will probably be improved til Nagios 4, but it will
require a change in Nagios' object structure, so we can't really do it without
upping the major version number :-/
--
Andreas Ericsson andreas.erics...@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] servicedependencies not working
Dan
Even for the same host dependencies you still need to define a host in the
servicedependency definitions.
At the moment your servicedependency (the one you pasted here) is not
associated with any host and hence the logic is not implemented on any host
testing logic.
Assaf
- Original Message -
From: Daniel Wittenberg daniel.wittenberg.r...@statefarm.com
To: nagios-users@lists.sourceforge.net nagios-users@lists.sourceforge.net
Sent: Thursday, 15 December, 2011 5:38:53 PM
Subject: [Nagios-users] servicedependencies not working
I’ve started playing with making a bunch of dependencies and at first it
appeared to be working, right now I’ve got a pretty basic test setup. I’ve
added one service to be dependent on the other one, but it seems that the
freshness might be mucking with it. Two services below:
define service {
service_description base_log_checks
servicegroups base_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3600
check_command service_is_
}
define service {
service_description nagios_cron
servicegroups base_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3000
check_command service_is_stale
}
define servicedependency {
service_description nagios_cron
dependent_service_description base_log_checks
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
inherits_parent 1
}
What appears to happen is that I kill nsclient so nagios_cron starts reporting
“stale” at 3000 seconds, and the same for base_log_checks shortly after. Then
about every hour I get more “stale” soft alerts, and then after the third try
it goes to a HARD alert and I still get a ticket, though I’m not sure why it’s
even checking if execution should be disable when nagios_cron is in a warning
state. But not only does the active checks (service_is_stale) get executed but
I’m also still getting notifications sent after 3 attempts, so it doesn’t
really appear to be doing anything. Unfortunately right now these servers are
so busy it’s hard to put them in debug mode. Have I missed something obvious
with these?
Dan
--
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/
___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
--
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for
developers. It will provide a great way to learn Windows Azure and what it
provides. You can attend the event by watching it streamed LIVE online.
Learn more at http://p.sf.net/sfu/ms-windowsazure___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
[Nagios-users] servicedependencies not working
I've started playing with making a bunch of dependencies and at first it
appeared to be working, right now I've got a pretty basic test setup. I've
added one service to be dependent on the other one, but it seems that the
freshness might be mucking with it. Two services below:
define service {
service_description base_log_checks
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3600
check_commandservice_is_
}
define service {
service_description nagios_cron
servicegroupsbase_service_group
hostgroup_name base_windows_2003
use generic-passive-service
check_freshness 1
freshness_threshold 3000
check_commandservice_is_stale
}
define servicedependency {
service_description nagios_cron
dependent_service_description base_log_checks
execution_failure_criteria w,u,c
notification_failure_criteria w,u,c
inherits_parent 1
}
What appears to happen is that I kill nsclient so nagios_cron starts reporting
stale at 3000 seconds, and the same for base_log_checks shortly after. Then
about every hour I get more stale soft alerts, and then after the third try
it goes to a HARD alert and I still get a ticket, though I'm not sure why it's
even checking if execution should be disable when nagios_cron is in a warning
state. But not only does the active checks (service_is_stale) get executed but
I'm also still getting notifications sent after 3 attempts, so it doesn't
really appear to be doing anything. Unfortunately right now these servers are
so busy it's hard to put them in debug mode. Have I missed something obvious
with these?
Dan
--
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/___
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
