Setting statsd timing output to a hash results in config parse error
Description
Gliffy Diagrams
Activity
Show:
Jordan Sissel March 30, 2013 at 8:32 PM
Full confession - logstash has a crappy way of representing hashes. I'm hoping to improve the config parser to accept proper hash syntax soon.
Josh Russell March 28, 2013 at 8:24 PM
I'm an idiot and did not see the definition of a "hash" as it pertains to logstash at http://logstash.net/docs/1.1.9/configuration
Disregard
Using logstash-1.1.9-monolithic.jar, the documentation at http://logstash.net/docs/1.1.9/outputs/statsd#setting_timing states:
timing
Value type is hash
Default value is {}
A timing metric. metric_name => duration as hash
However, specifying this parameter as a hash like the following:
statsd { host => "graphite.host.net" namespace => 'logstash' sender => 'hostname' timing => {"prod.lb.app.nginx.response_time"=>"%{responsetime}"} }results in:
Error at line 48, column 15: "{\"prod.lb.app.nginx.response_time\"=>\"%{responsetime}\"}\n }\n}\n\n"Specifying the parameter as an array works as expected