HTTPJSONCollector 'double-dots' Hystrix metrics?

[mejofi]

Apologies if this is a configuration option I have missed, but I am having an issue with the HTTPJSONCollector talking to a Hystrix metrics endpoint in a Java application. It collects everything just fine, but inserts an extra dot in the collected data, regardless of whether we set the path, or how long this path is in terms of elements.

No other configuration other than enabled and url, which yields entries like this;

servers.net.example.appserv.httpjson..hystrix.ThreadPool.x.x 0 1471943878

The Hystrix endpoint is the default configuration, as far as I know. Is this expected behaviour, an error in the data, or some mismatch between collector and endpoint?

JSON data is formatted like this;

{"hystrix.ThreadPool.x.x":0,"hystrix.Command.x.x":0}

Much more extensive than that, but the above is the basic format; all on one line, key-value pairs separated by commas, curly braces, validates as proper JSON.

Thanks!

[josegonzalez]

Seems like a prefixing bug. I feel as though there was a pr made recently to fix this, though I'll have to check.

[shortdudey123]

This is due to the _json_to_flat_metrics method having prefix empty on the initial call. This causes a leading dot to be added on line 49 (probably same thing with line 41).

I do not have time to put a PR in right now so feel free to submit one.