Martijn C
Guest
|
 Posted:
Tue Nov 01, 2005 1:51 pm Post subject:
Resolving an Active alert: wrong status (?) |
|
|
Dear Newsgroup,
I want to discuss the behaviour of the "Agent Heartbeat"-Alert in
combination with resolving (also in Maintenance mode).
When there is a Agente Heartbeat error the server status will be grey.
When this alert is manually resolved the server status is ok and it
looks like the server is not down. Only when you look at the last
heartbeat you can conclude that the server is down.
I notice that this resolved ticket is still "Active", shouldn't it be
that active alerts can't be resolved? (or an option that arranges for
that)
When a machine goes down during maintenance mode, this heartbeat alert
is immediately set to "resolved". When the maintenance is switched off
and the server is still down the server has a "green" state which will
only reflect the real situation when the heartbeat alert is unresolved.
Shoudn't active alerts be set to new when machine is removed from
maintenance?
Did anybody struggle with the same issue before? Is there some Tool /
method developed?
Thanks ahead for you response!
Regards,
Martijn. |
|
Adam White
Guest
|
| Posted:
Wed Nov 02, 2005 1:51 am Post subject:
RE: Resolving an Active alert: wrong status (?) |
|
|
The only solution I have is "don't take it out of maintenance mode until you
have confirmed it is back up" sorry
"Martijn C" wrote:
| Quote: | Dear Newsgroup,
I want to discuss the behaviour of the "Agent Heartbeat"-Alert in
combination with resolving (also in Maintenance mode).
When there is a Agente Heartbeat error the server status will be grey.
When this alert is manually resolved the server status is ok and it
looks like the server is not down. Only when you look at the last
heartbeat you can conclude that the server is down.
I notice that this resolved ticket is still "Active", shouldn't it be
that active alerts can't be resolved? (or an option that arranges for
that)
When a machine goes down during maintenance mode, this heartbeat alert
is immediately set to "resolved". When the maintenance is switched off
and the server is still down the server has a "green" state which will
only reflect the real situation when the heartbeat alert is unresolved.
Shoudn't active alerts be set to new when machine is removed from
maintenance?
Did anybody struggle with the same issue before? Is there some Tool /
method developed?
Thanks ahead for you response!
Regards,
Martijn.
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in