# Parsing of thrift fields - not quite JSON

**URL:** <https://discuss.elastic.co/t/parsing-of-thrift-fields-not-quite-json/101550>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [September 23, 2017, 12:29am UTC](https://discuss.elastic.co/t/parsing-of-thrift-fields-not-quite-json/101550 "2017-09-23T00:29:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidbernard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidbernard/32/22472_2.png) [@davidbernard](https://discuss.elastic.co/u/davidbernard)\
**Post date:** [September 23, 2017, 12:29am UTC](https://discuss.elastic.co/t/parsing-of-thrift-fields-not-quite-json/101550/1 "2017-09-23T00:29:04Z")

</div>

The thrift fields representing params, request and response are in "human readable format".

Does anyone have advise as to how to parse these with logstash?

```
  "thrift": {
        "params": "(messages: [(1: \"test\", 2: \"The parrot cannot be concerned all with the cat\\n\")])",
        "return_value": "0"
  }

```

Should the be in JSON instead?

---

<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:** [October 21, 2017, 12:29am UTC](https://discuss.elastic.co/t/parsing-of-thrift-fields-not-quite-json/101550/2 "2017-10-21T00:29:42Z")

</div>

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