screenshot-1.png
|
Causes |
Team INT
[ZBX-20606] Wrong OID used for uptime Created: 2022 Feb 17 Updated: 2025 Dec 23 Resolved: 2025 Dec 23 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Templates (T) |
| Affects Version/s: | 5.0.20, 5.4.10 |
| Fix Version/s: | 7.0.23rc1, 7.4.7rc1, 8.0.0alpha2 (master) |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Aleksey Volodin | Assignee: | Marina Generalova |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 11h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
screenshot-1.png
|
||||
| Issue Links: |
|
||||
| Team: | Team INT |
||||
| Story Points: | 0.5 | ||||
| Description |
|
For now in Template Module Generic SNMP for uptime used OID 1.3.6.1.2.1.1.3.0 which in fact is a 32-bit counter and will roll over after 496 days. Also since for value hundred of seconds used - preproc step with Custom multiplayer used. But you can poll 1.3.6.1.6.3.10.2.1.3.0 which returns the uptime in seconds and should not roll over for 135 years. And also since value returns in seconds preproc steps can be deleted.
|
| Comments |
| Comment by Marina Generalova [ 2025 Dec 23 ] |
|
We have looked into this ticket and our conclusion is that there is no need to fix the OID because both OIDs are valid and replacing one with another does not solve any problem. I will close this ticket as WON'T FIX. |