nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpsGenie Integration to Jira - surppress P3-P5 alerts during night hours.

Theis Joergensen

Hi Community,

I have an exiting use-case which i cannot figure out how to setup in OpsGenie

Currently i have 5 integrations creating alerts via a webhook to Jira. A C1 ticket in Jira generate a P1 in Opsgenie, C2 generate P2 and so forth.

During normal working hours (07.30-15.30) alerts are routed to our operations team, outside these hours alerts are routed to our monitoring assistants team.

Its working as expected and has been sufficient since launch. Now we have started 24/7 support and i need an option to add an additional rule.

From 24.00-06.00, i would like OpsGenie only triggers notifications for P1 and P2, and not P3-P5 as it is normally.

I have checked integration in OpsGenie and webhook in Jira to see if i could automatically disable P3-P5 integrations in this timespan but it doesn't seem to be possible.

Anyone who have resolved this issue, or have an idea i can try?

Thanks in advance.

Accepted answers

Nick Haller

Hi @Theis Joergensen ,

Notification policies should be able to help with the addition to this use case. You can delay / suppress notifications for after hours alerts that are P3-5.

Note that notification policies are only included in the Standard and Enterprise plans though. It might look something like this:

All comments

Nick Haller

Hi @Theis Joergensen ,

Notification policies should be able to help with the addition to this use case. You can delay / suppress notifications for after hours alerts that are P3-5.

Note that notification policies are only included in the Standard and Enterprise plans though. It might look something like this:

Theis Joergensen

@Nick Haller Thanks for the swift reply.

Unfortunately we only have the essentials plan.

Looking at the routing rule video, it seems that this might also be possible using multiple routing rules? However, it seems like it's only possible to create one per team when having the essential plan, is this correct?

Stefan Draber_kwaltd

Hi @Theis Joergensen , that's correct, here you get an overview about all Essential plan limitations: https://support.atlassian.com/opsgenie/docs/which-features-are-not-available-in-the-essentials-plan/#Routing-and-escalation-rules

Theis Joergensen

@Stefan Draber Thanks, Stefan.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

opsgenie