# Stdout parse into json

**URL:** <https://discuss.elastic.co/t/stdout-parse-into-json/115237>\
**Category:** Kibana\
**Created:** [January 12, 2018, 8:11am UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237 "2018-01-12T08:11:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arght](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arght/32/26506_2.png) [@arght](https://discuss.elastic.co/u/arght)\
**Post date:** [January 12, 2018, 8:11am UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/1 "2018-01-12T08:11:06Z")

</div>

hi, my application generate logs in json format and output it to stdout. Is there a way to have it visible in kibana as a list of dictionaries?  
Currently i see it as a string  
"level": "info",  
"message": "{"whatever": "value1", "test": {"whatever2": "value2"}}",  
"hostname": "whatever1",...

and I want to see:  
"message": {"whatever": "value1", "test": {"whatever2": "value2"}},  
"hostname": "whatever1",...

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [January 12, 2018, 1:11pm UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/2 "2018-01-12T13:11:36Z")

</div>

Hey @arght, how are you ingesting your data into Elastisearch, are you using Beats or Logstash, or some other method? Generally you'll want to parse the log messages into the separate fields on ingest, so that you store the specific fields in Elasticsearch which allows you to query it appropriately.

---

<div class="post-metadata">

**Author:** ![Krunal\_kalaria](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krunal_kalaria/32/23862_2.png) [@Krunal\_kalaria](https://discuss.elastic.co/u/Krunal_kalaria)\
**Post date:** [January 12, 2018, 1:25pm UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/3 "2018-01-12T13:25:35Z")

</div>

hi @arght

You have any config file ?

---

<div class="post-metadata">

**Author:** ![arght](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arght/32/26506_2.png) [@arght](https://discuss.elastic.co/u/arght)\
**Post date:** [January 17, 2018, 7:55am UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/4 "2018-01-17T07:55:00Z")

</div>

hi, sorry for so late replay. W're using fluentd but i have only access to kibana as it runs on openshift

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [January 17, 2018, 1:28pm UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/5 "2018-01-17T13:28:13Z")

</div>

@arght I don't have enough experience with Fluentd to guide you on how to parse your logs differently, but I'd suggest investigating how to use Fluentd to parse the data from your logs into separate Elasticsearch fields.

---

<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:** [February 14, 2018, 1:28pm UTC](https://discuss.elastic.co/t/stdout-parse-into-json/115237/6 "2018-02-14T13:28:22Z")

</div>

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