-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
Affects Version/s: 8.0.0alpha2
-
Component/s: Server (S)
-
None
-
S26-W10/11
-
0.25
How to reproduce:
default server, default settings
1) Install the latest Zabbix server (tested with Revision bed5ab9 and with the latest Docker trunk image)
2) Add a Test media webhook for version 8.0 (Alerts>Media types):
3) Enable problem reporting for trigger actions (Alerts > Actions > Trigger actions).
4) Set up media notifications for the user (User settings>Notifications>Media>>Add) using the added Test webhook. The "Send to" field can be filled with any characters.
5) Create any host with an item, assign it a value (e.g., 0).
6) Set a trigger for this item to generate a problem (e.g., when item value = 1).
7) Trigger the problem by changing the item value to the alarming value (e.g., 1).
8) Go to Monitoring > Problems. The created problem should receive additional tags:
__tag1: value1, __tag2: value2, but it does not receive them correctly:
Expected behavior:
The triggered problem should receive the correct tags assigned by the webhook.

Notes:
- Issue does not appear in Zabbix versions: 7.0 (Revision 5891b60) and 7.4 (Revision bed5ab9)
- Issue was confirmed on two local machines and on a VM
- Also attaching webhooks for the remaining Zabbix versions.
- caused by
-
ZBX-27271 Improve scalability and performance by not calculating hash for uint64
-
- Closed
-