I am remote now, but i will send you some debug info later today or tomorrow.

What we see are interfaces being ignored for alerts (alerts off for specific interface, under the device settings) still alerting for several alert checks (up/down, half udplex, mtu, etc). It looks like some interfaces are ok, but also after enabling>saving>rediscover>polling>disabling>saving>Discovery>polling, the interface is still being alerted on. 

Bastiaan

Op 14 apr. 2016 om 14:35 heeft Adam Armstrong <adama@memetic.org> het volgende geschreven:

I've just tested this, and it seems to be working fine for me. Ignoring ports removed them from the status notifications table.

adam.

On 14/04/2016 13:32:14, Adam Armstrong <adama@memetic.org> wrote:

This is affecting the alerting stuff, too?

adam.

On 14/04/2016 13:25:18, Bastiaan Topper <b.topper@korton.nl> wrote:

Hi,

We are experiencing the same issue. We have a lot of interfaces excluded from alerting. This stopped working about a week ago. We dont want to ignore the specific interface alerts for a specific time or until it recovers ( the features we currently have in the alerting system) but also want to be able to ignore interfaces complete from the interface based alerts. We use this quite a lot.
Would be great to have this feature back :)

Regards,

Bastiaan Topper
Op 14 apr. 2016 om 14:02 heeft Robert Williams <Robert@CustodianDC.com> het volgende geschreven:

Hehe, well, I’m confident they were being ignored up until last week because we suddenly have so many, that for them all to appear at once suggests a global change to me. The ignore port feature is pretty handy, there are a number of interface types which we ignore errors for, but still collect data from them. Anything half-duplex (Carel pCOs, modbus interfaces, generators, door controls, environmental stuff etc.) and a lot of windows servers (don’t choke, please) - particularly on customers boxes with MS Hyper-V and the 2 million made-up sub-interfaces it creates for fun.

 

So, please can it stay ‘appreciated’ - it’s very much liked here :)

 

Cheers!

 

Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong
Sent: 14 April 2016 12:35
To: observium@observium.org
Subject: Re: [Observium] (Not)Ignored Ports

 

Well, since the thing you're looking at is deprecated, there's no preferred method :P

 

But having those ports set as ignored should cause them not to appear there. I've no idea why they are. Are you sure they weren't always?

 

adam.

On 14/04/2016 10:37:35, Robert Williams <robert@custodiandc.com> wrote:

Ahhh, ok, no problem. If it’s being depreciated then what’s the preferred exclusion method for rubbish half-duplex ports that throw errors all day? Is there an alternative way of filtering their noise out?

 

Cheers!

 

Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong
Sent: 14 April 2016 10:25
To: observium@observium.org
Subject: Re: [Observium] (Not)Ignored Ports

 

This is probably related to some changes I made the other day to try to make some things more consistent when displaying status counts. This box is currently semi-deprecated, but I'll have a look later!

 

adam.

On 14/04/2016 09:53:57, Robert Williams <robert@custodiandc.com> wrote:

Hi All,

 

Is anyone else seeing this? Or any pointers towards a flag that needs to be set to stop them showing up? It makes reading the summary notifications quite difficult when it’s flooded with irrelevant errored ports :)

 

Cheers!

 

Robert Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com

From: observium [mailto:observium-bounces@observium.org] On Behalf Of Robert Williams
Sent: 10 April 2016 12:02
To: Observium Network Observation System (observium@observium.org) <observium@observium.org>
Subject: [Observium] (Not)Ignored Ports

 

Hi,

 

It looks like ignored ports are suddenly being included in the ‘Device Status Notifications’ for Errors.

 

We have quite a few devices which have ‘expected’ errors (half-duplex IP-PDUs etc.) so are now being spammed with error’ed ports:

 

 

They _do_ disappear if I select the device itself to be ignored, but they used to be silenced just by setting the ‘Alerts’ column to ‘No’.

 

 

Is this an error - or is there now an intentional new variable which I need to set in config.php to ignore them?

 

Cheers guys!

 

 

Robert Williams

Custodian Data Centre