I have an MS Teams v2 integration where alert messages are sent to a Teams channel when an alert is created in Opsgenie.
I have an alert filter set up of:
Match one or more conditions below
Message Not Contains 4xx
I was hoping that this would prevent any messages being sent to the Teams channel where the message field contained "4xx" but this doesn't seem to be working.
Is this how the filters should work, or does the action of sending a message upon create override the condition filter?
Hello There,
Thanks for reaching out to Atlassian Community!
The filter you’ve set up (Message Not Contains 4xx
) should work as expected to prevent alerts with "4xx" in the message field from being sent to the Teams channel. However, if it’s not working, there are a few things to check:
Filter Placement: Ensure that the filter is correctly configured in the Microsoft Teams v2 integration settings. Filters in Opsgenie integrations are applied to determine which alerts are forwarded to the integration.
Action Mapping: By default, Opsgenie forwards several alert actions (e.g., create, acknowledge, close) to Microsoft Teams. The "Create" action is mandatory and cannot be disabled, but the filter should still apply to it.
Filter Logic: Double-check the filter logic. For example, ensure there are no typos or formatting issues in the condition (Message Not Contains 4xx
).
If the filter is correctly configured and still not working, it’s possible that the integration is not applying the filter as expected. In this case, I recommend:
Testing the filter with a different condition to confirm if the issue is specific to "4xx".
Reviewing the integration logs in Opsgenie to see if the alerts are being forwarded despite the filter.
If the issue persists, it might require further investigation by Opsgenie support. Please contact us using the following link - https://support.atlassian.com/contact/
Best Regards,
Egor
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.