We have a use case to stop sending alerts for a specific application, if we there is a planned downtime for that application and we pass this downtime info to Opsgenie via JIRA ticket.
Can we configure these rules into Opsgenie and use its integration with JIRA for passing this info??
Hi @Manohar Goli (Dnfcs) If you don't want to receive alerts from these applications when there is scheduled maintenance/downtime but still want to receive other alerts for those applications in other scenarios the best way to go about this would be to use the Alert and Notification Policies in Opsgenie. I'll use Jira for this example.
From within the team that the Jira integration is assigned to, click on the policies tab.
First, set up an alert policy to add the tag "maintenance" to any low priority alert coming from Jira with the maintenance in the message. (You can adjust the parameters to make sense for your use case, this is simply what I used for the example.)
Now every alert relating to scheduled maintenance coming from Jira will automatically be assigned the tag "maintenance."
Next from Notification Policies, set it up so that every alert coming from Jira, that has the maintenance tag is automatically closed.
Hopefully this helps!
Thanks for the detailed response. This is definitely helpful. However the requirement our client is to further automate this whole scheduled maintenance for planned changes. For example, an application ( already configured for alerts on Opsgenie) that is part of a change request (jira ticket), is there a way to trigger a change (may be use web hook from JIRA to Opsgenie) to Alert profile of that particular application for that particular maintenance period (again this info is recorded on Change request (JIRA) and passed on as update to Opsgenie)
Challenge which they are trying to address is to avoid manual changes to alert profile when there is a scheduled maintenance for a specific application.
Yes @Manohar Goli (Dnfcs) Unless I'm misunderstanding your use case, you would still set up alert policies and notification policies, this way every time an alert came through related to that scheduled maintenance it would be tagged as scheduled maintenance thanks to the alert policy, and trigger an auto close thanks to the notification policy. Once it is set up, there is no manual intervention moving forward.
Meaning if Jira sends an alert to Opsgenie that scheduled maintenance is taking place, Opsgenie will add the tag maintenance automatically and then trigger the notification policy telling the alert to auto close.
You may need to adjust the tags or alert source used for your particular use case (only during the initial set up of the policy) but this is still the solution. Let me know if I'm misunderstanding your use case :)
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events