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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Rest API integration close alert based on alias

Hi there,

I'm trying to replicate similar behaviour to this question behaviour, but in the case using the REST API integration, using the following settings

message sample (ERROR): [Product Environment] A-Service: ERROR

message sample (SUCCESS):  [Product Environment] A-Service: SUCCESS


Screenshot 2021-09-22 at 21.56.27.pngScreenshot 2021-09-22 at 21.56.49.png


The idea is to create an alert with message contains ERROR, 

Close the error alert with same alias when new message contains SUCCESS


Creation on ERROR works fine, but for SUCCESS message it logs "Can not execute alert action. Incoming data does not match any actions." and alias in this case is empty "" + and previous ERROR alert remains open of course.

Any advice/hints on what I'm doing wrong ? See attached screenshots.

Thanks in advance.


2 answers

1 accepted

1 vote
Answer accepted
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 22, 2021

Hi @Charalampos Kailantzis ,

I believe your issue is be due to the Rest API using a different URL or endpoint to close and alert vs. creating one:

And what I believe is happening is the request being sent Opsgenie is probably using the URL to create an alert - so that error in the logs would make sense with no matching action found in the Create Alert action.

The URL needed to close the alert might be something like:

or one of the other options we have available to close an alert through the API. Here's a test as well for example through Postman:



Hope that helps! Let us know if you have any other questions.

Checking now the logs more carefully:

  • alias [Product Environment] A-Service
  • message [Product Environment] A-Service: ERROR

any idea why the message still contains "ERROR", when in the body I have "SUCCESS". ??. Or I'm missing something ? I'm also using Postman for testing this.

Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 23, 2021

Closing the alert through the API would not change the message of the alert. You could update the alert's message through an API call or in the UI:

HI @Nick H ,

Understood. But in your example screenshot in postman, I see a 'message' field defined in the body for 'close' alert call, or I'm seeing it in the wrong way ?

The use case behind my question, is that there is a custom monitoring 'ERROR' and 'SUCCESS' solution for various services and environments that creates alerts in opsgenie when a service is Down. The question was how to make use of the rest API integration filters/conditions then in order to close an ERROR alert when same service is up again. Is it possible only via the close alert api ? 

Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 23, 2021

That is correct - in my example I defined the message field in the close alert request body.

But I'm realizing that the Close Alert action of the API integration might not be able to filter on the Message of the alert - so I do apologize for misleading you here. It's different than other integrations - like the Email integration with the other community post you shared.

You could alternatively have the Close Alert action act like a catch-all - matching on all alerts that do not match on a Create Alert action, and that would work through an API request:


Hi @Nick H 

Thanks for the clarification.

I tried the close api alert with the filter set to "match all alerts", even set the allias field to: {{alias}}, for the close action, instead of the substring function, and the alert was closed successfully (with empty body payload).

Thanks for your help!

Like # people like this

hi @Nick H , 

thanks for your reply. I changed the call to the close alert, and used exaclty same paradigm. So while I still see the

"result": "Request will be processed"
in the response of the 'Close" api call. still the message is the same in the logs  "Can not execute alert action. Incoming data does not match any actions.".
Message sample that I sent is: 
"[Product Environment] A-Service: SUCCESS"
which means, that the alias is found I guess, is just a problem with the rules/conditions in the integration maybe ?
Thank you.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events