Opsgenie Alert is not Created

Question

I have an alert configured in the elastic cloud which I throw at both Slack and opsgenie API (webhook).

The alert goes through the Slack channel but the opsgenie doesn't create an alert for it.

Could you tell me how to troubleshoot it?

PS:

I have multiple alerts configured and the other similar alerts work fine on both Slack and Opsgenie. I have tested them as well.

One noticeable difference is that this alert (problematic) has a status check of down for >1 within 1 minute while the others have >5 within 10 minutes.

Moh Wijayanto · Answer

Sorry for the late reply.

I just found out that the alert was never created in the first place.

The log from before is opsgenie trying to close the alert when it is recovered.

It failed because the alert is not created.

Nick Haller · Answer

Can you review either the the Processed incomingData and/or Received integration request logs?

They might shed some light into what is be parsing in the payload, or if there is not anything parsing in the payload at all - so you can reference whether or not the data is matching on the create alert action.

I know you mentioned the create alert action is set to Match all alerts, but there could be more in the log to determine why alerts are not being created.

The log you shared;

Can not execute alert action. There is no open alert with alias

leads me to believe the request received is trying to preform some other actions than creating an alert.

Wija MW · Answer

I got an error

Can not execute alert action. There is no open alert with alias ...

I use match all alerts type in the create alert's filter.

I think it should match every data that is coming.

I have checked my policy as well but I think there is nothing that blocking it.

Do you have any suggestion on what should I check next?