<?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: Indexing JSON data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320952#M59889</link>
    <description>&lt;P&gt;I agree with what @aakwah wrote but a bad props.conf file is not going to stop data from coming in (although it may come in "wrong").  We need to see your inputs.conf file.  When you make changes to input.conf, you must restart the forwarder's splunk instance.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 13:35:30 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-06-01T13:35:30Z</dc:date>
    <item>
      <title>Indexing JSON data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320950#M59887</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I created a sourcetype (props.conf) to parse my json files. A local input (index once)  was created only to test the props.conf and it works fine!&lt;BR /&gt;
When I tried to create a continuously monitor file the events didn't appear in Splunk. I tried to monitor the entire folder (*.json) and a specific json file.&lt;BR /&gt;
Has anyone had something similar?&lt;/P&gt;

&lt;P&gt;follow my props.conf&lt;/P&gt;

&lt;P&gt;[json_mention]&lt;BR /&gt;
TRUNCATE = 0&lt;BR /&gt;
BREAK_ONLY_BEFORE_DATE = false&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;BR /&gt;
LINE_BREAKER = ({\s+"location":)&lt;BR /&gt;
MUST_BREAK_AFTER = {\s+"location":&lt;BR /&gt;
TIME_FORMAT=%Y-%m-%d %H:%M:%S&lt;BR /&gt;
TIME_PREFIX=({\s+"collected_at":\s+")&lt;BR /&gt;
MAX_TIMESTAMP_LOOKAHEAD=20&lt;/P&gt;

&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:16:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320950#M59887</guid>
      <dc:creator>monteirolopes</dc:creator>
      <dc:date>2020-09-29T14:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing JSON data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320951#M59888</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;For json objects extraction you can make use of  &lt;CODE&gt;INDEXED_EXTRACTIONS&lt;/CODE&gt;, the following stanza should work fine.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; [json_mention]
 INDEXED_EXTRACTIONS = json
 KV_MODE = none
 LEARN_MODEL = false
 TRUNCATE = 0
 category = Structured
 description = JavaScript Object Notation format.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please note that &lt;CODE&gt;INDEXED_EXTRACTIONS&lt;/CODE&gt; should be applied at input time, when data is first read by Splunk.&lt;/P&gt;

&lt;P&gt;Check props.conf doc for more details:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.0/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.0/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 29 May 2017 13:12:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320951#M59888</guid>
      <dc:creator>aakwah</dc:creator>
      <dc:date>2017-05-29T13:12:15Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing JSON data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320952#M59889</link>
      <description>&lt;P&gt;I agree with what @aakwah wrote but a bad props.conf file is not going to stop data from coming in (although it may come in "wrong").  We need to see your inputs.conf file.  When you make changes to input.conf, you must restart the forwarder's splunk instance.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 13:35:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-JSON-data/m-p/320952#M59889</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-06-01T13:35:30Z</dc:date>
    </item>
  </channel>
</rss>

