Nagios: Service dependency on same host for an entire hostgroupSpace out various service checks for a host with NagiosNagios check for service not if host is upSet Host status from service status on NagiosNAGIOS notification command for service/contactgroupHow to dedicate hostgroup to user in Nagios core?Nagios service check interval based on host typeOverriding Nagios hostgroup service with host serviceNagios: check host service even if host is downNagios exclude a service for a single hostNagios: Dependency from service to different host
Why does Taylor’s series “work”?
On a piano, are the effects of holding notes and the sustain pedal the same for a single chord?
Was murdering a slave illegal in American slavery, and if so, what punishments were given for it?
How does the "reverse syntax" in Middle English work?
Vehemently against code formatting
Gambler's Fallacy Dice
How can sister protect herself from impulse purchases with a credit card?
Chain rule instead of product rule
Will this series of events work to drown the Tarrasque?
How do I unravel apparent recursion in an edef statement?
Novel where a cube cooled below absolute zero makes a hole in reality
What city and town structures are important in a low fantasy medieval world?
Bash Read: Reading comma separated list, last element is missed
Head-internal relative clauses
How do we explain the use of a software on a math paper?
Why is so much ransomware breakable?
Managing heat dissipation in a magic wand
Why is python script running in background consuming 100 % CPU?
Why did Nick Fury not hesitate in blowing up the plane he thought was carrying a nuke?
How come Arya Stark wasn't hurt by this in Game of Thrones Season 8 Episode 5?
How to determine the distribution of Ubuntu
Parse a C++14 integer literal
Was Tyrion always a poor strategist?
Warped chessboard
Nagios: Service dependency on same host for an entire hostgroup
Space out various service checks for a host with NagiosNagios check for service not if host is upSet Host status from service status on NagiosNAGIOS notification command for service/contactgroupHow to dedicate hostgroup to user in Nagios core?Nagios service check interval based on host typeOverriding Nagios hostgroup service with host serviceNagios: check host service even if host is downNagios exclude a service for a single hostNagios: Dependency from service to different host
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a Nagios system with a large number of hosts categorised in different hostgroups. Each of these hosts has two services monitored on it, one of which is intended to be dependent on the other - if service1 is WARNING or CRITICAL, service2 on that server should not give an alert as well. service2 is intended more for statistic collection, while service1 is a simple availability check - as such, I always want service2 checking, but not alerting if service1 is reporting as down.
This is my services.cfg entry:
define servicedependency
hostgroup example-servers
#host_name host1.example.com,host2.example.com
service_description service1
dependent_service_description service2
execution_failure_criteria n
notification_failure_criteria u,w,c,o
I have tried both specifying it via a hostgroup and as a list of individual servers. Ideally, I would do it for the entire hostgroup in one rather than have to constantly maintain a list.
However, this does not seem to work, either way. If service1 is down, service2 also shows a CRITICAL status in the problems screen and on host details.
nagios
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
add a comment |
I have a Nagios system with a large number of hosts categorised in different hostgroups. Each of these hosts has two services monitored on it, one of which is intended to be dependent on the other - if service1 is WARNING or CRITICAL, service2 on that server should not give an alert as well. service2 is intended more for statistic collection, while service1 is a simple availability check - as such, I always want service2 checking, but not alerting if service1 is reporting as down.
This is my services.cfg entry:
define servicedependency
hostgroup example-servers
#host_name host1.example.com,host2.example.com
service_description service1
dependent_service_description service2
execution_failure_criteria n
notification_failure_criteria u,w,c,o
I have tried both specifying it via a hostgroup and as a list of individual servers. Ideally, I would do it for the entire hostgroup in one rather than have to constantly maintain a list.
However, this does not seem to work, either way. If service1 is down, service2 also shows a CRITICAL status in the problems screen and on host details.
nagios
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
add a comment |
I have a Nagios system with a large number of hosts categorised in different hostgroups. Each of these hosts has two services monitored on it, one of which is intended to be dependent on the other - if service1 is WARNING or CRITICAL, service2 on that server should not give an alert as well. service2 is intended more for statistic collection, while service1 is a simple availability check - as such, I always want service2 checking, but not alerting if service1 is reporting as down.
This is my services.cfg entry:
define servicedependency
hostgroup example-servers
#host_name host1.example.com,host2.example.com
service_description service1
dependent_service_description service2
execution_failure_criteria n
notification_failure_criteria u,w,c,o
I have tried both specifying it via a hostgroup and as a list of individual servers. Ideally, I would do it for the entire hostgroup in one rather than have to constantly maintain a list.
However, this does not seem to work, either way. If service1 is down, service2 also shows a CRITICAL status in the problems screen and on host details.
nagios
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
I have a Nagios system with a large number of hosts categorised in different hostgroups. Each of these hosts has two services monitored on it, one of which is intended to be dependent on the other - if service1 is WARNING or CRITICAL, service2 on that server should not give an alert as well. service2 is intended more for statistic collection, while service1 is a simple availability check - as such, I always want service2 checking, but not alerting if service1 is reporting as down.
This is my services.cfg entry:
define servicedependency
hostgroup example-servers
#host_name host1.example.com,host2.example.com
service_description service1
dependent_service_description service2
execution_failure_criteria n
notification_failure_criteria u,w,c,o
I have tried both specifying it via a hostgroup and as a list of individual servers. Ideally, I would do it for the entire hostgroup in one rather than have to constantly maintain a list.
However, this does not seem to work, either way. If service1 is down, service2 also shows a CRITICAL status in the problems screen and on host details.
nagios
nagios
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
asked Mar 8 '13 at 15:41
jreid9001jreid9001
13626
13626
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
From the Nagios manual for "execution_failure_criteria": "If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be)."
Sounds like you should be using "u,c" instead (don't check if server1 is UNKNOWN or CRITICAL). Or perhaps "w,u,c" IF a WARNING state from service1 should also cause service2 not to execute.
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
add a comment |
If you specify "execution_failure_criteria n" then service2 will always be checked. If is is checked and is in a warning or critical state the user interface will show that state. You can't prevent that (afaik), but you can prevent it sending notifications, e.g "notification_failure_criteria u,w,c".
I think you can either have "execution_failure_criteria" set as it is (i.e. "n"), and live with the status showing service2 as critical when it can't be reached, or change it to "c".
You probably don't want to suppress notifications if service1 is OK, which is what you are doing with the "o" in "notification_failure_criteria u,w,c,o".
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f486027%2fnagios-service-dependency-on-same-host-for-an-entire-hostgroup%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the Nagios manual for "execution_failure_criteria": "If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be)."
Sounds like you should be using "u,c" instead (don't check if server1 is UNKNOWN or CRITICAL). Or perhaps "w,u,c" IF a WARNING state from service1 should also cause service2 not to execute.
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
add a comment |
From the Nagios manual for "execution_failure_criteria": "If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be)."
Sounds like you should be using "u,c" instead (don't check if server1 is UNKNOWN or CRITICAL). Or perhaps "w,u,c" IF a WARNING state from service1 should also cause service2 not to execute.
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
add a comment |
From the Nagios manual for "execution_failure_criteria": "If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be)."
Sounds like you should be using "u,c" instead (don't check if server1 is UNKNOWN or CRITICAL). Or perhaps "w,u,c" IF a WARNING state from service1 should also cause service2 not to execute.
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
From the Nagios manual for "execution_failure_criteria": "If you specify n (none) as an option, the execution dependency will never fail and checks of the dependent service will always be actively checked (if other conditions allow for it to be)."
Sounds like you should be using "u,c" instead (don't check if server1 is UNKNOWN or CRITICAL). Or perhaps "w,u,c" IF a WARNING state from service1 should also cause service2 not to execute.
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
answered Mar 10 '13 at 0:10
Jim BlackJim Black
281212
281212
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
add a comment |
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
I'd like the check to be made in any case (for performance data), but only to send notifications if service1 is not warning/critical.
– jreid9001
Mar 11 '13 at 10:03
add a comment |
If you specify "execution_failure_criteria n" then service2 will always be checked. If is is checked and is in a warning or critical state the user interface will show that state. You can't prevent that (afaik), but you can prevent it sending notifications, e.g "notification_failure_criteria u,w,c".
I think you can either have "execution_failure_criteria" set as it is (i.e. "n"), and live with the status showing service2 as critical when it can't be reached, or change it to "c".
You probably don't want to suppress notifications if service1 is OK, which is what you are doing with the "o" in "notification_failure_criteria u,w,c,o".
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
add a comment |
If you specify "execution_failure_criteria n" then service2 will always be checked. If is is checked and is in a warning or critical state the user interface will show that state. You can't prevent that (afaik), but you can prevent it sending notifications, e.g "notification_failure_criteria u,w,c".
I think you can either have "execution_failure_criteria" set as it is (i.e. "n"), and live with the status showing service2 as critical when it can't be reached, or change it to "c".
You probably don't want to suppress notifications if service1 is OK, which is what you are doing with the "o" in "notification_failure_criteria u,w,c,o".
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
add a comment |
If you specify "execution_failure_criteria n" then service2 will always be checked. If is is checked and is in a warning or critical state the user interface will show that state. You can't prevent that (afaik), but you can prevent it sending notifications, e.g "notification_failure_criteria u,w,c".
I think you can either have "execution_failure_criteria" set as it is (i.e. "n"), and live with the status showing service2 as critical when it can't be reached, or change it to "c".
You probably don't want to suppress notifications if service1 is OK, which is what you are doing with the "o" in "notification_failure_criteria u,w,c,o".
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
If you specify "execution_failure_criteria n" then service2 will always be checked. If is is checked and is in a warning or critical state the user interface will show that state. You can't prevent that (afaik), but you can prevent it sending notifications, e.g "notification_failure_criteria u,w,c".
I think you can either have "execution_failure_criteria" set as it is (i.e. "n"), and live with the status showing service2 as critical when it can't be reached, or change it to "c".
You probably don't want to suppress notifications if service1 is OK, which is what you are doing with the "o" in "notification_failure_criteria u,w,c,o".
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
answered Mar 21 '15 at 17:11
John BallJohn Ball
19612
19612
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f486027%2fnagios-service-dependency-on-same-host-for-an-entire-hostgroup%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
