<?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: Do I have a possible KV extraction issue on the universal forwarder? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431985#M75607</link>
    <description>&lt;P&gt;HI @ehowardl3 ,&lt;/P&gt;

&lt;P&gt;I am assuming that forwarder means Universal forwarder, in that case can you please apply below configuration on Universal Forwarder ?&lt;/P&gt;

&lt;P&gt;props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test:json]
INDEXED_EXTRACTIONS = json
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 28 Aug 2018 09:18:49 GMT</pubDate>
    <dc:creator>harsmarvania57</dc:creator>
    <dc:date>2018-08-28T09:18:49Z</dc:date>
    <item>
      <title>Do I have a possible KV extraction issue on the universal forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431984#M75606</link>
      <description>&lt;P&gt;I have some json events that are fairly long (10K-20K characters). Most events come through fine, except for the fact that some events have an issue with some of the fields towards the end of the event not being automatically extracted. I ran a couple of searches and found that the maximum raw length of the events with no issues is 10,197, while the minimum raw length of the events with the extraction issues is 10,251. &lt;/P&gt;

&lt;P&gt;This led me to believe that I needed to bump up maxchars in the kv stanza in limits.conf, since it has a default limit of 10,240. However, upon making the change, the extraction issues remain. Here are my configurations:&lt;/P&gt;

&lt;P&gt;On the forwarder:&lt;/P&gt;

&lt;P&gt;props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test:json]
KV_MODE = json
TIMESTAMP_FIELDS = Date
TRUNCATE = 0
NO_BINARY_CHECK = true
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;On the search head:&lt;/P&gt;

&lt;P&gt;limits.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[kv]
limit = 200
maxchars = 25000
maxcols = 1024
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any ideas?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;BR /&gt;
E&lt;/P&gt;</description>
      <pubDate>Mon, 27 Aug 2018 20:21:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431984#M75606</guid>
      <dc:creator>ehowardl3</dc:creator>
      <dc:date>2018-08-27T20:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Do I have a possible KV extraction issue on the universal forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431985#M75607</link>
      <description>&lt;P&gt;HI @ehowardl3 ,&lt;/P&gt;

&lt;P&gt;I am assuming that forwarder means Universal forwarder, in that case can you please apply below configuration on Universal Forwarder ?&lt;/P&gt;

&lt;P&gt;props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test:json]
INDEXED_EXTRACTIONS = json
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 28 Aug 2018 09:18:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431985#M75607</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2018-08-28T09:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Do I have a possible KV extraction issue on the universal forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431986#M75608</link>
      <description>&lt;P&gt;Thank you! This worked. I had tried that previously, however I had:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[test:json]
INDEXED_EXTRACTIONS = JSON
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm assuming the uppercase JSON was causing an issue.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 12:11:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431986#M75608</guid>
      <dc:creator>ehowardl3</dc:creator>
      <dc:date>2018-08-28T12:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: Do I have a possible KV extraction issue on the universal forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431987#M75609</link>
      <description>&lt;P&gt;Great, it worked. I have converted my comment to answer so that you can accept/upvote it.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Harshil&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 12:29:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Do-I-have-a-possible-KV-extraction-issue-on-the-universal/m-p/431987#M75609</guid>
      <dc:creator>harsmarvania57</dc:creator>
      <dc:date>2018-08-28T12:29:08Z</dc:date>
    </item>
  </channel>
</rss>

