<?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: Best parameters for ingesting JSON logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628146#M107808</link>
    <description>&lt;P&gt;We can't validate your props.conf settings without seeing some sample data.&amp;nbsp; However, AIUI, the &lt;FONT face="courier new,courier"&gt;TIMESTAMP_FIELDS&lt;/FONT&gt; setting applies only when &lt;FONT face="courier new,courier"&gt;INDEXED_EXTRACTIONS&lt;/FONT&gt; is used so I'd use &lt;FONT face="courier new,courier"&gt;TIME_PREFIX&lt;/FONT&gt;.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Jan 2023 14:00:04 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-01-24T14:00:04Z</dc:date>
    <item>
      <title>What are the best parameters for ingesting JSON logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628145#M107807</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;which method is best, using TIME_PREFIX = timestamp":" or TIMESTAMP_FIELDS = @timestamp?&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.2/Data/Configuretimestamprecognition#Examples" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.2/Data/Configuretimestamprecognition#Examples&lt;/A&gt; does not talk about TIMESTAMP_FIELDS&lt;/P&gt;
&lt;P&gt;We are using this parameter for another JSON source and it works fine too.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;Examples :

UF side :
etc/deployment-apps/_server_app_LBA_ZZZ_LX/local/props.conf
[ZZZ_metrics_json]
TIMESTAMP_FIELDS = start (useless in my opinion as should only run on indexers side?)
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3N.%z  (useless in my opinion as should only run on indexers side?)
INDEXED_EXTRACTIONS = json

etc/deployment-apps/_server_app_LBA_MIC_SUP/local/props.conf
[VVV:sup:json]
INDEXED_EXTRACTIONS = json

IDXC side :
[siem@s301lbasplmgt2 ~]$ cat /OPT/siem/splunk/etc/master-apps/APP_PROPS/local/props.conf

[ZZZ_metrics_json]
TIMESTAMP_FIELDS = start
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3N.%z

etc/master-apps/XXX_VVV_PROPS/default/props.conf
[VVV:sup:json]
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3N.%z
TIME_PREFIX = timestamp":"
MAX_TIMESTAMP_LOOKAHEAD = 50


SHC side:
etc/shcluster/apps/XXX_VVV_PROPS/default/props.conf
[VVV:sup:json]
KV_MODE = none

etc/shcluster/apps/APP_YYY_parser_json/default/props.conf
[ZZZ_metrics_json]
KV_MODE = none
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 15:13:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628145#M107807</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2023-01-24T15:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: Best parameters for ingesting JSON logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628146#M107808</link>
      <description>&lt;P&gt;We can't validate your props.conf settings without seeing some sample data.&amp;nbsp; However, AIUI, the &lt;FONT face="courier new,courier"&gt;TIMESTAMP_FIELDS&lt;/FONT&gt; setting applies only when &lt;FONT face="courier new,courier"&gt;INDEXED_EXTRACTIONS&lt;/FONT&gt; is used so I'd use &lt;FONT face="courier new,courier"&gt;TIME_PREFIX&lt;/FONT&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 14:00:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628146#M107808</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-24T14:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best parameters for ingesting JSON logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628182#M107814</link>
      <description>&lt;P&gt;It's simple JSON standard format with @timestamp field, I could upload anonymized sample data if needed &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So I understand&amp;nbsp;INDEXED_EXTRACTIONS = json is not necessary if I use TIME_PREFIX and I could maybe save disk space/performances not indexing fields at indexing phase (as read at &lt;A href="https://community.splunk.com/t5/Splunk-Search/What-are-the-possible-gains-from-an-index-time-extraction-of-a/m-p/212017" target="_blank"&gt;https://community.splunk.com/t5/Splunk-Search/What-are-the-possible-gains-from-an-index-time-extraction-of-a/m-p/212017&lt;/A&gt;)?&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 17:52:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628182#M107814</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2023-01-24T17:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: Best parameters for ingesting JSON logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628185#M107816</link>
      <description>&lt;P&gt;Yes, &lt;FONT face="courier new,courier"&gt;INDEXED_EXTRACTIONS&lt;/FONT&gt; will use more storage as well as index-time CPU..&amp;nbsp; If you don't need every field from the JSON indexed then either use &lt;FONT face="courier new,courier"&gt;KV_MODE=json&lt;/FONT&gt; or extract the desired fields using &lt;FONT face="courier new,courier"&gt;EXTRACT&lt;/FONT&gt; or SPL commands.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jan 2023 18:40:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628185#M107816</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-24T18:40:38Z</dc:date>
    </item>
    <item>
      <title>Re: Best parameters for ingesting JSON logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628254#M107834</link>
      <description>&lt;P&gt;Hi Rich,&lt;/P&gt;&lt;P&gt;that worked however I had to add SHOULD_LINEMERGE = false in indexers props.conf because our have several events at the same millisecond.&lt;/P&gt;&lt;P&gt;To sum up, on UF side no props.conf&lt;/P&gt;&lt;P&gt;On IDXC :&lt;/P&gt;&lt;P&gt;TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3N.%z&lt;BR /&gt;TIME_PREFIX = timestamp":"&lt;BR /&gt;MAX_TIMESTAMP_LOOKAHEAD = 50&lt;BR /&gt;SHOULD_LINEMERGE = false&lt;/P&gt;&lt;P&gt;on SHC&amp;nbsp; (app with global context) :&lt;/P&gt;&lt;P&gt;KV_MODE = json&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2023 10:18:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-best-parameters-for-ingesting-JSON-logs/m-p/628254#M107834</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2023-01-25T10:18:35Z</dc:date>
    </item>
  </channel>
</rss>

