-
Problem report
-
Resolution: Fixed
-
Trivial
-
None
-
5.0.36
-
None
-
Zabbix version 5.4.4 running on RHEL8 in AWS; supported Aurora MySQL DB
I have created a new trigger action for Atlassian servers (Jira, Bitbucket, Bamboo, Confluence, etc.). I can see Problems in Monitoring > Problems but there is no action being taken. Any alert w/ a severity of Critical or above should be generating an email alert to the respective team and this is not happening.
Troubleshooting Steps:
- Have triple checked the trigger alert conditions and operations, host groups, items and triggers and found no issues
- Identical trigger actions for other host groups work
- Deleted the original trigger action that wasn't working, cloned from working trigger action (adding relevant conditions & operations), same result
- Rebuilt the trigger action from scratch (i.e. not cloned from an existing trigger action), same result
- Placed all hosts in a single host group (e.g. Application/Server/SOE/Atlassian/Prod instead of Application/Server/SOE/Atlassian/Prod and Application/Server/SOE/Atlassian/Prod/Jira, etc.)
- Sent test emails to the email distros via Media Types & they arrive without any issue, so no problems w/ the distro, user, or media type
Suggestions/Ideas:
I've noticed this bug several times previously. This is a serious issue & the team expecting the alerts understandably wants to know why they aren't arriving.
Please provide a step-by-step approach for debugging/troubleshooting this problem. Simply stating that you're unable to recreate the issue in your test environment in not a legitimate attempt to fix this bug (obviously). All the screenshots you should need are attached.