No Resolved message after Alert goes back to Normal state?

Hi everyone,

I am currently having a trouble where I won’t received any Resolved message after Alert goes back to Normal state. This error only occurs when using Microsoft Teams Workflows as Contact point, I still get the Resolved message with Email as Contact point.
Anyone has any idea how to solve this problem? I am using Grafana v11.1.0 (5b85c4c2fc).

Thank and Best Regards,
Anh Kieu

Hi there!

I am facing the same issue, so this must be prevailing issue.

Hope someone would be able to help us.

  • Ensure resolved notifications are not disabled for the contact point
  • Enable debug logs in Grafana.
  • Check for log lines that mentions Notify success, [resolved] and integration=teams. If there are entries, then you need to check the Teams Worklflow. It has debug functionality and shows which requests were received.

Thank you for your response @yuriy.tseretyan!

Ensured everything in order for it to work, but it just doesn’t.
Logs say that the state only changes from firing to resolved and doesn’t mention notify success at all.

Could this be an issue related to Grafana: Webhook Failed Validation - upon sending message to Teams · Issue #89617 · grafana/grafana · GitHub ? Does Grafana keep the state of which notification it sent? I also get the same error when Grafana sends notification to Teams Workflow, but I can not implement the workaround because of the limitation with Teams subscription.

Could this be the case why Grafana resolved notification is not being triggered aka Grafana never got the information that other side (Workflow) actually got the notification for firing alert, but views it as error because of wrong response code?

Thank you for your answer!

Try to upgrade to 11.1.2 or to the latest minor (11.6) and try again. Pull the changes in the MS teams contact point did not seem to be included into your version Alerting: Update grafana/alerting to 20240712181403-02e012d6dd7f by yuri-tceretian · Pull Request #90386 · grafana/grafana · GitHub

1 Like

@yuriy.tseretyan

Indeed, the problem was in version and fixes!

I upgraded to the pre-latest version 11.5.2. and now everything works like a charm!

Thank you for your assistance! :slight_smile:

2 Likes