<?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: Why is the Symantec time_format not working? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317632#M59386</link>
    <description>&lt;P&gt;Sorry, I did leave out the hour.  I've corrected my answer.&lt;/P&gt;</description>
    <pubDate>Sat, 03 Mar 2018 20:28:30 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2018-03-03T20:28:30Z</dc:date>
    <item>
      <title>Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317628#M59382</link>
      <description>&lt;P&gt;I am trying to set the time format from our Symantec events to the value of 'occurred_on' in my props.conf.&lt;/P&gt;

&lt;P&gt;here is the event string:&lt;BR /&gt;
",occurred_on="March 2, 2018 6:50:14 AM",&lt;/P&gt;

&lt;P&gt;here is how time is displayed:&lt;BR /&gt;
3/2/18&lt;BR /&gt;
6:50:27.000 AM&lt;/P&gt;

&lt;P&gt;Here is my props.conf:&lt;/P&gt;

&lt;P&gt;[symantec]&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = occurred_on=\"([A-Za-z]+\s\d{1,2},\s\d{4}\s\d{1,2}:\d{1,2}:\d{1,2})
TIME_FORMAT = %B %d, %Y %H:%M:%S
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I changed the time_prefix last night to what it was. I did have it earlier as [A-Za-z\s,0-9:]+&lt;BR /&gt;&lt;BR /&gt;
each of these expressions worked in regex101, I changed to what it is now because I only wanted to grab the time minus the am\pm.&lt;/P&gt;

&lt;P&gt;I have deployed and also restarted splunk on my devices.  &lt;/P&gt;

&lt;P&gt;any thought on what I am doing wrong or even how to debug these.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2018 12:21:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317628#M59382</guid>
      <dc:creator>pfabrizi</dc:creator>
      <dc:date>2018-03-02T12:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317629#M59383</link>
      <description>&lt;P&gt;The &lt;CODE&gt;TIME_PREFIX&lt;/CODE&gt; attribute should contain a regular expression describing what comes &lt;EM&gt;before&lt;/EM&gt; the timestamp.  In your case it should be &lt;CODE&gt;TIME_PREFIX = occurred_on=\"&lt;/CODE&gt;.&lt;BR /&gt;
Your &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; setting doesn't quite match your sample event.  Try &lt;CODE&gt;%B %d, %Y %H:%M:%S %p&lt;/CODE&gt;.  If you leave out the "%p", Splunk will interpret "6:50:27 AM" and "6:50:27 PM" as 06:50:27, which probably is not what you want.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2018 18:20:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317629#M59383</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2018-03-02T18:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317630#M59384</link>
      <description>&lt;P&gt;can you explain what the %Y:%M:%S is?&lt;/P&gt;

&lt;P&gt;I thought %M and %S where minutes and seconds?&lt;BR /&gt;&lt;BR /&gt;
What about the hour?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2018 19:36:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317630#M59384</guid>
      <dc:creator>pfabrizi</dc:creator>
      <dc:date>2018-03-02T19:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317631#M59385</link>
      <description>&lt;P&gt;this is not working. &lt;/P&gt;

&lt;P&gt;I am still seeing the time off, &lt;/P&gt;

&lt;P&gt;occurred_on="March 2, 2018 3:22:10 PM" &lt;BR /&gt;
is showing as   3:22:16 000 PM&lt;/P&gt;

&lt;P&gt;so there is a 6+ second difference.&lt;/P&gt;

&lt;P&gt;the text occurred_on starts at position 1165 and ends around 1204. Does this create an issue?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Mar 2018 20:30:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317631#M59385</guid>
      <dc:creator>pfabrizi</dc:creator>
      <dc:date>2018-03-02T20:30:01Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317632#M59386</link>
      <description>&lt;P&gt;Sorry, I did leave out the hour.  I've corrected my answer.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 20:28:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317632#M59386</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2018-03-03T20:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317633#M59387</link>
      <description>&lt;P&gt;As per the &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Commontimeformatvariables"&gt;date and time format variable documentation&lt;/A&gt; , I think your TIME_FORMAT is close but not quite right!&lt;/P&gt;

&lt;P&gt;Try:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_FORMAT = %B %e, %Y %I:%M:%S %p
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I'm not 100% sure that is correct but I think it's closer...your splunkd log files should inform you if the timestamp parsing is not working as expected&lt;/P&gt;

&lt;P&gt;From the documentation:&lt;BR /&gt;
%e "Like %d, the day of the month as a decimal number, but a leading zero is replaced by a space. (1 to 31) "&lt;BR /&gt;
%I "Hour (12-hour clock) with the hours represented by the values 01 to 12. Leading zeros are accepted but not required. "&lt;/P&gt;</description>
      <pubDate>Sun, 04 Mar 2018 00:35:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317633#M59387</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2018-03-04T00:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317634#M59388</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Dio you recommend the trouble shooting class? Will that help with this stuff?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 13:55:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317634#M59388</guid>
      <dc:creator>pfabrizi</dc:creator>
      <dc:date>2018-03-05T13:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the Symantec time_format not working?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317635#M59389</link>
      <description>&lt;P&gt;Which troubleshooting class? I'd recommend reading the splunkd logs carefully, I even built an application to detect various errors in the logs called &lt;A href="https://splunkbase.splunk.com/app/3796/"&gt;Alerts For Splunk Admins&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Although in this case the alerts would just find the date parsing not working, the documentation for Splunk is also quite useful here...&lt;/P&gt;</description>
      <pubDate>Mon, 05 Mar 2018 21:27:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-Symantec-time-format-not-working/m-p/317635#M59389</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2018-03-05T21:27:27Z</dc:date>
    </item>
  </channel>
</rss>

