Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-1622

Opsgenie and accessing custom Atlassian Assets object schemas

XMLWordPrintable

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Problem

      Opsgenie is heavily relying on the Services Object Schema in Assets.

      Services schema is somewhat limited in its content, and customer requires some additional flexibility in enriching OpsGenie alerts upon arrival with some additional information stored in other Assets object schemas (which they have developed for their org).

      An example of enrichment would be adding custom tags and attributes to the alerts driven by that custom schema, allowing customers to implement better logic in assigning these alerts to the responders.

      Suggested Solutions

      To have a native way of accessing other (non-Service) object schema in assets from Opsgenie, where Opsgenie is to query the assets, grab the additional details required, and add those to the alert.

      Current Workarounds

      1. Once the alert is in Opsgenie, the webhook integration will call a Jira webhook for the
      "If the is created" then "post to URL in Webhook" condition.

      2. Jira webhook destination is provided by the Jira automation, which would be triggered once the Incoming webhook request is detected

      3. That automation will grab the Opsgenie alert payload, parse it, query the custom asset object schema, and, via OG restful APIs, enrich the original alert.

      The approach above is workable but somewhat complex

              Unassigned Unassigned
              eguzun@atlassian.com Egor (Inactive)
              Votes:
              38 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: