<?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: Automatic JSON log extraction in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Automatic-JSON-log-extraction/m-p/296280#M93044</link>
    <description>&lt;P&gt;Hi deepak02!&lt;/P&gt;

&lt;P&gt;Splunk has both indexed extractions and searchtime extractions for json. &lt;/P&gt;

&lt;P&gt;They are found in props.conf. &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;INDEXED_EXTRACTIONS = &amp;lt; CSV|W3C|TSV|PSV|JSON &amp;gt;
* Tells Splunk the type of file and the extraction and/or parsing method
  Splunk should use on the file.
  CSV  - Comma separated value format
  TSV  - Tab-separated value format
  PSV  - pipe "|" separated value format
  W3C  - W3C Extended Extended Log File Format
  JSON - JavaScript Object Notation format
* These settings default the values of the remaining settings to the
  appropriate values for these known formats.
* Defaults to unset.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;*If you are using a forwarder, be sure to put the props.conf on the forwarder! not just the indexer!&lt;/P&gt;

&lt;P&gt;Also as an FYI, Splunk has a searchtime extractions available:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;KV_MODE = [none|auto|auto_escaped|multi|json|xml]
* Used for search-time field extractions only.
* Specifies the field/value extraction mode for the data.
* Set KV_MODE to one of the following:
  * none: if you want no field/value extraction to take place.
  * auto: extracts field/value pairs separated by equal signs.
  * auto_escaped: extracts fields/value pairs separated by equal signs and
                  honors \" and \\ as escaped sequences within quoted
                  values, e.g field="value with \"nested\" quotes"
  * multi: invokes the multikv search command to expand a tabular event into
           multiple events.
  * xml : automatically extracts fields from XML data.
  * json: automatically extracts fields from JSON data.
* Setting to 'none' can ensure that one or more user-created regexes are not
  overridden by automatic field/value extraction for a particular host,
  source, or source type, and also increases search performance.
* Defaults to auto.
* The 'xml' and 'json' modes will not extract any fields when used on data
  that isn't of the correct format (JSON or XML).
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;OR&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;AUTO_KV_JSON = [true|false]
* Used for search-time field extractions only.
* Specifies whether to try json extraction automatically.
* Defaults to true.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What ever way you decide, I encourage you to try a sample of your json using the Add Data wizard, to ensure you are getting the extractions you expect. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Data/Setsourcetype"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Data/Setsourcetype&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Mar 2017 17:49:21 GMT</pubDate>
    <dc:creator>mattymo</dc:creator>
    <dc:date>2017-03-28T17:49:21Z</dc:date>
    <item>
      <title>Automatic JSON log extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Automatic-JSON-log-extraction/m-p/296279#M93043</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am uploading logs in JSON format into Splunk.&lt;/P&gt;

&lt;P&gt;I want to enable automatic field extraction. &lt;/P&gt;

&lt;P&gt;Is there any setting for this, or does Splunk always enable automatic field extraction by default?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Deepak&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 17:35:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Automatic-JSON-log-extraction/m-p/296279#M93043</guid>
      <dc:creator>deepak02</dc:creator>
      <dc:date>2017-03-28T17:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Automatic JSON log extraction</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Automatic-JSON-log-extraction/m-p/296280#M93044</link>
      <description>&lt;P&gt;Hi deepak02!&lt;/P&gt;

&lt;P&gt;Splunk has both indexed extractions and searchtime extractions for json. &lt;/P&gt;

&lt;P&gt;They are found in props.conf. &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Admin/Propsconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;INDEXED_EXTRACTIONS = &amp;lt; CSV|W3C|TSV|PSV|JSON &amp;gt;
* Tells Splunk the type of file and the extraction and/or parsing method
  Splunk should use on the file.
  CSV  - Comma separated value format
  TSV  - Tab-separated value format
  PSV  - pipe "|" separated value format
  W3C  - W3C Extended Extended Log File Format
  JSON - JavaScript Object Notation format
* These settings default the values of the remaining settings to the
  appropriate values for these known formats.
* Defaults to unset.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;*If you are using a forwarder, be sure to put the props.conf on the forwarder! not just the indexer!&lt;/P&gt;

&lt;P&gt;Also as an FYI, Splunk has a searchtime extractions available:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;KV_MODE = [none|auto|auto_escaped|multi|json|xml]
* Used for search-time field extractions only.
* Specifies the field/value extraction mode for the data.
* Set KV_MODE to one of the following:
  * none: if you want no field/value extraction to take place.
  * auto: extracts field/value pairs separated by equal signs.
  * auto_escaped: extracts fields/value pairs separated by equal signs and
                  honors \" and \\ as escaped sequences within quoted
                  values, e.g field="value with \"nested\" quotes"
  * multi: invokes the multikv search command to expand a tabular event into
           multiple events.
  * xml : automatically extracts fields from XML data.
  * json: automatically extracts fields from JSON data.
* Setting to 'none' can ensure that one or more user-created regexes are not
  overridden by automatic field/value extraction for a particular host,
  source, or source type, and also increases search performance.
* Defaults to auto.
* The 'xml' and 'json' modes will not extract any fields when used on data
  that isn't of the correct format (JSON or XML).
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;OR&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;AUTO_KV_JSON = [true|false]
* Used for search-time field extractions only.
* Specifies whether to try json extraction automatically.
* Defaults to true.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What ever way you decide, I encourage you to try a sample of your json using the Add Data wizard, to ensure you are getting the extractions you expect. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Data/Setsourcetype"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Data/Setsourcetype&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2017 17:49:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Automatic-JSON-log-extraction/m-p/296280#M93044</guid>
      <dc:creator>mattymo</dc:creator>
      <dc:date>2017-03-28T17:49:21Z</dc:date>
    </item>
  </channel>
</rss>

