# Parsing JOSON in a pipeline

**URL:** <https://community.graylog.org/t/parsing-joson-in-a-pipeline/11100>\
**Category:** Graylog Central (peer support)\
**Created:** [July 8, 2019, 4:01pm UTC](https://community.graylog.org/t/parsing-joson-in-a-pipeline/11100 "2019-07-08T16:01:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Magneton](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/magneton/32/1609_2.png) [@Magneton](https://community.graylog.org/u/Magneton)\
**Post date:** [July 8, 2019, 4:01pm UTC](https://community.graylog.org/t/parsing-joson-in-a-pipeline/11100/1 "2019-07-08T16:01:30Z")

</div>

Dear All,

I have some JSON which is sent via a python script as part of a message, it is in the form of an array for a JSON field value similar to below

‘ExtendedProperties’: [{  
‘Name’: ‘UserAgent’,  
‘Value’: ‘CBAInPROD’  
}, {  
‘Name’: ‘RequestType’,  
‘Value’: ‘OrgIdWsTrust2:process’  
}, {  
‘Name’: ‘ResultStatusDetail’,  
‘Value’: ‘UserError’  
}],

It gets parsed by the JSON extractor on the input and is in a single field in the form as shown below.

{Name=UserAgent, Value=CBAInPROD}, {Name=RequestType, Value=OrgIdWsTrust2:process}, {Name=ResultStatusDetail, Value=UserError}

I would like to parse it out further. What would be the best method either parse\_json in a pipeline or using jsonpath?

Cheers

Jake

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [July 22, 2019, 4:07pm UTC](https://community.graylog.org/t/parsing-joson-in-a-pipeline/11100/2 "2019-07-22T16:07:13Z")

</div>

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