hexadecimal value

[rboersma]

Hi,

Zabbix reads the temparature OID of a QNAP system as 32 38 C2 B0 43 2F 38 32 C2 B0 46. After conversion to string (http://www.string-functions.com/hex-string.aspx) it should read something like this:
28°C/82°F?. Thats 28 degrees Celsius and 82 degrees Fahrenheid.
This is after getting rid of the spaces manually. When choosing numeric unsigned (hexadecimal), zabbix just shows 32. That is the first two numbers read from the OID's value.
I'm running 1.8.3, and thought this to be fixed in this release. But I'm clearly doing something wrong here.
Can anyone help me out?

Thanks,

Ruud Boersma

[rboersma]

Numeric (integer 64bit)

What do i have to do to get the value type "Numeric (integer 64bit)
"?
I only can choose between:
Numeric (unsigned)
Numeric (float)
character
log
text

edit: see https://support.zabbix.com/browse/ZBX-2452

[asaveljevs]

"Numeric (integer 64bit)" is the old name for "Numeric (unsigned)", so you can disregard that.

Regarding https://support.zabbix.com/browse/ZBX-2452, we have implemented parsing of strings like "32 38 C2 B0 43 2F 38 32 C2 B0 46" as simply removing spaces and then converting "3238C2B0432F3832C2B046" to decimal. If the correct behavior according to some standard specification is to convert "32 38 C2 B0 43 2F 38 32 C2 B0 46" to "28°C/82°F" and parse that instead, please feel free to open an issue on our tracker.

[rboersma]

correct value or not

I do not know if it's a standard behaviour, but it seems that in this case the conversion from hex to string gives the right value. Coverting from hex to decimal gives a value I can not work with. But it is very good possible that there are oid's out there that should be converted from hex to numeric.

Maybe an extra option in the ITEM where we can select the type of conversion after setting the "type of information" should do the trick.
So you have to set the type of information to "numeric unsigned"
data type "hexadecimal"
Convert value to "numeric" or "string".

[asaveljevs]

That might be one of the options. Could you please create an issue about it on https://support.zabbix.com/? We like it very much when issues are on the tracker instead of forums, otherwise they can be lost and forgotten.

[asaveljevs]

This issue has been reported as https://support.zabbix.com/browse/ZBXNEXT-505. Thanks!

[Sparky]

Hi Guys

This is pretty much the last issue I have on Zabbix, but I need a little help.

How do I apply the patch listed at http://ramblings.narrabilis.com/wp/q...sanbox-zabbix/

Do I need to recompile the whole Zabbix system after adding this code to misc.c (following the install instructions), or do I just copy this code into a file (if so, where?)

Edit : On further reading, this issue should have been resolved from version 1.8.3. I currently have server version 1.8.4 running, but I'm still seeing the hex vaules (with spaces) instead of the "human readable" trap.

Any ideas?

[Sparky]

Apologies for the bump, but I just cant seem to figure this one out.

[Sparky]

Ok, I've tried installing a VM and testing a fix for this, but I'm not coming right.

No ideas guys??