<?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: CheckPoint FW Logs from Manager with Two Timestamps in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90938#M18890</link>
    <description>&lt;P&gt;Couldn't put the answers to your questions in a comment.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Jan 2013 18:45:01 GMT</pubDate>
    <dc:creator>wbfoxii</dc:creator>
    <dc:date>2013-01-17T18:45:01Z</dc:date>
    <item>
      <title>CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90932#M18884</link>
      <description>&lt;P&gt;We are splunking logs from our CheckPoint FW.  The logs are delivered from the CheckPoint manager stations, not directly from the firewalls, so there are two timestamps - first from the management station and next from the FW.  We want to index based on the FW time.  Here's a typical record:&lt;/P&gt;

&lt;P&gt;Jan 17 16:47:31 aaa.bbb.178.200 fw1log: 17Jan2013 17:39:49 accept aaa.bbb.161.11 &amp;gt;eth2c13 rule: nnn; rule_ uid: {93622F88-3071-4FE4-BC7B-9B232AE482E6}; src: aaa.bbb.112.163; dst: aaa.bbb.4.35; proto: udp; product: VPN-1 &amp;amp; FireWall-1; service: 389; s_port: 3490;&lt;/P&gt;

&lt;P&gt;The time we want is 17Jan2013 17:39:49.&lt;/P&gt;

&lt;P&gt;I went into /etc/system/local/props.conf and added:&lt;/P&gt;

&lt;P&gt;TIME_PREFIX = fw1log:\s  &lt;/P&gt;

&lt;P&gt;TIME_FORMAT = %d%b%Y %H:%M:%S&lt;/P&gt;

&lt;P&gt;No luck getting this to use the second (correct) timestamp.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 16:01:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90932#M18884</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-17T16:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90933#M18885</link>
      <description>&lt;P&gt;Try this as your time prefix:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TIME_PREFIX = ^(?:(?:[^\s]+)\s){5}
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 17 Jan 2013 17:02:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90933#M18885</guid>
      <dc:creator>sbrant_splunk</dc:creator>
      <dc:date>2013-01-17T17:02:54Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90934#M18886</link>
      <description>&lt;P&gt;That didn't solve it.  I assume I can run a query with | extract reload=t at the end to get the new copy of props.conf active.  Checked the props list with btool and verified that this is the TIME_PREFIX being used.&lt;/P&gt;

&lt;P&gt;Time still matches the first one found.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 17:11:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90934#M18886</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-17T17:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90935#M18887</link>
      <description>&lt;P&gt;&lt;CODE&gt;extract reload=t&lt;/CODE&gt; was previously a way of reloading SEARCH-TIME properties from props.conf/transforms.conf. Nowadays you don't need that because each search is run in its own process which will read the current props/transforms settings when it starts.&lt;/P&gt;

&lt;P&gt;Index-time settings can however NOT be reloaded without restarting Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 17:17:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90935#M18887</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2013-01-17T17:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90936#M18888</link>
      <description>&lt;P&gt;I made a few assumptions about the props.conf.  Just to be sure, is the props.conf on the indexer?  Does the stanza for the checkpoint data have the correct name to match the sourcetype?  Can you post the entire stanza for checkpoint?  It's always best to be explicit.  Maybe something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[checkpoint]
TIME_PREFIX = ^(?:(?:[^\s]+)\s){5}
TIME_FORMAT = %d%b%Y %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 25
LINE_BREAKER = ([\r\n]+)
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 17 Jan 2013 17:20:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90936#M18888</guid>
      <dc:creator>sbrant_splunk</dc:creator>
      <dc:date>2013-01-17T17:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90937#M18889</link>
      <description>&lt;P&gt;Props.conf is on the indexer, which is also the search head.&lt;/P&gt;

