[ZBXNEXT-5564] adjust the SNMP-Uptime trigger in the SNMP Template Created: 2019 Nov 13 Updated: 2024 Jan 23 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Templates (T) |
Affects Version/s: | 4.4.1 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Stefan | Assignee: | Aleksandre Sebiskveradze |
Resolution: | Unresolved | Votes: | 22 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
||||||||
Issue Links: |
|
Description |
Hello, due a SNMP-"Bug" or better the 32bit limitations the uptime is reset after 497days, and we got messages the server has been restarted. It would be very nice if you can adjust them to something like if last =497days and now 0days its fire not the trigger |
Comments |
Comment by Alireza Fallah [ 2020 Apr 11 ] |
This issue is very annoying and so many people are looking for work around and solution, It would be nice even if you can come up with an expression for the trigger to ignore the change from 479 days to 0 in the meantime you fix the issue on the software.
Thank you |
Comment by Oleksii Zagorskyi [ 2021 Jun 30 ] |
Forum discussion https://www.zabbix.com/forum/zabbix-help/47245-snmp-uptime-overflow-after-497-days |
Comment by sSiDs [ 2021 Jul 08 ] |
same issue...and above solution didnt help...or i've made smthng wrong... |
Comment by Craig Hopkins [ 2022 Jul 25 ] |
We've amended our trigger to only alert if any of the last 10 values don't exceed 497 days |
Comment by aws maythem [ 2024 Jan 23 ] |
I added 1.3.6.1.6.3.10.2.1.3.0 item for snmpEngineTime and made a trigger for 2 items : |