On 12 Jan 2010, at 12:38, [email protected] wrote:
-------- Original-Nachricht --------
Datum: Tue, 12 Jan 2010 11:53:46 +0000
Von: Ton Voon <[email protected]>
An: Opsview Users <[email protected]>
Betreff: Re: [opsview-users] Host Interfaces: critical if admin
down and link down?
On 11 Jan 2010, at 17:56, [email protected] wrote:
If an interface's Links status is down and the admin status is also
down, the Opsview status is critical. But I'd consider the down/down
situation as a intended one, so the Opsview status should be OK.
I see what you mean, but why are you monitoring it? Should it be a
warning or unknown instead so you can disable monitoring of it?
At the moment, you have to "tick" that you want that interface
monitored. This is because we need the extra services created at
Nagios to store the performance data and provide the alerting.
That's the point: If the interfaces that are 'admin down'/'link
down' turn OK in Opsview, you'd be able to "tick" all interfaces
when adding a host (switch/router) and won't have to "tick" it if a
port gets configured 'admin enabled' and connected. Also if a host
is removed, the port gets configured 'admin down' and cable is
disconnected, it wouldn't be necessary to reconfigure the host and
"untick" the interface monitoring.
To put it in a short sentence: I'd like the Opsview status of a
monitored port to be non-OK *only* if the 'links status' and 'admin
status' differ.
Fair enough - I can see that is easier to maintain. I've raised https://secure.opsera.com/jira/browse/OPS-947
to cover this.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
