In hyperic open source , how do I prevent getting alerts for a server that

[hypermike]

Whats the best way in Hyperic open source to have alerts NOT to be sent for numerous
remote agents on servers if the problem is a NETWORK problem and NOT a server problem on a particular network???

I believe currently if the Hyperic server cant talk to an agent on another system then all alerts for that remote system will fire off even if its a NETWORK problem. Is there a way in the Hyperic Open source to avoid this as an issue by defining alerts differently . Any ideas
would be appreciated.

[jtravis_hyperic]

You can achieve this by enabling the alert filtering on your definition.

-- Jon


On Oct 5, 2007, at 5:04 PM, mike monczynski wrote:

> Whats the best way in Hyperic open source to have alerts NOT to be
> sent for numerous
> remote agents on servers if the problem is a NETWORK problem and
> NOT a server problem on a particular network???
>
> I believe currently if the Hyperic server cant talk to an agent on
> another system then all alerts for that remote system will fire off
> even if its a NETWORK problem. Is there a way in the Hyperic Open
> source to avoid this as an issue by defining alerts differently .
> Any ideas
> would be appreciated.

[hypermike]

Do you have a small example of what you are calling alert filtering for such a problem as
a network problem and NOT a remote agent system ???

Isnt this only for the Enterprise Version. I stated in the original question that I was using the 3.1 Hyperic open source versions

Message was edited by: hypermike

[chol_hyperic]

Hi!

This question is really the make or break issue for us regarding purchase and/or download of HQ.
I'd really like to know if this is possible, and if so, a basic rundown on how it is determined to be a network error.
Otoh, is it possible to specify an alarm to be dependant on another alarm not in effect?
(if server1_status=down; sound_alarm; unless router1_status=down) ...


Thanks alot, Chol.

[chol_hyperic]

Posting to the wrong guy before.. Path-based alarm suppression.

[BradFelmey]

Policy-based alerting is part of HQ Enterprise Edition. It is not present in the HQ Open-Source version.

[chol_hyperic]

Thanks for a quick answer, we will ofcourse look into the Enterprise Edition.


c.

[hypermike]

I never got a answer to the question I asked. I was told to use alert filtering and asked
for an example. Was the answer that - to use alert filtering the same as what you call
Policy -based alerting . I didnt understand what the answer to use alertfiltering was referring to.
Please note earlier replies from J travis.

Message was edited by: hypermike

[hypermike]

Is the ploicy based alerting you are talking about the saame thing jtravis calls alert filtering ???

[hypermike]

Can anybody just give a 1 or 2 sentence answer to this question. I know nagios can do this .

Is the ploicy based alerting you are talking about above the same thing jtravis calls alert filtering ???

[jtravis_hyperic]

With 3.2, you have the ability to turn off alerts, system wide (for
cases such as moving your infrastructure or other things which may
trigger massive alerts).

Another way to is to use the 'Filter Alerts' checkbox on your alert
definitions. This collapses all alerts that happen on a platform
into a single email.

Another way to avoid getting alert emails is using the 'Follow the
Sun' role calendars in the Role admin area.

-- Jon


On Oct 25, 2007, at 5:03 PM, mike monczynski wrote:

> Can anybody just give a 1 or 2 sentence answer to this question. I
> know nagios can do this .
>
> Is the ploicy based alerting you are talking about above the same
> thing jtravis calls alert filtering ???

[staceyeschneide]

We should point out that 3.2 is the winter release we are working on, and the Follow-the-sun alerts is a Enterprise feature as well.