<?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 Logs are delayed for Symantec logs, why? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127057#M10109</link>
    <description>&lt;P&gt;The delay appears to be up to 15 minutes   The delay is with the Symantec logs (sourcetype values:  sep, sep:agt_system, sep:ids, and sep:behavior)&lt;/P&gt;

&lt;P&gt;The delay is also inconsistent, meaning there are times where the logs are not delayed.&lt;BR /&gt;
Has anyone seen this before?&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jul 2015 16:09:27 GMT</pubDate>
    <dc:creator>MikeBertelsen</dc:creator>
    <dc:date>2015-07-16T16:09:27Z</dc:date>
    <item>
      <title>Logs are delayed for Symantec logs, why?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127057#M10109</link>
      <description>&lt;P&gt;The delay appears to be up to 15 minutes   The delay is with the Symantec logs (sourcetype values:  sep, sep:agt_system, sep:ids, and sep:behavior)&lt;/P&gt;

&lt;P&gt;The delay is also inconsistent, meaning there are times where the logs are not delayed.&lt;BR /&gt;
Has anyone seen this before?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2015 16:09:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127057#M10109</guid>
      <dc:creator>MikeBertelsen</dc:creator>
      <dc:date>2015-07-16T16:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: Logs are delayed for Symantec logs, why?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127058#M10110</link>
      <description>&lt;P&gt;For clarification, Symantec logs are delayed getting into Splunk.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2015 16:11:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127058#M10110</guid>
      <dc:creator>MikeBertelsen</dc:creator>
      <dc:date>2015-07-16T16:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Logs are delayed for Symantec logs, why?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127059#M10111</link>
      <description>&lt;P&gt;If the "delay" is only 15 minutes, then I would guess that at least one of the servers that is generating the timestamps inside of the events has significant clock drift.  You can see which one with this search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* | eval timestamp=coalesce(timestamp,"OK") | eval date_zone=coalesce(date_zone,"none") | eval prev_sourcetype=if(sourcetype=$_sourcetype$,"none",_sourcetype) | dedup date_zone splunk_server index host sourcetype timestamp prev_sourcetype | eval lagSecs=_time-_indextime
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Find the &lt;CODE&gt;host&lt;/CODE&gt; values that have bad &lt;CODE&gt;lagSecs&lt;/CODE&gt; times.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2015 16:15:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Logs-are-delayed-for-Symantec-logs-why/m-p/127059#M10111</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-07-16T16:15:52Z</dc:date>
    </item>
  </channel>
</rss>

