[ZBXNEXT-1046] Conversation from hexademical 8-octet long OctectString to integer Created: 2011 Dec 02  Updated: 2021 Oct 15  Resolved: 2021 Oct 15

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Change Request Priority: Major
Reporter: Kiril Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: flexibility, preprocessing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-1444 Zabbix Lua Master Ticket Closed

 Comments   
Comment by Kiril [ 2011 Dec 02 ]

SNMP Integer value is stored on 4 octets, which is too small for counters. For this reason a lot of application used 8-octet long OctectString hexademical format.
The latest Zabbix version (1.8.9) does not support such kind of conversation. As a result the configured items that has to get via SNMP value in 8-octet long OctectString hexademical format does not work.
It will be great if it is possible during teh configuretion fo the snmp item to be able to choose also the type of conversation that you want.

Also this will be a great advantage because almost all of the monitoring system does not support such type of conversation and it is necessary to be with external script.

Comment by richlv [ 2011 Dec 08 ]

sorry for ignorance, doesn't value type "hex" help here ?
values with spaces were supposed to be fixed in ZBX-2452

Comment by richlv [ 2011 Dec 08 ]

possibly related forum thread :
http://www.zabbix.com/forum/showthread.php?t=17774

Comment by Alexei Vladishev [ 2021 Oct 15 ]

JavaScript preprocessing is what we need here.

Generated at Fri Apr 26 05:43:30 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.