Nick Haller Atlassian Team

Hi @Kimi Nakashima , To re-notify users you can configure a Notification Policy under the team receiving these alerts. Notification policies can be used to restart the notification process for any open alerts after x-time. If the alert gets closed before the time configured, the policy will not apply / restart…

That's correct! The alert would still be created, but notifications would not be sent to users until the count of the alert hits a deduplication of x2. 

Hi @Alexander Developer , I'm not entirely sure what button you are looking for, but I believe you are referring to the option to Create or Link Issues within an alert. Those options should appear here in an alert after you link your account: When searching that doc for "button" - the only other thing I can think of is the…

Hi @dhiman.das , I was able to test and confirm the "invitationDisabled" should work as expected - I was able to invite users via API and not have invitations send. The syntax would look something like this: {"username": "xyz123@opsgenie.com","fullName": "john doe","invitationDisabled": "false","role": {"name": "Admin"…

Hi @Ben Gardella , Like @[deleted] mentioned, we see most customers adding a Notification Policy that is configured to restart notifications after X-time following when the alert was created: https://docs.opsgenie.com/docs/team-policies#notification-policy These can be configured under a team's Policies tab and would look…

Hi @Steve Wareham ! This is possible with Notification Policies: https://docs.opsgenie.com/docs/team-policies#notification-policy Notification Policies can be added under a team's Policies tab, and can be configured to do exactly this; delay notifications unless the deduplication count is greater than one (or another…

Hi @Jose_Martin , Thanks for reaching out. This similar community post may help with your issue: https://community.atlassian.com/t5/Opsgenie-questions/Mapping-alert-values-from-Solarwinds/qaq-p/1327612 ^ Although related to Solarwinds, the concept is the same. AWS's priority might vary from Opsgenie's so it will not map…

Hi @Vladimir Blando , Are you able to check your account's logs under the Settings tab -> Debug section to see if Opsgenie is receiving any warning / error requests? The requests from Prometheus might not be matching some conditions in order to create alerts. You should be able to adjust what's configured in Alert Manager…

Hi @Contact IT , Glad the issue_updated solved the initial problem! As for your Webhook - it does not look like your JQL accounts for the ticket being reopened; triggering the Webhook when this action is taken on the alert. Which is most likely why you cannot find any logs in Opsgenie since we're not receiving anything…

Hi @Contact IT , Sounds like the Jira ticket is transitioned to Blocker after it is created - so instead of the condition being; Event Equals jira:issue_created -> it should be Event Equals jira:issue_updated Below is an example of a log that shows the priority being increased after the ticket is created, and the event…

Hi @Lukasz Kaminski , "Alert de-duplication is one of the key features that Opsgenie provides to help reducing the number of alerts and to prevent alert fatigue. Because monitoring systems can be quite 'chatty' by sending many events for the same problem and having to manage many alerts that were raised for the same or…

Hi @Mark Skrzypczyk ! Thanks for reaching out. At this time Opsgenie > JSD does not have this functionality out-of-the-box. We do have an open feature request that I can certainly add you to though. In the meantime - the workaround requires a few steps in both Opsgenie and JSD. In Opsgenie - you will want to create an…

Of course! Please let us know if you happen to run into any other questions or issues. Best, Nick

Hi @Derek Stevenson The best place to troubleshoot Opsgenie > JSD is in the alert's Activity Logs, as well in the Logs found under Settings > Debug. The Activity Logs only show the response such as a 400, 401, etc. - but the debug Logs will provide more details to the error. Typically SSO issues are related to a 401 or 403…

Hi Andrii, Thanks again for your time just now via in-app chat! Glad we could sort this out. For others that might face the same/similar problem - there were a few steps to troubleshoot and resolve this issue. In order for the Integration's Close Alert action to apply, two things must match; 1) The filter conditions of…

Hi Andrii, Thanks for providing those. I'd need to take a deeper look at some other logs and your account to really make an assessment. I just sent you a message through our in-app chat tool that can be found at the bottom-right corner of the screen: If you do not see this - it's most likely due to an ad-blocker. If…

Hi Andrii, It looks like you have added another condition in those actions along with what the default filters are; Create action default filter: Event Type = create Close action default filter: Event Type = close Not to say addition conditions can't be done, but have you tried testing with the default filters? Without…

Hi Andrii, That would be dependent on what dynamic field the hostname is being parsed in on the integration. You can drag and drop these fields to specify what the alias will be in the different actions such as Create or Close: If the hostname is not parsing in any of these provided fields, but is parsed in the payload of…

Hi Scott, Like you mentioned, Solarwind severities typically do not match to Opsgenie priorities out-of-the-box. So we see most customers mapping Severity -> Priority on the integration level. Under the Advanced section of the integration, you can filter on the data being sent from SW (such as the severity) and map to the…

Hi Nic, You'd want to configure a Notification Policy that suppresses the notifications for this entity/types of alerts. Within the policy, filter on the field that the entity is parsed through (most likely the Entity) -> then have the Maintenance window enable this policy when either scheduled or started:

Hi Andrea, Yes! The best way to do this is with Central Notification Templates: https://docs.opsgenie.com/docs/central-notification-templates CNTs provide the ability to define shared notification settings that are managed from a single place, and can be assigned to user(s) account roles. They standardize notification…

Will do! No updates on this ticket yet, but I've added you to the ticket in case anything develops.

Welcome! Please let us know if you run into any other questions or issues. And if you decide to move forward with trialing Opsgenie, we offer an in-app live chat bubble that my team and I can help with.

I'm personally not familiar with PD's time-based grouping feature, but within an Opsgenie service's incident rule - multiple matching rules (and/or conditions) can be defined to associate alerts into one incident. This does not have time-based functionality since it's all dependent on an ongoing incident, so the filter…

Hi Andreas, Opsgenie does have alert correlation that acts in a similar fashion: https://docs.opsgenie.com/v1.0/docs/correlate-alerts-with-incident-1 Essentially if you have an ongoing service disruption (with your Fibre Network), alerts can be associated to an incident during the window its open - and group to the 'same…

Unfortunately not at this time, but we do have an open feature request for this that I have added you to. Our tickets are not public, so I'll reach out directly with any updates/developments on the ticket. And if you'd like to contact support for an update yourself, the ticket for reference is ALX-818; Add recurring time…

Hi Daniel - thanks for the feedback. You can alternatively suppress the notifications of an integration (found under Settings -> Configured integrations OR a team's Integration tab) - but will need to remember to turn this option back on after the fact:

You can use this option (Custom Value to Opsgenie Priority) with other webhook-based integrations. Unfortunately it does not work with our API integrations such as Prometheus. Prometheus is an integration that sends notifications through our API (https://prometheus.io/docs/alerting/configuration/#opsgenie_config) and due…

It's not an option (unless you are seeing something else with your integration): Prometheus is using an API key to post to Opsgenie and because of this, looking for the values that are priority is (P1-5).

I'm realizing Prometheus unfortunately is not an integration that can have a custom value to Opsgenie property configured such as a value {{severity.substring(0,2)}}: So the best option is mapping this on the Alert Manager side like shown above. We also see customers using Alert Policies to parsed for the severity field,…