[ZBX-20075] [template][F5 Big-IP SNMP] wrong trigger expression for certificate monitoring Created: 2021 Oct 12 Updated: 2024 Apr 10 Resolved: 2021 Dec 13 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Templates (T) |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | 5.0.19rc1, 5.4.9rc1, 6.0.0beta1, 6.0 (plan) |
| Type: | Problem report | Priority: | Major |
| Reporter: | thomas | Assignee: | Alexander Bakaldin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | templates | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Zabbix installation "All In One" VM |
||
| Team: | |
| Sprint: | Sprint 83 (Dec 2021) |
| Story Points: | 1 |
| Description |
|
Steps to reproduce: Create a host and link template "F5 Big-IP SNMP" to this host. If host is a F5 device, installed certificates are discovered by "Certificate discovery" rule. Result: Trigger expression to monitor certificate expiration date is wrong :
last(/F5 Big-IP SNMP/bigip.cert.expiration.date[{#CERT.NAME}]) + 86400 * {$BIGIP.CERT.MIN} < now()
Problem isn't not created when there is less than {$BIGIP.CERT.MIN} days before certificate expiration but {$BIGIP.CERT.MIN} days later after certificate expiration. Expected: Trigger expression should be :
last(/BDF F5 Big-IP SNMP/bigip.cert.expiration.date[{#CERT.NAME}]) - 86400 * {$BIGIP.CERT.MIN} < now()
I also suggest improvements :
|
| Comments |
| Comment by Alexander Bakaldin [ 2021 Dec 07 ] |
|
Available in:
|