<?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: How to recognize event time that is embedded in json string in epoch seconds? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57511#M11237</link>
    <description>&lt;P&gt;That is basically right, but first, is this all on a single Splunk instance (no forwarder)? You should try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = \"createTime\"\:
TIME_FORMAT = %10s%3N
MAX_TIMESTAMP_LOOKAHEAD = 15
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;instead of what you have above. I think the &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt; you have should work anyway, but that the &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; might not be taking because &lt;CODE&gt;%s&lt;/CODE&gt; is expecting epoch seconds, and your timestamp is milliseconds, which puts the date about 40,000 years in the future, which is outside of Splunk's default sanity limit. You might want to also try &lt;CODE&gt;%s%3N&lt;/CODE&gt; for your &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; if the above doesn't work, or if you have dates either before Sep 8 2001 (9 digits) or dates after 2286.&lt;/P&gt;</description>
    <pubDate>Fri, 12 Aug 2011 20:22:56 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2011-08-12T20:22:56Z</dc:date>
    <item>
      <title>How to recognize event time that is embedded in json string in epoch seconds?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57510#M11236</link>
      <description>&lt;P&gt;I'm using "From files and directories" --&amp;gt; "Upload and index a file" to feed the data file. The file has data in following format.&lt;/P&gt;

&lt;P&gt;{ "_id": { "$oid": "4b97ca22729772ec85d48fc0"}, "subscriberId": "C10000235", "createTime": 1268238882453, "serviceGroup": "SGID0001", "sessionProtocolIndicator": null,    "networkProxyId": "PROXY_001" }&lt;/P&gt;

&lt;P&gt;Search shows the following basic information:&lt;BR /&gt;
host=srinidev   sourcetype=sds3   source=sds3.out&lt;/P&gt;

&lt;P&gt;How can I get splunk (using 4.2.3) to recognize 1268238882453 as the date and use it as event time?&lt;/P&gt;

&lt;P&gt;I added a $SPLUNK_HOME/etc/local/props.conf file with these lines:&lt;/P&gt;

&lt;P&gt;[sds3]&lt;/P&gt;

&lt;P&gt;TIME_PREFIX = createTime&lt;/P&gt;

&lt;P&gt;TIME_FORMAT = %s&lt;/P&gt;

&lt;P&gt;I also added $SPLUNK_HOME/etc/apps/search/input.conf, but with not much success.&lt;/P&gt;

&lt;P&gt;Any help is greatly appreciated. Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:47:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57510#M11236</guid>
      <dc:creator>skericsson</dc:creator>
      <dc:date>2020-09-28T09:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to recognize event time that is embedded in json string in epoch seconds?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57511#M11237</link>
      <description>&lt;P&gt;That is basically right, but first, is this all on a single Splunk instance (no forwarder)? You should try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = \"createTime\"\:
TIME_FORMAT = %10s%3N
MAX_TIMESTAMP_LOOKAHEAD = 15
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;instead of what you have above. I think the &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt; you have should work anyway, but that the &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; might not be taking because &lt;CODE&gt;%s&lt;/CODE&gt; is expecting epoch seconds, and your timestamp is milliseconds, which puts the date about 40,000 years in the future, which is outside of Splunk's default sanity limit. You might want to also try &lt;CODE&gt;%s%3N&lt;/CODE&gt; for your &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; if the above doesn't work, or if you have dates either before Sep 8 2001 (9 digits) or dates after 2286.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2011 20:22:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57511#M11237</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-08-12T20:22:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to recognize event time that is embedded in json string in epoch seconds?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57512#M11238</link>
      <description>&lt;P&gt;Thanks. Still having trouble. So is etc/apps/search/input.conf necessary. I added following lines to that file. &lt;/P&gt;

&lt;P&gt;[monitor:///home/test/data/session_data.out]&lt;/P&gt;

&lt;P&gt;sourcetype = sds3&lt;/P&gt;</description>
      <pubDate>Sat, 13 Aug 2011 13:19:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-recognize-event-time-that-is-embedded-in-json-string-in/m-p/57512#M11238</guid>
      <dc:creator>skericsson</dc:creator>
      <dc:date>2011-08-13T13:19:12Z</dc:date>
    </item>
  </channel>
</rss>

