workaround 'parse_value: Ignoring trailing garbage ".0"'

[skarap]

When using curl_json to monitor couchdb _stats values I get a lot of 'parse_value: Ignoring trailing garbage ".0" after derive value. Input string was "4392.0".' type errors. The problem is that reported values in json have a trailing ".0" even if those are integers (e.g. couchdb/auth_cache_hits/current).

What do you think about making couchdb ignore the trailing ".0" if the expected type is integer? I can probably do it in parse_value function in src/daemon/common.c .

[mfournier]

This issue was also reported to the mailing-list: http://mailman.verplant.org/pipermail/collectd/2014-August/006296.html

and somebody complained about it on IRC just now.

[jespada]

Indeed I'm experiencing the same problem, with the same component mentioned on the mailing-list

[schafik]

experiencing same problem

[anowak]

The same problem here. This message is emitted with INFO severity, so setting log level to notice can be sometimes used as a workaround.

[piotrskowron-scrive]

The same with postgresql monitroing
[2016-04-16 20:38:36] parse_value: Ignoring trailing garbage ".639" after derive value. Input string was "8.639".

[octo]

IIuc, JSON only supports floating point values (and those poorly). When parsing JSON, we should probably either assume double and cast to derive_t or use libyajl for the job.