Nick Haller Atlassian Team

Feel free to also open a ticket with our support team here: https://support.atlassian.com/opsgenie/ I noticed you blurred some of the above screenshot so if you needed to keep this private, we can take a look at things behind the scenes.

Hi @[deleted] , If this notification policy is consistent, and should always apply M-F 07:30-16:30, then I don't think enabling this via a maintenance policy is needed. You should be able to simply just keep the notification policy enabled at all times. Regardless, what exactly is not working as expected? Is the…

No I don't believe there is a way to do that; export a list of Opsgenie alerts and import them into Jira as issues.

Hi @ssllumiquinga , That error is more related to the integration, and the issue type not being recognized by Opsgenie. If you have not already configured this part of the integration, you'll need to configure these fields: The top of the other Community post shared above should provide more info into that: Opsgenie Alerts…

This write up as well should help troubleshooting the issue: Opsgenie Alerts Not Creating Jira / Jira Service Management Issues

Hi @ssllumiquinga , You'd first want to check the alert's activity log to see if there are any errors: Typically if no issue is being created, there will be some 400 error that might better explain why the alert is not creating an issue. If there is an activity log that shows, "Sent [createIssue] action to Jira" but no…

Yes - adjust the condition(s) and what's being filtered on in your Low Alert create alert action: Whatever is defined here is matching on your Lowest JSM Issues. If your actions are configured like this; JSM "Low" issues should map to P4 Opsgenie alerts, and JSM "Lowest" issues should map to P5 Opsgenie alerts: You Lowest…

Right, but the P5s / Lowest JSM issues are matching on this create alert action: For context, these actions are processed top >> down in an order of operations. Opsgenie will review the top action, and if Opsgenie does not match the action's filter/conditions, look at the next action(s) until a match is made. So it seems…

Hi @Marlon Silva , Is your P4 create alert action mapping to the Priority Contains "Low" by chance? If yes - then my guess is the P5s (Lowest) are matching on that condition - since it would contain "Low." And if that's the case, then you may want to change the P4 create alert action mapping to the Priority Equals "Low."…

Hi @heidi_rechek , If possible, I'd suggest reviewing the payload being received by Opsgenie under the Settings menu >> Logs tab - to see what is/not matching with those fields. You also could use a regex condition that could look something this one that's simply looking for "oms" regardless of case…

Apologies, with the JSM integration it would be: Webhook Event Equals jira:issue_created

Great! One suggestion would be to add an additional condition in your Critical Priority create alert action: Event Equals jira:issue_created: Otherwise any request sent from JSM to Opsgenie for the same issue will probably match this existing create alert action. The updates on the issue would then be deduplicated since…

Based on the create alert actions you shared, the JSM issue is matching the action AFTER your configured action - meaning that the issue being created in NOT matching on the conditions defined in the Critical Priority create alert action: So you'd want to review the Logs tab of what's being parsed in the payload to ensure…

Hi @Marlon Silva , If possible, please check the alert's activity log to see which create alert action is being used: Important to note these actions are processed top > down, and Opsgenie will use the first matching create alert action it finds. If there's a create alert action being used before the one you expected, then…

Hi @Cindy , You'd have to upgrade your plan to get the global Integrations tab. This is only available on the Standard and Enterprise plans, along with the Advanced tab of the integration mentioned at the top of this thread.

Hi @robin Dexter , Looks like the Severity of your JSM issues might be a custom field being sent from JSM >> Opsgenie. If that's the case, and the values of the Severity field are P1 to P4, you should be able to map these to Opsgenie priorities using the Custom Value to Opsgenie Priority option in the integration: The…

Hi @Rahul Laad , If your DL can forward emails to an Opsgenie Email integration, then this should be possible. The Email integration is very simple; anytime an email is sent to the integration's address, an alert can be created. If you want to fine-tune the integration to only have certain emails create Opsgenie alerts,…

Hi @Brent Landon , Sounds like your plan might be limited to this functionality. Under the Standard and Enterprise plans, each integration offers an Advanced tab where you can filter on the subject, along with what should/not trigger an Opsgenie alert: If your Opsgenie is under trial, Owners can upgrade the trial for free…

My colleague just opened the public feature request that can be followed here: https://jira.atlassian.com/browse/OPSGENIE-391 Looks like you already found that through another…

Hi @Andrew Parker , It's not possible to notify users via voice notification for their Incoming Call notification rule. This is by design to avoid confusion if the integration has the option, "Notify when a call comes in, only if it is not answered in 0 minutes" option. Otherwise users could get a voice notification, along…

Thanks for clarifying. Yes - that's exactly what would happen. Regardless of whether the alert is closed manually, through the API, the integration, etc. - users would stop being notified once the alert is closed.

Hi @Piyush Rathod , You can use string processing or regex to extract those specific fields. I believe you should be able to use: {{ description.substringBetween("alertname =","-") }} {{ description.substringBetween("env =","-") }} {{ description.substringBetween("description =","-") }} to pull those values.

Hi @Rowell , Seems like you could leverage an Email Integration to connect InsightIDR with Opsgenie, and have these emails from InsightIDR create alerts in Opsgenie. Then have Opsgenie sit between Rapid7 and JSM to create issues from these alerts. Within the JSM integration, you should be able to specify which types of…

Hi @Heather Brown , The issue key can be defined in the integration's Advanced tab. The data parsed as the issue key will also parse as the dynamic alias field with the Jira and JSM integrations: Best practice is to leave the dynamic alias parsing in the alias field of all integration actions, and have the issue key…

Hi @Manikranth V Bheemineni , Then I believe OEC would be required with your instance, and that checkbox would need to be selected. With this, you would install the OEC service on a server (typically on the JSM server), and it will sit in the middle of Opsgenie and JSM. Opsgenie alerts would send to OEC, which will then…

Hi @shenningsgard , Atlassian site roles don't always correlate one-to-one with Opsgenie roles - so my guess is you might be a User in Opsgenie even though you are a site admin. You'd realistically have to manage Opsgenie roles within Opsgenie specifically - while the Atlassian site can manage which user(s) have access to…

Hi @Carlos Sanchez , That's correct - "escalation policies allow to send notification based on the alert generated only and not the issue priority." But routing rules can filter on the alert's priority, or the priority being sent from Jira (as long as it's being parsed in an Opsgenie alert field), and send each specific…

Hi @[deleted] , You could map the Opsgenie integration to add a comment to the issue when the alert is closed: The text added in the comment will be something like this: [Opsgenie]: Nicholas Haller closed alert: "Network Connectivity Issues" https://opsg.in/a/t So you could add an automation rule that filters on the…

Hi @Lukasz Kaminski Under the ServiceNow integration's Advanced tab, you should be able to control which SN incidents do/not create alerts. You'd realistically just want to delete the Create Alert action so nothing triggers the creation of an alert: Note this tab is only available on the Opsgenie Standard and Enterprise…

Hi @Alex Radnaev , Is that log from Outlook specifically? I'm wondering if that might be some restriction within your email provider? I just tested with forwarding a personal email to an Email Integration with no problem. Granted this test was done through Gmail, Opsgenie should be able to receive forwarded emails: