# Keep double quote on JSON trace

**URL:** <https://discuss.elastic.co/t/keep-double-quote-on-json-trace/153691>\
**Category:** Logstash\
**Created:** [October 23, 2018, 10:11pm UTC](https://discuss.elastic.co/t/keep-double-quote-on-json-trace/153691 "2018-10-23T22:11:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Wadin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonathan_wadin/32/36858_2.png) [@Jonathan\_Wadin](https://discuss.elastic.co/u/Jonathan_Wadin)\
**Post date:** [October 23, 2018, 10:11pm UTC](https://discuss.elastic.co/t/keep-double-quote-on-json-trace/153691/1 "2018-10-23T22:11:06Z")

</div>

Hello,

I have a log file which produces a json content on one line well formatted. When I print it with the output { stdout { codec =\> rubydebug } } I see the correct Json with the fields double quote surround correctly parsed into "message". When I try to pass this json to a command line parameter through the plugin-exec-output the json is passed without the double quote field, example :  
Log : { "param1": "valeur", "param2" : "valeur2" }  
Message (stdout rubydebug) : "message" =\> "{ "param1": "valeur", "param2": "valeur2"}  
output exec : command =\> "binary.exe "%{message}""  
execute : binary.exe { param1: valeur, param2: valeur2 } without the double quote which surround the parameter and values.

Any explanation?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 20, 2018, 10:24pm UTC](https://discuss.elastic.co/t/keep-double-quote-on-json-trace/153691/2 "2018-11-20T22:24:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.