Currently there seems to be no way to identify which action was responsible for a message.
Beside the informational benefit it would make it a lot easier to fix sending of multiple messages for the same trigger caused by sub-optimal configured action conditions.
- is duplicated by
-
ZBX-10606 Frontend Monitoring->Events section "Event Detail" do not show "name of actions"
- Closed