Uploaded image for project: 'Help-Coaches-Desk'
  1. Help-Coaches-Desk
  2. HELC-927

FIWARE.Request.Coach.INCENSe.Issue: CEP's sequence detection

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Component/s: INCENSe
    • Labels:
      None

      Description

      Hello,
      This is the second issue I had with CEP this last days.

      I'll take advantage of DoSAttack example project to explain the issue.I make two main changes to it:-One is to make ExpectedCrash event have 3 more variables. This way I can log to DoSAttackTRConsumer file the 3 values that triggered it.-Then I also change the Cardinality Policy of the Agent from Single to Unrestricted. This way the event can be triggered several times in a row, as TrafficReports come in.

      I test this result and I find it works ok. I can see in the log that the values that trigger detection are the sequence of 3 values that arrived just before the event. This, taking into account that the test beeing made on those 3 values still remains the example test: (TR3.volume>1.50* TR2.volume AND TR2.volume>1.50 * TR1.volume).
      The issue arrises if I make the test be just (TR3.volume>1.50* TR2.volume), then CEP doesn't hold TR1 correctly. Now TR1 is the same as TR2, and loses memory.
      Going a step forward I make the condition (3>2) which is always true and should trigger a detection on any event that arrives. In this case all TR1, TR2 an TR3 are the same and CEP has no memory of past values, even though the agent is of Type: Sequence.

      The desired application would be for the CEP to recieve 22 readings as a sequence of input events and analyse only the 1st, 2nd, 8th and 15th values of this sequence, at each value that enters. But I find I can't make CEP remember the values correctly unless I'm testing all of them explicitly in the Condition view-box.
      What would be the correct way to analyse the 1st, 8th and 15th values of the last 21 values that arrived, at each one that arrives?

      Appended to this email I send the sepecification JSON after all of this changes. The producer file is still the example one, unaltered, but I also send it appended.

      If you need more information let me know.

      Arthur
      _______________________________________________
      Fiware-incense-coaching mailing list
      Fiware-incense-coaching@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-incense-coaching

      [Created via e-mail received from: Arthur Vieira <arthurmvieira@hotmail.com>]

      1. AlteredDoSAttack.json
        2 kB
        FW External User
      2. DoSAttackScenarioJSON.txt
        0.1 kB
        FW External User

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          25d 16h 14m 1 Pasquale Andriani 01/Sep/15 12:28 PM
          In Progress In Progress Answered Answered
          1d 20h 46m 1 Fabiana Fournier 03/Sep/15 9:14 AM
          Answered Answered Closed Closed
          59s 1 Fabiana Fournier 03/Sep/15 9:15 AM

            People

            • Assignee:
              pandriani Pasquale Andriani
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: