<?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: Ingesting Cisco ISE logs - wrong timestamp in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417564#M7280</link>
    <description>&lt;P&gt;No, but you gave me an awesome idea! &lt;/P&gt;

&lt;P&gt;If we can't install the TA directly, we are a University and getting these installs takes some effort, then I will bust open the props.conf on the Cisco ISE TA and use those stanzas as first stab. &lt;/P&gt;

&lt;P&gt;Thanks for sparking that idea!&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jan 2019 17:26:51 GMT</pubDate>
    <dc:creator>montgomeryam</dc:creator>
    <dc:date>2019-01-22T17:26:51Z</dc:date>
    <item>
      <title>Ingesting Cisco ISE logs - wrong timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417562#M7278</link>
      <description>&lt;P&gt;Hello! &lt;/P&gt;

&lt;P&gt;We are trying to track down issues with ingesting UDP syslog data from Cisco ISE in which it is being indexed in the wrong year timestamp. What I can see is that the events are often being collected as far back as 1986. I understand that we can utilize a props.conf to configure timestamp recognition on events that are missing identifiable timestamps.&lt;/P&gt;

&lt;P&gt;Anyone else have this issue and were you able to fix it in props.conf?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jan 2019 17:11:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417562#M7278</guid>
      <dc:creator>montgomeryam</dc:creator>
      <dc:date>2019-01-22T17:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting Cisco ISE logs - wrong timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417563#M7279</link>
      <description>&lt;P&gt;Did you try to use the TA for cisco ise? its for collecting ise syslog data&lt;BR /&gt;
&lt;A href="https://splunkbase.splunk.com/app/1915/#/overview"&gt;https://splunkbase.splunk.com/app/1915/#/overview&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jan 2019 17:16:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417563#M7279</guid>
      <dc:creator>dkeck</dc:creator>
      <dc:date>2019-01-22T17:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting Cisco ISE logs - wrong timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417564#M7280</link>
      <description>&lt;P&gt;No, but you gave me an awesome idea! &lt;/P&gt;

&lt;P&gt;If we can't install the TA directly, we are a University and getting these installs takes some effort, then I will bust open the props.conf on the Cisco ISE TA and use those stanzas as first stab. &lt;/P&gt;

&lt;P&gt;Thanks for sparking that idea!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jan 2019 17:26:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417564#M7280</guid>
      <dc:creator>montgomeryam</dc:creator>
      <dc:date>2019-01-22T17:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting Cisco ISE logs - wrong timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417565#M7281</link>
      <description>&lt;P&gt;Happy to help. It would be great if you could accept the answer &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jan 2019 07:48:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Ingesting-Cisco-ISE-logs-wrong-timestamp/m-p/417565#M7281</guid>
      <dc:creator>dkeck</dc:creator>
      <dc:date>2019-01-24T07:48:38Z</dc:date>
    </item>
  </channel>
</rss>

