<?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 Parsing JSON syslog data - additional fields extraction happening. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-JSON-syslog-data-additional-fields-extraction-happening/m-p/380155#M68660</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;need help in parsing below JSON message.&lt;/P&gt;

&lt;P&gt;{ "MsgDesc": "1229340728.000000:iso.3.6.1.4.1.9.9.96.1.1.1.1.2.567777 = INTEGER: 1 iso.3.6.1.4.1.9.9.96.1.1.1.1.3.345455 = INTEGER: 3 iso.3.6.1.4.1.9.9.96.1.1.1.1.4.345435 = INTEGER: 1 iso.3.6.1.4.1.9.9.96.1.1.1.1.5.111249171 = IpAddress: 192.168.1.100 iso.3.6.1.4.1.9.9.", "MsgType": "SNMPD-3-ERROR", "Severity": 3}&lt;/P&gt;

&lt;P&gt;props for this sourcetype are in HF ( Splunk version 7.3.0 &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;pulldown_type = true&lt;BR /&gt;
category = Structured&lt;BR /&gt;
KV_MODE = none&lt;BR /&gt;
AUTO_KV_JSON = false&lt;BR /&gt;
INDEXED_EXTRACTIONS= json&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;The problem is along with the MsgDesc, MsgType &amp;amp; Severity, Splunk extracting iso.3.6.1.4.1.9.9.96.1.1.1.1.2.567777, iso.3.6.1.4.1.9.9.96.1.1.1.1.3.345455 also. from the MsgDesc value. I dont want these extra fields. Is there a way solve this?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Seshu&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 01:14:59 GMT</pubDate>
    <dc:creator>seshagirik545</dc:creator>
    <dc:date>2020-09-30T01:14:59Z</dc:date>
    <item>
      <title>Parsing JSON syslog data - additional fields extraction happening.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-JSON-syslog-data-additional-fields-extraction-happening/m-p/380155#M68660</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;need help in parsing below JSON message.&lt;/P&gt;

&lt;P&gt;{ "MsgDesc": "1229340728.000000:iso.3.6.1.4.1.9.9.96.1.1.1.1.2.567777 = INTEGER: 1 iso.3.6.1.4.1.9.9.96.1.1.1.1.3.345455 = INTEGER: 3 iso.3.6.1.4.1.9.9.96.1.1.1.1.4.345435 = INTEGER: 1 iso.3.6.1.4.1.9.9.96.1.1.1.1.5.111249171 = IpAddress: 192.168.1.100 iso.3.6.1.4.1.9.9.", "MsgType": "SNMPD-3-ERROR", "Severity": 3}&lt;/P&gt;

&lt;P&gt;props for this sourcetype are in HF ( Splunk version 7.3.0 &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;pulldown_type = true&lt;BR /&gt;
category = Structured&lt;BR /&gt;
KV_MODE = none&lt;BR /&gt;
AUTO_KV_JSON = false&lt;BR /&gt;
INDEXED_EXTRACTIONS= json&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;The problem is along with the MsgDesc, MsgType &amp;amp; Severity, Splunk extracting iso.3.6.1.4.1.9.9.96.1.1.1.1.2.567777, iso.3.6.1.4.1.9.9.96.1.1.1.1.3.345455 also. from the MsgDesc value. I dont want these extra fields. Is there a way solve this?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Seshu&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:14:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-JSON-syslog-data-additional-fields-extraction-happening/m-p/380155#M68660</guid>
      <dc:creator>seshagirik545</dc:creator>
      <dc:date>2020-09-30T01:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing JSON syslog data - additional fields extraction happening.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-JSON-syslog-data-additional-fields-extraction-happening/m-p/380156#M68661</link>
      <description>&lt;P&gt;That's because splunk is also auto extracting the Key value Pairs (this=that), most likely because you are in verbose mode while searching.  Your KV_MODE=none should fix that but it has to be set on your search heads not the forwarder.&lt;/P&gt;

&lt;P&gt;Also INDEXED_EXTRACTIONS=JSON should be all uppercase and it should be on the first forwarder that "sees" the data (UF or HF).  &lt;/P&gt;</description>
      <pubDate>Sun, 07 Jul 2019 16:06:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-JSON-syslog-data-additional-fields-extraction-happening/m-p/380156#M68661</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2019-07-07T16:06:59Z</dc:date>
    </item>
  </channel>
</rss>

