-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Trivial
-
None
-
Affects Version/s: 7.0.32, 8.0.0
-
Component/s: Templates (T)
Hello Dev Team,
The F5 Big-IP by SNMP template contains pool status trigger prototypes that use count based expressions incompatible with the configured "Discard unchanged with heartbeat: 1h" preprocessing.
As a result, persistent pool failures may remain undetected, and no problem event is generated.
Affected versions:
Zabbix 7.0.32
Zabbix 7.4 - same configuration verified.
Zabbix 8.0 - same configuration verified.
Affected components:
Template: F5 Big-IP by SNMP
Discovery rule: pool discovery
Item prototypes: pool status available and pool status enabled
Trigger prototypes: pool not available / pool not enabled
Configuration causing the issue:
Both affected item prototypes have the following settings:
Update interval: 5m
Preprocessing: Discard unchanged with heartbeat - 1h
The corresponding trigger expressions are:
Pool availability:
count(/F5 Big-IP by SNMP/bigip.pool.available[{#POOL.NAME}],120m,"ne","1")>20
Pool enabled:
count(/F5 Big-IP by SNMP/bigip.pool.enabled[{#POOL.NAME}],120m,"ne","1")>4
Steps to reproduce
1. Import and link the official F5 Big-IP by SNMP template to a device.
2. Verify that the pool status available and the pool status enabled item prototypes use 5 - minute polling and 1 - hour heartbeat preprocessing.
3. For the availability scenario, set or simulate a persistent unavailable pool state for example, availability value 3 - red.
4. For the enabled scenario, set or simulate a persistent disabled pool state > value 2.
5. Keep each failure state unchanged for more than 120 minutes.
6. Check the corresponding item history, trigger expressions and generated problem events.
Thank you!