<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Field-extraction on a JSON message with multiple delimiters? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317504#M94976</link>
    <description>&lt;P&gt;It helped. Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 04 Dec 2017 17:34:01 GMT</pubDate>
    <dc:creator>jayakumar89</dc:creator>
    <dc:date>2017-12-04T17:34:01Z</dc:date>
    <item>
      <title>Field-extraction on a JSON message with multiple delimiters?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317502#M94974</link>
      <description>&lt;P&gt;I have this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;{"date": null, "facility": -1, "host": null, "level": -1, "message": "2017-11-13T03:45:00+0000 monStatsLog, applianceName=xxxxx, tenantName=xxxx, mstatsTimeBlock=1510544700, tenantId=1, vsnId=0, mstatsTotSentOctets=250, mstatsTotRecvdOctets=0, mstatsTotSessDuration=26001, mstatsTotSessCount=1, mstatsType=sdwan-acc-ckt-app-stats, mstatsId=tftp:Controller1:MPLS:1:2, mstatsAttribs=1:3:general-internet:file-server:Unknown", "charset": "UTF-8", "remote_address": "xxxxxxx", "hostname": "xxxxxx"}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm trying to parse a json file with entries like above, where the &lt;CODE&gt;message&lt;/CODE&gt; field has multiple values, which are in turn delimited using comma and =. How can I parse that specific field to extract all the information?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2017 17:57:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317502#M94974</guid>
      <dc:creator>jayakumar89</dc:creator>
      <dc:date>2017-12-01T17:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Field-extraction on a JSON message with multiple delimiters?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317503#M94975</link>
      <description>&lt;P&gt;Assuming that your JSON is coherent and being processed correctly you should already have a &lt;CODE&gt;message&lt;/CODE&gt; field so just do this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| makeresults 
| eval message="2017-11-13T03:45:00+0000 monStatsLog, applianceName=xxxxx, tenantName=xxxx, mstatsTimeBlock=1510544700, tenantId=1, vsnId=0, mstatsTotSentOctets=250, mstatsTotRecvdOctets=0, mstatsTotSessDuration=26001, mstatsTotSessCount=1, mstatsType=sdwan-acc-ckt-app-stats, mstatsId=tftp:Controller1:MPLS:1:2, mstatsAttribs=1:3:general-internet:file-server:Unknown"

| rename COMMENT AS "Everything above generates sample event data; everything below is your solution"

| rename message AS _raw
| kv
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 02 Dec 2017 21:33:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317503#M94975</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-12-02T21:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: Field-extraction on a JSON message with multiple delimiters?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317504#M94976</link>
      <description>&lt;P&gt;It helped. Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2017 17:34:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Field-extraction-on-a-JSON-message-with-multiple-delimiters/m-p/317504#M94976</guid>
      <dc:creator>jayakumar89</dc:creator>
      <dc:date>2017-12-04T17:34:01Z</dc:date>
    </item>
  </channel>
</rss>

