Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,444
Community Members
 
Community Events
176
Community Groups

Route New Relic Alerts to On Call

Hello,

I have set up an integration in OpsGenie and New Relic.
Currently the integration in OpsGenie receives both Critical and Moderate alerts into the OpsGenie integration from New Relic

Is there a way that I can configure OpsGenie so that only Critical alerts from New Relic go to our on call engineer from 5pm to 08.30am?
And then both critical and moderate alerts go to the whole team from 08.30am to 5pm?

 

Thanks

1 answer

1 accepted

1 vote
Answer accepted
Nick H Atlassian Team Jan 19, 2023

Hi @Paul Donnelly ,

That should be possible. You'd first want to extract the field(s) that determines these alerts are critical or moderate - whether it's a tag, custom field, etc.

After, you could use routing rules to filter on the alert field determining if these alerts are critical or moderate, and route to a specific escalation depending on the time of day.

For example:

rr1.jpg

rr2.jpg

 

^ If an alert is created and matches the filter / time restrictions of the top routing rule, alerts will be routed to the After Hours escalation - which only notifies the on-call user(s).

If an alert is created and does not match the filter / time restrictions of the top routing rule, the default routing rule (ELSE) will route alerts to the Business Hours escalation - which notifies all members of the team.

Thanks @Nick H  I worked out that part eventually :-) 

Just one thing I'm not sure of is this messageRoute alert.PNG

Does this mean that when I have my on call route setup for P1 issues, OpsGenie will now ignore any other escalation polices I have?
For example I have a policy that has alerts 08.30am to 5pm? I need the P1 issues to notify the team during these hours

 

Thanks

Nick H Atlassian Team Jan 19, 2023

Hi @Paul Donnelly ,

That's a warning to inform customers an escalation is not apart of the workflow with the routing rule. Routing alerts directly to a schedule will essentially skip over the escalation(s) entirely. If the use case were to notify others if the on-call user(s) do not take action, then you'd want to route to an escalation.

But with your use case to only notify the on-call user(s) for critical after hours alerts, then you can leave it as is! You realistically do not need an escalation for that routing rule.

@Nick H excellent thanks!

 

Just one more thing. I've now set up my on call route to notify the on call engineer based on the days/times shown. Alerts are then routed to the on call schedule (which contains information about who is on call and when)

I'm seeing an information message as shown. Is this OK? I couldn't see it on your setup

alerts.PNG

Nick H Atlassian Team Jan 19, 2023

Hi @Paul Donnelly ,

If I were to edit my routing rule to send alerts directly to the team's schedule instead of an escalation, I'd have the same UI / warning:

rr3.jpg

 

It's the same warning from your other response, but a different view.

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events