<?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: Playtime in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210776#M61531</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/18719"&gt;@jdprovine&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;It's technically viable to gather a&amp;nbsp;&lt;EM&gt;rough&lt;/EM&gt; estimate of how much time someone is spending on 'non-work' tasks depending on your configuration and how much you really want to trust the session information. I'm not going to get into the how because I don't believe that technology should be used to address human resource issues, and the information that can be gathered can be very inaccurate depending on what the user was doing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This isn't something that Palo Alto really supports without a bit of a work around and calculation of the proper traffic statistics. I would tell whoever is asking that it simply can't be done in an accurate manner.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Apr 2018 15:42:47 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2018-04-18T15:42:47Z</dc:date>
    <item>
      <title>Playtime</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210565#M61500</link>
      <description>&lt;P&gt;I know that I am not the only one who faces trying to track and minimize the amount of playing on the internet during regular work hours. Is there anyway to track and prove that a user is playing on the internet when they should be working using the PA?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Apr 2018 19:32:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210565#M61500</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-04-17T19:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: Playtime</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210738#M61520</link>
      <description>&lt;P&gt;By the response I got I am beginning to think this is either not possible or not done &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 13:24:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210738#M61520</guid>
      <dc:creator>jdprovine</dc:creator>
      <dc:date>2018-04-18T13:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Playtime</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210776#M61531</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/18719"&gt;@jdprovine&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;It's technically viable to gather a&amp;nbsp;&lt;EM&gt;rough&lt;/EM&gt; estimate of how much time someone is spending on 'non-work' tasks depending on your configuration and how much you really want to trust the session information. I'm not going to get into the how because I don't believe that technology should be used to address human resource issues, and the information that can be gathered can be very inaccurate depending on what the user was doing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This isn't something that Palo Alto really supports without a bit of a work around and calculation of the proper traffic statistics. I would tell whoever is asking that it simply can't be done in an accurate manner.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Apr 2018 15:42:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/playtime/m-p/210776#M61531</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-04-18T15:42:47Z</dc:date>
    </item>
  </channel>
</rss>

