(Running Zabbix 6.0 from Docker)
Hello! I am monitoring a HP LaserJet M15w printer with SNMPv3, however I am having issues when trying to create an item for the system uptime using this OID
However, when setting the up the item as per https://www.zabbix.com/documentation...fig/items/item:
I set the item in the following way:
But I get this value in return:
NOTE: I did notice that the item preprocessing needed to be set to "Change per second", as per the documentation, but this might actually be the issue?
Any help would be greatly appreciated!
Hello! I am monitoring a HP LaserJet M15w printer with SNMPv3, however I am having issues when trying to create an item for the system uptime using this OID
Code:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1871274) 5:11:52.74
Special processing is used if the following time-related units are used:
unixtime - translated to "yyyy.mm.dd hh:mm:ss". To translate correctly, the received value must be a Numeric (unsigned) type of information.
uptime - translated to "hh:mm:ss" or "N days, hh:mm:ss"
For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:56:04"
s - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.
For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"
unixtime - translated to "yyyy.mm.dd hh:mm:ss". To translate correctly, the received value must be a Numeric (unsigned) type of information.
uptime - translated to "hh:mm:ss" or "N days, hh:mm:ss"
For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:56:04"
s - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.
For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"
But I get this value in return:
NOTE: I did notice that the item preprocessing needed to be set to "Change per second", as per the documentation, but this might actually be the issue?
Any help would be greatly appreciated!
polling in 3s interval does not do any good...
Comment