<?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 What are the requirements for a perfect Splunk JSON document? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349922#M64235</link>
    <description>&lt;P&gt;Our Sales Engineer told us that the Splunk json parser requires several specific things in the json document, in order to be interpreted as json. What are they?&lt;/P&gt;

&lt;P&gt;We would like to avoid hard-coded solutions such as &lt;A href="https://answers.splunk.com/answers/607375/how-do-we-assign-each-json-document-to-a-distinct-1.html"&gt;How do we assign each JSON document to a distinct event?&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jan 2018 15:00:56 GMT</pubDate>
    <dc:creator>ddrillic</dc:creator>
    <dc:date>2018-01-30T15:00:56Z</dc:date>
    <item>
      <title>What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349922#M64235</link>
      <description>&lt;P&gt;Our Sales Engineer told us that the Splunk json parser requires several specific things in the json document, in order to be interpreted as json. What are they?&lt;/P&gt;

&lt;P&gt;We would like to avoid hard-coded solutions such as &lt;A href="https://answers.splunk.com/answers/607375/how-do-we-assign-each-json-document-to-a-distinct-1.html"&gt;How do we assign each JSON document to a distinct event?&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 15:00:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349922#M64235</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-30T15:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349923#M64236</link>
      <description>&lt;P&gt;Why not just apply base configs to your JSON file and have it break correctly rather than trying to format the log to Splunk? &lt;/P&gt;

&lt;P&gt;If you let Splunk try to figure out the linebreaking, it will add additional overhead to your indexing and slow it down. &lt;/P&gt;

&lt;P&gt;Adding this will give you correct linebreaking and timestamping along with avoiding the merging pipeline which increases your indexing speed &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[sourcetype]
TIME_PREFIX = 
TIME_FORMAT = 
LINE_BREAKER = 
SHOULD_LINEMERGE = false
MAX_TIMESTAMP_LOOKAHEAD = 
TRUNCATE = 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="https://wiki.splunk.com/Community:HowIndexingWorks"&gt;https://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 15:09:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349923#M64236</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2018-01-30T15:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349924#M64237</link>
      <description>&lt;P&gt;@skoelpin, good question.&lt;/P&gt;

&lt;P&gt;We have teams that can form their json logs per the Splunk's needs. So, we are lucky in this sense.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 15:44:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349924#M64237</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-30T15:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349925#M64238</link>
      <description>&lt;P&gt;We were told by the Sales Engineer that as long as it's proper JSON, all we need to do is set -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;INDEXED_EXTRACTIONS = json
category = Structured
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in &lt;CODE&gt;props.conf&lt;/CODE&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 16:43:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349925#M64238</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-30T16:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349926#M64239</link>
      <description>&lt;P&gt;Your sales engineer is partially right, but you should ALWAYS apply base configs to lessen the indexer load when indexing data. This is a big part of the SCC2 bootcamp &lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 16:48:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349926#M64239</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2018-01-30T16:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349927#M64240</link>
      <description>&lt;P&gt;Much appreciated @skoelpin.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jan 2018 16:56:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349927#M64240</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-30T16:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349928#M64241</link>
      <description>&lt;P&gt;This solution works!!!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2018 00:21:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349928#M64241</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-02-02T00:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: What are the requirements for a perfect Splunk JSON document?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349929#M64242</link>
      <description>&lt;P&gt;For the record, the predefined _json sourcetype has these two defined config variables -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; INDEXED_EXTRACTIONS = json
 category = Structured
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 16 Mar 2018 01:19:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-requirements-for-a-perfect-Splunk-JSON-document/m-p/349929#M64242</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-03-16T01:19:35Z</dc:date>
    </item>
  </channel>
</rss>

