Updates in upcoming releases

Important changes in future releases that might require additional steps or planning during an upgrade.

Alert deduplication behavior updates

Alert deduplication has been available as an experimental, opt-in feature, disabled by default and fully configurable by users. Users can currently toggle it at will, and we have documented and announced it in previous release notes. Over time, we have gathered valuable feedback and telemetry, but the core user workflow remains unchanged.

Starting with upcoming Nozomi Networks Operating System (N2OS) releases, we are formalizing and expanding this functionality across multiple versions, while keeping configuration simple and predictable.

N2OS 26.3.0: alert deduplication becomes a standard feature

With N2OS v26.3.0, we will no longer consider alert deduplication experimental. It will become a standard, fully supported feature that any deployment can use.

  • The feature will continue to be disabled by default
  • Users will be able to toggle alert deduplication from both N2OS and Vantage
  • Existing documentation remains valid, and no changes are required to user workflows
  • We incorporated learnings from the experimental phase into the underlying implementation, without changing how users enable or use the feature

This ensures a smooth transition for environments that are already using the experimental capability, while providing a clear and stable path for new adopters.

N2OS 26.5.0: alert deduplication enabled by default for new deployments

N2OS v26.5.0 will enable alert deduplication by default for all new deployments. This change reflects our confidence in the feature's stability and its impact on reducing alert noise and improving operator focus.

  • New installations of N2OS v26.5.0, or later, will have alert deduplication turned on by default
  • The feature will remain fully configurable and can be toggled from N2OS or Vantage, depending on the deployment
  • Existing deployments upgrading to N2OS v26.5.0 will keep their explicit configuration for alert deduplication:
    • If you explicitly enabled or disabled deduplication, N2OS will preserve that choice across the upgrade
    • If you left the configuration at its default state, it will follow the version default: disabled by default in N2OS v26.3.0 and N2OS v26.4.0, and enabled by default for new deployments starting with N2OS v26.5.0

Maintain current behavior through the transition

Because the default behavior changes with N2OS v26.5.0 for new deployments, customers who want to guarantee that their environment retains its current deduplication behavior across future upgrades should explicitly set their preferred state before moving to N2OS v26.5.0.

  • N2OS will honor explicit configuration (either enabled or disabled) across upgrades
  • If you leave alert deduplication in its default state, it will track the evolving version defaults as you upgrade

To ensure consistent behavior:

This phased approach helps ensure that new environments benefit from a more streamlined alert experience out of the box, while giving existing customers full control over when and how they adopt the new default behavior.