Nick Haller Atlassian Team

Hi @Joanne Oliveira , By default, the New Relic integration will try to close an open existing Opsgenie alert based on the State: Note that screenshot above is of the Advanced tab which is only available on the Opsgenie Standard and Enterprise plans, or the JSM/O Premium and Enterprise plans. So as long as New Relic is…

Hi @Ste404 , There is an option to add No-one into an override which leaves the on-call blank - if that is what you need for on Thursday and Friday: But if you need multiple users to cover the on-call for Thursday / Friday (or another shift), you may want to add a few one-off rotations that only cover those days - since…

Hi @Ste404 , Since only one user can exist on-call in a rotation, multiple rotations would be needed for that user case (5 users on-call in the morning, and 3 users on-call in the afternoon). It might look something like this: Note you can easily clone a rotation to configure this a bit quicker by clicking the pencil icon…

Ok, well the reason the alert is sending to both Slack channels can be reviewed in my previous responses. I also included a workaround to avoid the team alert from sending to the default / global Slack integration.

Hi @John Alan , Closest thing to that functionality would be to repeat the escalation, and revert the ack'd / seen states when it repeats: Note that the repeat functionality of an escalation is NOT included in the Free and Essentials plans. Otherwise, you could also consider a notification policy that auto-restarts…

Hi @Cat Ward , That's realistically by design. Again - global Slack integrations will review ALL alerts in your Opsgenie because there is no team assigned the alert. Slack integrations assigned to a team will trigger only for the alerts sent to the same team. What exactly is the use case? Do you not want to alerts sending…

Hi @sergii_yelenski , Alert policies cannot control the creation of an alert based on the time. They are used to modify an alert such as increase the priority, add tags, add responders, etc. Closest thing to this behavior would be to configure a notification policy under your team instead. These can delay / suppress alerts…

Hi @Cat Ward , Global Slack integrations - meaning the integration is assigned to [No Team] - can apply to ALL alerts created in your Opsgenie. Team Slack integrations will only apply to alerts sent to the same team. If you want the global Slack integration to only trigger when a team is not assigned to the alert, you…

Hi @T.N. Chakravarthy , Along with what @Howard Nedd suggested, some customers will leverage an Email integration if your external system can send emails to Opsgenie. Either alternative is what most customers will use though if Opsgenie does not offer a prebuilt integration.

Thanks @Zekai Huang . We'll look into that. In the meantime, I removed the ticket number and link in your last response. I can confirm it has been received. Someone will reach out soon.

Hi @Zekai Huang , You may want to open a ticket with our support team here: https://support.atlassian.com/opsgenie/ Not sure if this is an Opsgenie or JSM query, but we can review the ticket and transfer it if needed.

Hi @Masato Kato , Please open a ticket with Opsgenie support here for assistance: https://support.atlassian.com/opsgenie

Hi @Masato Kato , Please open a ticket with Opsgenie support here for assistance: https://support.atlassian.com/opsgenie/

Hi Everyone, We have a public feature request to better define what is a Critical Alert for iOS. You can follow, watch and vote for that here: https://jira.atlassian.com/browse/OPSGENIE-134

Hi @Esteban Gomez Villa , Yes, that should be possible. You'd only want to use one AWS integration vs. multiple, and have it global - meaning it's not assigned to a team. This then opens a Responder field within each Create Alert action where you can add the three teams to be responders on the alert like so:

The Advanced tab isn't offered on the Free and Essentials plans. You'd have to upgrade to Standard or Enterprise for this functionality. To review what is/not included in each plan, check out our pricing page: https://www.atlassian.com/software/opsgenie/pricing Besides upgrading, there isn't a workaround since…

Hi @Nathan Eden , No developments as far as I know, but I've added another note to the internal ticket to ensure this is on our engineers' radar, and hopefully it is escalated soon. For reference, the internal ticket number is, HEIMDALL-7881

Hi @staci.cavalcante , Sounds like you are hoping for some form of mass notifications - which Opsgenie does not support any longer. This was an older feature, but has since been deprecated. Like you mentioned, leveraging incidents / templates might be the closest thing Opsgenie has to this functionality.

Hi @Matt Jones , It sounds like Opsgenie is adding a note when closing the alert? Hope I'm understanding that correctly. By default, the Datadog integration adds the templated message as a note when the alert is closed. You should be able to remove this, or clear a note from being added when the alert closes under the…

Hi @Nadia Marina Ramasawmy , Opsgenie does not have a display feature to show which rotation(s) a user is in besides viewing the rotation in the UI, or running some sort of GET using the API. When you click into a user from within the UI, you can view which schedule(s) they are a participant of: Then review the schedule(s)…

Hi @Joanne Oliveira , That makes sense. Alert policies can be used for this use case, but you should be able to configure this under one integration without alert policies. If you leave the integration global - meaning it is not assigned to any team - then a Responder field appears within each create alert action. Each…

Hi @Joanne Oliveira , Alerts cannot be auto-assigned to a user. A user needs to acknowledge the alert to become the Owner, or the alert can be assigned to a user as well: Sending alerts to a team through an integration or Alert policy would notify your users based on what you have configured under the team's On-call tab;…

You can query on the alerts that have tags with something like either of these using the API: tag !: null https://api.opsgenie.com/v2/alerts?query=tag%20%21%3A%20null or using a wildcard: tag: "*" https://api.opsgenie.com/v2/alerts?query=tag%3A%20%22%2A%22 The incident query isn't as robust, and does not support Null…

I converted ALX-2872 >> OPSGENIE-945. ALX-2872 was the internal feature request. Opsgenie was recently added to public feature requests like Jira, and we're slowly rolling our internal feature requests into publicly facing ones.

Hi @Agrawal Shashank , Since the Close Alert API requires an identifier to determine which alert to close, and is limited to the possible values of id, tiny and alias - it's not possible to bulk close alerts through the API. Workaround: Within the Alerts tab - create a query on these types of alerts, select multiple at a…

Hi Everyone, Just opened a public feature request for this functionality you can follow, watch and vote for here: https://jira.atlassian.com/browse/OPSGENIE-945

Hi @Ali Raza , What was the problem / issue you were encountering?

Deduplication is dependent on the alias field. You can edit what data parses here (or does not) under the integration's Advanced tab. Note this tab is only available on the standalone Opsgenie Standard and Enterprise plans, or the JSM/O Premium and Enterprise plans though.

Hi @Ian Taylor , I don't think deduplication tracking in the second instance is possible with Opsgenie << >> Opsgenie. I didn't realize initially your ask was related to this type of integration. Just did some testing on my end, and found the same results: I believe the Opsgenie integration is only designed to mirror the…

Hi @Ian Taylor , "However on receipt of further alerts with a matching alias the count is increasing on the primary account but not the secondary." - If the secondary instance is not deduplicating, then what exactly is happening? If the alerts are not deduplicating, I'd have to assume: 1 - The secondary instance is…