I have two servers working as active standby MSSQL Servers. I made a service for each server and configured a BPI group for both services where it fires alarm only in case both services are down.
that is working fine... i have one problem in the dashboards and other screens (Operation Screen and Operation Center) where the service for the standby host is always appearing.
How can i hide both services while keep them functional?
Hide Service
Re: Hide Service
If you acknowledge the problem for that host it will hide it from the Operations screen pages, as well as the unhandled problem pages. However, using this method you'll want to tell BPI to ingore scheduled downtime and acknowledged problems in the group logic. This can be set from the Admin->Manage Components->Edit Settings (icon) for Nagios BPI.
-
ahmad.zuhd
- Posts: 44
- Joined: Sun Jul 01, 2012 2:33 am
Re: Hide Service
I know that acknowledging the service will hide it. However, i need to find another way to configure the service to be hidden without that. I think it must be taken into consideration when using the BPI
Concerning your comment:
do you agree with me on that?
Concerning your comment:
I dont need the BPI to ignore the acknowledged problem cuase in my case (i have a database cluster with the same service running in both servers and on of them is up and the other is waiting) so i configured the BPI service to changed to critical state when both services are down. however since i need to acknowledge one to be hidden, i dont need the BPI to ignore it..mguthrie wrote:However, using this method you'll want to tell BPI to ingore scheduled downtime and acknowledged problems in the group logic. This can be set from the Admin->Manage Components->Edit Settings (icon) for Nagios BPI.
do you agree with me on that?
Last edited by slansing on Tue Apr 16, 2013 10:13 am, edited 1 time in total.
Reason: Merged posts due to double posting.
Reason: Merged posts due to double posting.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Hide Service
BPI won't ignore acknowledged problems, they will still be included in the algorithm when calculating if the group is up or down.ahmad.zuhd wrote:I dont need the BPI to ignore the acknowledged problem cuase in my case
-
ahmad.zuhd
- Posts: 44
- Joined: Sun Jul 01, 2012 2:33 am
Re: Hide Service
according to the description
Logic Handling For Problem States: Ignore host and service problems that are acknowledged or in scheduled downtime.Handled problems will not be factored into the group's problem percentage.
what does that mean..
also can you please advice about hiding the service using the config parameters rather than acknowledging the service.
Logic Handling For Problem States: Ignore host and service problems that are acknowledged or in scheduled downtime.Handled problems will not be factored into the group's problem percentage.
what does that mean..
also can you please advice about hiding the service using the config parameters rather than acknowledging the service.
Re: Hide Service
OK, so lets rewind things just a bit. What's the final goal in all of this? I'm guessing you only want to receive alerts or see the problem if both services are down correct? If you have a BPI check running against that group, you'll get that behavior, but as far as the Unhandled Service problems page goes, you'll still see the down service if one of them is down, and there's no way to change that behavior.
Note for swilkerson: The documentation is correct. You can tell BPI to ignore problems if they've been acknowledged or in scheduled downtime. BPI will not count them as problems.
Note for swilkerson: The documentation is correct. You can tell BPI to ignore problems if they've been acknowledged or in scheduled downtime. BPI will not count them as problems.
-
ahmad.zuhd
- Posts: 44
- Joined: Sun Jul 01, 2012 2:33 am
Re: Hide Service
ok seems there is no way to hide the service other than acknowledgment.
can u please consider that change in future releases
can u please consider that change in future releases