We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6113

Delay initial backoff for Optimize importers

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • backend
    • 2
    • S

      When a user creates a cluster in the cloud, it can be that their first action is to create and deploy a process. By the time this is deployed, Optimize's import pipelines might have backed off up to 30 seconds (or their configurable amount), meaning that there is a somewhat unnecessary delay in the import of that first process. It would be a cleaner experience for users to be able to see that first process almost immediately.

      We should investigate whether or not it makes sense to delay back off for the first x number of minutes of operation after Optimize starts up

      ATs:

      • Importers can be configured to delay the starting of backing off
      • Documentation is updated
      • For SaaS customers, a sensible default is used

      Justification:

      Users expect data to be instantly available in Optimize in the case where there is not a backlog of data to be imported. The backoff behaviour is unclear and this will make the user's first cloud experience a bit smoother

        This is the controller panel for Smart Panels app

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

            Delay initial backoff for Optimize importers

              • Icon: Task Task
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • backend
              • 2
              • S

                When a user creates a cluster in the cloud, it can be that their first action is to create and deploy a process. By the time this is deployed, Optimize's import pipelines might have backed off up to 30 seconds (or their configurable amount), meaning that there is a somewhat unnecessary delay in the import of that first process. It would be a cleaner experience for users to be able to see that first process almost immediately.

                We should investigate whether or not it makes sense to delay back off for the first x number of minutes of operation after Optimize starts up

                ATs:

                • Importers can be configured to delay the starting of backing off
                • Documentation is updated
                • For SaaS customers, a sensible default is used

                Justification:

                Users expect data to be instantly available in Optimize in the case where there is not a backlog of data to be imported. The backoff behaviour is unclear and this will make the user's first cloud experience a bit smoother

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        joshua.windels Joshua Windels
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              joshua.windels Joshua Windels
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated: