Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1111 I can receive import progress over WebSocket connection
  3. OPT-1132

Progress Report bar is based on web socket

XMLWordPrintable

    • Icon: Feature Part Feature Part
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.0.0
    • None
    • frontend
    • None

      • given
        • status websocket available on ws://localhost:8090/ws/status
      • when
        • I login to optimize
      • then
        • I see import progress report based on websocket connection

        This is the controller panel for Smart Panels app

            [OPT-1132] Progress Report bar is based on web socket

            Johannes added a comment -

            sebastian.stamm: You can now start with the ticket. The endpoint is documented here: https://github.com/camunda/camunda-optimize/wiki/WebSockets-API-documentation

            Johannes added a comment - sebastian.stamm : You can now start with the ticket. The endpoint is documented here: https://github.com/camunda/camunda-optimize/wiki/WebSockets-API-documentation

            Johannes added a comment - - edited

            The code itself looks good, but:

            • when the engine crashes, the engine connection icon is not shown at all and the Elasticsearch icon still indicates that it is connected. Expected: both should be red as the status is coming from the engine and we do not know if Elasticsearch is still up. -> Sebastian and I talked about it and decided that this case is very unlikely to ever occur. So we decided to omit that issue for now
            • also the ticket description could contain some acceptance tests to know what is the expected behavior. -> Sebastian promised to adjust that the next time

            Johannes added a comment - - edited The code itself looks good, but: when the engine crashes, the engine connection icon is not shown at all and the Elasticsearch icon still indicates that it is connected. Expected: both should be red as the status is coming from the engine and we do not know if Elasticsearch is still up. -> Sebastian and I talked about it and decided that this case is very unlikely to ever occur. So we decided to omit that issue for now also the ticket description could contain some acceptance tests to know what is the expected behavior. -> Sebastian promised to adjust that the next time

              Unassigned Unassigned
              askar.akhmerov Askar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: