ExportXMLWordPrintable

    • Type: New Feature Request
    • Resolution: Unresolved
    • Priority: Trivial
    • 8.0.0rc2 (master)
    • Affects Version/s: 8.0.0rc1
    • Component/s: Server (S)
    • S26-W40/41
    • 2

      CEP windows can react when a PROBLEM event occurs, enters a window, is evicted, or when the window closes. However, they cannot directly react when an existing event changes from OPEN to CLOSED.

      This limits topology-based suppression. For example:

      1. An edge switch problem opens a CEP window.
      2. AP problems sharing the same topology tag enter that window and are suppressed.
      3. The edge switch recovers several hours later, while one or more APs remain down. (for example power recovers in building for switch, but not APs)
      4. The remaining AP problems should now be unsuppressed.

      The edge recovery changes the existing CEP event to CLOSED, but does not provide an execution point that can close the window. A separate CEP rule cannot handle the recovery, and it could not remove suppression owned by the original rule anyway.

      Requested functionality

      Add a CEP execution point such as When event closed or When event resolved.

      When an event contained in one or more CEP windows changes to CLOSED, the relevant rule should be able to:

      • evaluate operation conditions against the closed event;
      • execute operations such as Close window;
      • subsequently execute Window closed operations for the remaining events.

      For the topology example, an operation conditioned on role=edge could close the window when the edge event recovers. A Window closed operation from the same rule could then unsuppress every still-open AP problem.

      The recovery should not need to be represented by a new synthetic PROBLEM event.

      Expected result

      CEP can keep downstream problems suppressed for as long as the upstream problem remains open, regardless of elapsed time. When that specific upstream event closes, the rule can immediately close the corresponding window and act on the remaining downstream problems.

        1. image-2026-09-28-16-31-59-190.png
          11 kB
          Martins Orinskis
        2. image-2026-09-29-08-49-52-080.png
          38 kB
          Martins Orinskis
        3. image-2026-10-05-12-37-30-173.png
          27 kB
          Martins Orinskis
        4. image-2026-10-05-12-48-33-424.png
          16 kB
          Martins Orinskis

            Assignee:
            Sergejs Olonkins
            Reporter:
            Nathan Liefting
            Team A
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 8h 25m
                8h 25m