Type of received is not suitable for value type...

[galmok]

I noticed that I received not supported for some values and the message is:

Type of received value [1405923622912.000000] is not suitable for value type [Numeric (float)]

The configured key is:

perf_counter["\SQLServeratabases({#DBNAME})\Data File(s) Size (KB)",30]

It has a custom multiplier of 1024 and unit is B.

This key is part of a template and is used for a approx 10 databases.

Can I safely change the template containing this definition and if yes, to what?

By safely I mean: Do I lose any existing data? And will Zabbix the log the value?

I am using v3.0.7.

Thanks.

[wick]

hi galmok

You can change your Template safely doing a clone of the template and change your item value type to <Numeric (Unsigned)>

I think after that the item could return value

Sorry for my bad english

[galmok]

Thanks.

I am not interested in cloning the template, if it can be avoided.

4 questions:

Can't I just change the data format in the template?
Will this propagate to the configurations using the template?
Will this cause the data to be logged in the new format from when I changed it?
Will this keep or erase existing data recorded with the old format?

I know too little about Zabbix' inner workings to answer these questions myself.

I have tried posting to "Troubleshooting and Problems" but my problem wasn't enough of a problem for it to show up there. :-(

[wick]

1/ Yes you can do it
2/ I don't think because your items are in error so it will remain
3/ I do not understand this question
4/ I think it will erase them that is why I advised you to clone this template or just the item so you keep track of both
If you clone the items they will be propagate to the configurations of your host

[galmok]

Thank you for the answers.

My next question is this:

Seeing as Numeric(float) cannot contain the value, what are my options now?

The choices in the GUI are:

Numeric (float)
Numeric (unsigned)
Character
Log
Text

It seems to me that Numeric (unsigned) might be the only solution in this case.

I changed it to Numeric (unsigned) and now the size is logged. But as you wrote, the history is gone.

[galmok]

I want to add that the range for floats is somewhat limited:

Allowed range: -999999999999.9999 to 999999999999.9999

Why is the decimal separator placement a requirement? If this hadn't been there, I could have logged for a long time without issue.

The mentioned limitation seems to fit the decimal datatype better than a float (which by its name indicates floating point, i.e. floating decimal separator).

[wick]

Seeing as Numeric(float) cannot contain the value, what are my options now?

It's not a question you answer here

It seems to me that Numeric (unsigned) might be the only solution in this case.
I changed it to Numeric (unsigned) and now the size is logged. But as you wrote, the history is gone.

after

I want to add that the range for floats is somewhat limited:

True I agree

Why is the decimal separator placement a requirement? If this hadn't been there, I could have logged for a long time without issue.
The mentioned limitation seems to fit the decimal datatype better than a float

You have an answer here

https://www.zabbix.com/forum/showthread.php?t=37718

I think i can't help more ...

[galmok]

Thank you for the link, although I did find it on my initial search of this forum. I guess Zabbix just doesn't have a good solution for logging big numbers. Numeric(float) is incapable and Numeric(unsigned) prevents delta calculations.

For storage sizes, Numeric(unsigned) is usually fine, though.

Also, Zabbix could do with a system that optionally would preserve data when switching between data types.

[[email protected]]

I came across a different case .
I have php script that echos a value . I create it as an item and wanted to monitor the value


UserParameter=managerappcpu[*], php -f test.php

Then error with type data recieved [1] not supported with type Numeric (Unsigned)

I changed it to float still the error persisted .
But when check with my script . I came to know that my script was printing empty spaces . That's cause the problem .

if($cpu >0){


echo $cpu;
}

if($cpu >0){
echo $cpu;
}


So Please kindly check your script before deploying to live