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,553,439
Community Members
 
Community Events
184
Community Groups

Only perform close action on OEC when action is triggered by user

Marius.Myrbakk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 25, 2023

We have a two way integration with our monitoring system that closes alerts in opsgenie when the alarm is cleared and we also have OEC installed to clear the alarm in the monitoring system if the corresponding alert in opsgenie is closed.

However we do not want OEC to perform a close action if the alarm is already cleared in our monitoring system, only if the alert is closed by a user in opsgenie while the alarm is still active.

 

I've tried solving this using Alert Filter in OEC settings and matching the condition Details (key/value) username NOT Contains Alert API

oecfilter.png

as I noticed in the logs that the payload for all alarms not manually closed by a user contained "username":"Alert API"

 

This did unfortunatly not work and I see close actions are still executed.

 

This does not have any service impact as the close action on allready closed alarms are ignored by the monitoring system, but it is spamming our logs.

 

Is this possible to solve in opsgenie configuration or do I need to add a function in the close-script in OEC?

1 answer

0 votes
Marius.Myrbakk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 25, 2023

Another option could be for the integration that closes the Alert to add a tag and then filter on that tag in the OEC action filter, but I would still like to know if there is a way of doing it in Opsgenie with the information that is already there.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events