&lt;P&gt;This is probably more than you want, but here's btool props list --debug&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
search     [checkpt_log]&lt;BR /&gt;
system     ANNOTATE_PUNCT = True&lt;BR /&gt;
system     BREAK_ONLY_BEFORE =&lt;BR /&gt;
system     BREAK_ONLY_BEFORE_DATE = True&lt;BR /&gt;
system     CHARSET = UTF-8&lt;BR /&gt;
system     DATETIME_CONFIG = /etc/datetime.xml&lt;BR /&gt;
system     HEADER_MODE =&lt;BR /&gt;
system     LEARN_SOURCETYPE = true&lt;BR /&gt;
system     LINE_BREAKER_LOOKBEHIND = 100&lt;BR /&gt;
system     MAX_DAYS_AGO = 2000&lt;BR /&gt;
system     MAX_DAYS_HENCE = 2&lt;BR /&gt;
system     MAX_DIFF_SECS_AGO = 3600&lt;BR /&gt;
system     MAX_DIFF_SECS_HENCE = 604800&lt;BR /&gt;
system     MAX_EVENTS = 256&lt;BR /&gt;
system     MAX_TIMESTAMP_LOOKAHEAD = 128&lt;BR /&gt;
system     MUST_BREAK_AFTER =&lt;BR /&gt;
system     MUST_NOT_BREAK_AFTER =&lt;BR /&gt;
system     MUST_NOT_BREAK_BEFORE =&lt;BR /&gt;
system     SEGMENTATION = indexing&lt;BR /&gt;
system     SEGMENTATION-all = full&lt;BR /&gt;
system     SEGMENTATION-inner = inner&lt;BR /&gt;
system     SEGMENTATION-outer = outer&lt;BR /&gt;
system     SEGMENTATION-raw = none&lt;BR /&gt;
system     SEGMENTATION-standard = standard&lt;BR /&gt;
system     SHOULD_LINEMERGE = True&lt;BR /&gt;
system     TIME_FORMAT = %d%b%Y %H:%M:%S&lt;BR /&gt;
system     TIME_PREFIX = ^(?:(?:[^\s]+)\s){5}&lt;BR /&gt;
system     TRANSFORMS =&lt;BR /&gt;
Splunk_Cis TRANSFORMS-force-sourcetype_for_cisco_devices = force_sourcetype_for_cisco_pix, force_sourcetype_for_cisco_asa, force_sourcetype_for_cisco_wap, fo&lt;BR /&gt;
rce_sourcetype_for_cisco_fwsm, force_sourcetype_for_cisco_acs, force_sourcetype_for_cisco_ios, force_sourcetype_for_cisco_catchall&lt;BR /&gt;
system     TRUNCATE = 10000&lt;BR /&gt;
system     maxDist = 100&lt;BR /&gt;
&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:07:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90937#M18889</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2020-09-28T13:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90938#M18890</link>
      <description>&lt;P&gt;Couldn't put the answers to your questions in a comment.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2013 18:45:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90938#M18890</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-17T18:45:01Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90939#M18891</link>
      <description>&lt;P&gt;TIME_PREFIX = ^(?:(?:[^\s]+)\s){5} is what is actually there.  I don't know why the formatter removed the  backslash in front of the s.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jan 2013 13:12:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90939#M18891</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-18T13:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90940#M18892</link>
      <description>&lt;P&gt;And even in this comment the backslash was removed.  I guess I don't know how to markup with Markdown&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jan 2013 13:14:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90940#M18892</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-18T13:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: CheckPoint FW Logs from Manager with Two Timestamps</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90941#M18893</link>
      <description>&lt;P&gt;I changed the time prefix setting to: &lt;BR /&gt;
&lt;PRE&gt;TIME_PREFIX = fw1log:\s&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;
(s has a backslash in front of it)&lt;/P&gt;

&lt;P&gt;I think there was a global setting from some other application for max timestamp lookahead that needed to be changed from the [default] stanza to a more specific stanza&lt;/P&gt;

&lt;P&gt;Anyway, now it is working.&lt;/P&gt;

&lt;P&gt;Many thanks to sbrant for keeping me on the right track.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Jan 2013 13:32:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CheckPoint-FW-Logs-from-Manager-with-Two-Timestamps/m-p/90941#M18893</guid>
      <dc:creator>wbfoxii</dc:creator>
      <dc:date>2013-01-18T13:32:57Z</dc:date>
    </item>
  </channel>
</rss>

