Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-4175

Too frequent engine/version rest calls caused by status websocket updates

XMLWordPrintable

      Context:
      Every status websocket update (triggered by an importStatus change of any configured engine) currently causes a REST API call to the engine on `/version` to verify the engine is available. This call is triggered by every status update connection and thus causes an unnecessary amount of such requests only limited by the number of allowed websocket connections import.data.decision-instance.maxPageSize. See linked support ticket.

      AT:

      • the engine status is either updated in regular intervals or indirectly through the import activity and stored
      • the status websocket update relies on the stored status rather than triggering individual checks for every single connection

        This is the controller panel for Smart Panels app

            [OPT-4175] Too frequent engine/version rest calls caused by status websocket updates

            Sebastian Bathke added a comment - - edited

            The frequency will be mitigated already by OPT-4273 which has a reduced scope.

            Sebastian Bathke added a comment - - edited The frequency will be mitigated already by OPT-4273 which has a reduced scope.

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: