<?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: session end reason = aged-out in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699327#M115875</link>
    <description>&lt;P&gt;From a cursive search, this seems to be an error associated with Palo Alto Firewalls. If this is an error message generated by a Palo Alto firewall, then you will likely find more relevant information on the Palo Alto docs or support forum.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Sep 2024 20:47:34 GMT</pubDate>
    <dc:creator>marnall</dc:creator>
    <dc:date>2024-09-17T20:47:34Z</dc:date>
    <item>
      <title>session end reason = aged-out</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699271#M115871</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What does&amp;nbsp;session end reason = &lt;STRONG&gt;aged-out&lt;/STRONG&gt; mean? We are facing one way audio issue. Could this be possibly a reason?&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2024 10:43:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699271#M115871</guid>
      <dc:creator>tnegi</dc:creator>
      <dc:date>2024-09-17T10:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: session end reason = aged-out</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699276#M115873</link>
      <description>&lt;P&gt;Where are you seeing that?&amp;nbsp; In what context?&lt;/P&gt;&lt;P&gt;Splunk doesn't process audio.&amp;nbsp; Please tell us more about the use case and the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2024 12:11:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699276#M115873</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2024-09-17T12:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: session end reason = aged-out</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699327#M115875</link>
      <description>&lt;P&gt;From a cursive search, this seems to be an error associated with Palo Alto Firewalls. If this is an error message generated by a Palo Alto firewall, then you will likely find more relevant information on the Palo Alto docs or support forum.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Sep 2024 20:47:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/session-end-reason-aged-out/m-p/699327#M115875</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-09-17T20:47:34Z</dc:date>
    </item>
  </channel>
</rss>

