-
Suggestion
-
Resolution: Unresolved
-
None
User Problem
In the current design, the JSM integration is only for Opsgenie Alerts and JSM issues syncing. However, the term, Incident, exists on both products for the similar objective, it makes more sense to have the synchronization between them.
Suggested Solutions
Please consider building the synchronization between the Incidents on JSM and Opsgenie, without further configurations with the Incident Rules and the Responder Alerts.
Current Workarounds
For JSM to Opsgenie
- Complete the JSM Cloud integration.
- Set up the Incident Rules on the associated teams to match the JSM issues that are created in the "Incident" Issue Type.
In this way, whenever a JSM Incident is created, an Opsgenie Alert and an Opsgenie Incident will be generated automatically.
For Opsgenie to JSM
- Configure the Action Filter on the JSM Cloud integration to only post the Responder Alerts, which are created by the Opsgenie Incident for the associated teams, to create an JSM issue in the "Incident" Issue Type.
In this way, whenever an Opsgenie Incident is created, Opsgenie will create the Responder Alert to the team who is listed as a Responder Team, and Opsgenie will post this alert data to create a JSM Incident accordingly.
- is related to
-
OPSGENIE-67 Ability to to integrate Opsgenie Incidents with external systems
- Reviewing
-
JSDCLOUD-14539 Populate linked alerts field on JSM incident when alert is created through operations syncs /Responders alert
- Under Consideration
Hi Support,
Indeed this is a "basic" feature that would be highly useful for our NOC to avoid multiple "click". Currently they manually create incidents into OpsGenie, link all alerts to this incidents and do the exact same thing within JSM. The main goal here would be to create a JSM ticket directly from OpsGenie with all mandatory information coming from monitoring in OpsGenie and sync it in realtime.
Thank you