Reduce latency of asynchronous JSM incident provisioning so incident features (responders / linked alerts) become available faster

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • Component/s: Operations - Sync
    • None
    • 0
    • 1

      *Current Problem*
      When a JSM incident is created (natively or via Jira Automation / operations sync), the connection to Opsgenie (provisioning) runs asynchronously in the background. As a result, incident features such as Responders and Linked alerts are not available for the first few minutes after creation. During the early stage of incident response, this waiting time is an operational pain point. There is no customer-side setting to speed this up.

      *Suggested Solution*
      Speed up the provisioning pipeline that runs at incident creation time, and shorten or eliminate the lag before incident features (responders / linked alerts) become available.

      *Workaround*
      No workaround exists that shortens the underlying wait time. Pressing "Update incident" manually may re-check the provisioning state, but it does not speed up the asynchronous processing itself.

              Assignee:
              Unassigned
              Reporter:
              Jun Itokawa
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: