Configuration option to preserve ifOperStatus data polled during ifLastChange updates

In the current implementation, SevOne discards all polled data for a given polling interval whenever it detects an update to ifLastChange. Although this behaviour is designed to maintain data consistency, it introduces a significant limitation for interface state monitoring.

When an interface transitions from up (ifOperStatus = 1) to down (ifOperStatus = 2), the ifLastChange attribute is updated as an immediate result of that transition. Since SevOne discards all collected metrics for that poll cycle after detecting an ifLastChange update, the ifOperStatus = 2 value—captured within that same polling interval—is removed before it can be stored or evaluated for alerting.

This results in down events not being captured reliably, preventing accurate interface state alerting.

Requested Enhancement:

Introduce a configuration option that allows specific OIDs—particularly ifOperStatus—to be exempt from the discard‑on‑ifLastChange behaviour.

This would ensure that critical operational state transitions are preserved and evaluated for alerting, even when accompanied by an ifLastChange update.

Possible implementation options include:

• A configurable whitelist of OIDs that should not be discarded when ifLastChange updates occur.
• A toggle to disable discard behaviour entirely for interface‑level status OIDs.
• A per‑device or per‑policy override within polling settings.