Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-6013

FIWARE.Request.Tech.Data.CEP.Debugging CEP and CEP-Orion connection

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Hi!

      I’m Iván, from Encore Lab, one of the FI-C3 startups.

      We’re having trouble with the CEP generic enabler. Right now our devices
      send all its data to the ORION platform, and the ORION redirects the
      submitted data to the CEP using some subscriptions. Then we have created a
      new project in CEP in order to try to detect patterns for our seizure
      detection system. But at this step we are having some issues to configure
      the CEP tool, which we don’t know if it’s receiving the events properly or
      if the rules we’ve configured are not correct.

      In order to see what’s working it would be useful to see the CEP’s inner
      status. Is there any tool that allow us to debug the CEP application, or at
      least see if it is receiving and processing the events with no errors and
      which rules are being applied?

      Another question: Is there any more information to read about CEP and its
      connection to ORION? Maybe some examples where it’s showed the connection
      between them can be useful for us. We have seen some videos but its
      explanations are not enough… We’re really having lots of issues and errors
      while configuring the CEP.

      Thank you so much. Kind regards,

      Iván Pérez
      Encore Lab, S.L.
      Av. Zaragoza 18 - 1º Oficina 2
      26006 Logroño (La Rioja)
      Tel.: +34 941 273 376
      <http://www.encore-lab.com/> www.encore-lab.com

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-fic3-coaching@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-fic3-coaching mailing list
      Fiware-fic3-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-fic3-coaching
      [Created via e-mail received from: =?iso-8859-1?B?SXbhbiBQ6XJleg==?= <ivan@encore-lab.com>]

        Issue Links

          Activity

          Hide
          urishani Uri Shani added a comment -

          Hello Ivan,
          There is a standing issue in connecting with ORION with PROTON CEP due to change in the message format from XML to JSON. Therefore, new revisions of ORION will not connect.
          You need to use ORION version which works with XML format messages.
          So, is that the case here?

          Thanks,

          • Uri

          Related help request: https://jira.fiware.org/browse/HELC-1289

          Show
          urishani Uri Shani added a comment - Hello Ivan, There is a standing issue in connecting with ORION with PROTON CEP due to change in the message format from XML to JSON. Therefore, new revisions of ORION will not connect. You need to use ORION version which works with XML format messages. So, is that the case here? Thanks, Uri Related help request: https://jira.fiware.org/browse/HELC-1289
          Hide
          fw.ext.user FW External User added a comment -

          Hello,

          At the moment I'm using ORION 0.28 (I've updated from 0.27 this week, and no problems with ORION so far). As far as I know the current version would be the last supporting XML, so this case might not be the conflicting formats.

          Thanks


          Iván Pérez
          Encore Lab, S.L.
          Av. Zaragoza 18 - 1º Oficina 2
          26006 Logroño (La Rioja)
          Tel.: +34 941 273 376
          www.encore-lab.com

          ----Mensaje original----
          De: Help-Desk jira-help-desk@fi-ware.org
          Enviado el: miércoles, 02 de marzo de 2016 11:00
          Para: javier.romero@atos.net; ext_user@fi-ware.org; ivan@encore-lab.com
          CC: INNA@il.ibm.com
          Asunto: [FIWARE-JIRA] (HELP-6013) [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection

          Hello Ivan,
          There is a standing issue in connecting with ORION with PROTON CEP due to change in the message format from XML to JSON. Therefore, new revisions of ORION will not connect.
          You need to use ORION version which works with XML format messages.
          So, is that the case here?

          Thanks,

          • Uri

          Related help request: https://jira.fiware.org/browse/HELC-1289

          -------------------------------------------------------------------------------
          Uri Shani created HELP-6013:
          -------------------------------

          Summary: [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection
          Key: HELP-6013
          URL:
          Project: Help-Desk
          Issue Type: extRequest
          Components: FIWARE-TECH-HELP
          Reporter: FW External User

          This email was generated by the FIWARE JIRA (http://jira.fiware.org).

          Show
          fw.ext.user FW External User added a comment - Hello, At the moment I'm using ORION 0.28 (I've updated from 0.27 this week, and no problems with ORION so far). As far as I know the current version would be the last supporting XML, so this case might not be the conflicting formats. Thanks – Iván Pérez Encore Lab, S.L. Av. Zaragoza 18 - 1º Oficina 2 26006 Logroño (La Rioja) Tel.: +34 941 273 376 www.encore-lab.com ---- Mensaje original ---- De: Help-Desk jira-help-desk@fi-ware.org Enviado el: miércoles, 02 de marzo de 2016 11:00 Para: javier.romero@atos.net; ext_user@fi-ware.org; ivan@encore-lab.com CC: INNA@il.ibm.com Asunto: [FIWARE-JIRA] ( HELP-6013 ) [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection Hello Ivan, There is a standing issue in connecting with ORION with PROTON CEP due to change in the message format from XML to JSON. Therefore, new revisions of ORION will not connect. You need to use ORION version which works with XML format messages. So, is that the case here? Thanks, Uri Related help request: https://jira.fiware.org/browse/HELC-1289 ------------------------------------------------------------------------------- Uri Shani created HELP-6013 : ------------------------------- Summary: [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection Key: HELP-6013 URL: Project: Help-Desk Issue Type: extRequest Components: FIWARE-TECH-HELP Reporter: FW External User This email was generated by the FIWARE JIRA ( http://jira.fiware.org ).
          Hide
          urishani Uri Shani added a comment -

          Hi Ivan, here is more info from our experts (Assuming you work with the XML messaging format):

          1. To get information re connecting CEP to ORION etc you can look here: https://github.com/ishkin/Proton/blob/master/documentation/ProtonUserGuidev4.4.1.pdf. This is the CEP User guide , from page 40 there are instructions and example on how to connect to ORION context broker.
          2. We have no tooling allowing to inspect CEP internal state, however there are couple of things which should be verified:
            1. First of all the application syntactic correctness. This can be verified by authoring the application in CEP AuthoringTool and clicking on "Verify" button. There should be no errors reported.
            2. Another thing to make sure the application is up and running is to test its state via REST: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification, under Administrating Instances section there is information how to retrieve instance state
            3. And finally, for debugging the application I would suggest creating a file consumer (basically making Proton to write output events to a file ) in the application definitions JSON, examples on how to do that can be found in the user guide. When specifying the events which should be forwarded to the consumer I would suggest specifying the row input event as well. If this event gets written to the output file and the derived events are not, that means there is something wrong with the application logic. On the other hand, if this event is not delivered to the output file that means something is wrong with the configuration between CEP and Orion, and events are not being delivered to CEP.

          Hope this helps.

          Show
          urishani Uri Shani added a comment - Hi Ivan, here is more info from our experts (Assuming you work with the XML messaging format): To get information re connecting CEP to ORION etc you can look here: https://github.com/ishkin/Proton/blob/master/documentation/ProtonUserGuidev4.4.1.pdf . This is the CEP User guide , from page 40 there are instructions and example on how to connect to ORION context broker. We have no tooling allowing to inspect CEP internal state, however there are couple of things which should be verified: First of all the application syntactic correctness. This can be verified by authoring the application in CEP AuthoringTool and clicking on "Verify" button. There should be no errors reported. Another thing to make sure the application is up and running is to test its state via REST: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Complex_Event_Processing_Open_RESTful_API_Specification , under Administrating Instances section there is information how to retrieve instance state And finally, for debugging the application I would suggest creating a file consumer (basically making Proton to write output events to a file ) in the application definitions JSON, examples on how to do that can be found in the user guide. When specifying the events which should be forwarded to the consumer I would suggest specifying the row input event as well. If this event gets written to the output file and the derived events are not, that means there is something wrong with the application logic. On the other hand, if this event is not delivered to the output file that means something is wrong with the configuration between CEP and Orion, and events are not being delivered to CEP. Hope this helps.
          Hide
          flegall Franck Le Gall added a comment -

          Hi

          Can the issue be closed ?

          Thank you
          Franck

          Show
          flegall Franck Le Gall added a comment - Hi Can the issue be closed ? Thank you Franck
          Hide
          urishani Uri Shani added a comment -

          I suppose, yes. No further info from user thus far.
          Will close.

          Show
          urishani Uri Shani added a comment - I suppose, yes. No further info from user thus far. Will close.
          Hide
          flegall Franck Le Gall added a comment -

          Ok. Thank you

          ----Message d'origine----
          De : Uri Shani (JIRA) jira-help-desk@fi-ware.org
          Envoyé : mardi 8 mars 2016 21:46
          À : Franck Le Gall <franck.le-gall@eglobalmark.com>
          Objet : [FIWARE-JIRA] (HELP-6013) [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection

          [ https://jira.fiware.org/browse/HELP-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41230#comment-41230 ]

          Uri Shani commented on HELP-6013:
          ---------------------------------

          I suppose, yes. No further info from user thus far.
          Will close.


          This message was sent by Atlassian JIRA
          (v6.4.1#64016)

          Show
          flegall Franck Le Gall added a comment - Ok. Thank you ---- Message d'origine ---- De : Uri Shani (JIRA) jira-help-desk@fi-ware.org Envoyé : mardi 8 mars 2016 21:46 À : Franck Le Gall <franck.le-gall@eglobalmark.com> Objet : [FIWARE-JIRA] ( HELP-6013 ) [Fiware-fic3-coaching] Debugging CEP and CEP-Orion connection [ https://jira.fiware.org/browse/HELP-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41230#comment-41230 ] Uri Shani commented on HELP-6013 : --------------------------------- I suppose, yes. No further info from user thus far. Will close. – This message was sent by Atlassian JIRA (v6.4.1#64016)

            People

            • Assignee:
              urishani Uri Shani
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: