<?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: Report issue - incorrect data in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155682#M51171</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/53332"&gt;@DKanta&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your customer might be running into the 100K limit.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;100K&lt;/SPAN&gt; &lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt; is the current &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt; in report generation. The report generation performs the query in the 'backward" direction (search from the latest to the oldest log entry until hitting the &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;100K&lt;/SPAN&gt; &lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt;) :&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/Custom-Report-May-Not-Show-All-Data-Depending-on-Columns/ta-p/52158" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/Custom-Report-May-Not-Show-All-Data-Depending-on-Columns/ta-p/52158&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
    <pubDate>Tue, 09 May 2017 11:53:11 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2017-05-09T11:53:11Z</dc:date>
    <item>
      <title>Report issue - incorrect data</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155680#M51170</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i have a problem: when my customer generates reports there are problem with data, i see that the usage in one week is less than the sum of two random days in the same week.&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;Week report: 450.5 G bytes&lt;/P&gt;&lt;P&gt;Day X: 588.3 G bytes&lt;/P&gt;&lt;P&gt;Day Y: 262.0 G bytes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone some hints?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniele&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 11:05:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155680#M51170</guid>
      <dc:creator>DKanta</dc:creator>
      <dc:date>2017-05-09T11:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: Report issue - incorrect data</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155682#M51171</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/53332"&gt;@DKanta&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your customer might be running into the 100K limit.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;100K&lt;/SPAN&gt; &lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt; is the current &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt; in report generation. The report generation performs the query in the 'backward" direction (search from the latest to the oldest log entry until hitting the &lt;/SPAN&gt;&lt;SPAN class="lia-search-match-lithium"&gt;100K&lt;/SPAN&gt; &lt;SPAN class="lia-search-match-lithium"&gt;limit&lt;/SPAN&gt;&lt;SPAN&gt;) :&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Management-Articles/Custom-Report-May-Not-Show-All-Data-Depending-on-Columns/ta-p/52158" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Management-Articles/Custom-Report-May-Not-Show-All-Data-Depending-on-Columns/ta-p/52158&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 11:53:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155682#M51171</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2017-05-09T11:53:11Z</dc:date>
    </item>
    <item>
      <title>Re: Report issue - incorrect data</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155689#M51176</link>
      <description>&lt;P&gt;Yup, always fun to run into. That being said if you can try and limit the query to the point where it wouldn't hit this limit then that is ideal. Worst case scenario you generate the entire report on a day by day basis and then stitch it all together with some pdf merging to create one nice long week report. Hacky way of doing things but it at least presents the information that you need with a little more manual work on your end. &amp;nbsp; &amp;nbsp; &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 12:59:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/report-issue-incorrect-data/m-p/155689#M51176</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-05-09T12:59:22Z</dc:date>
    </item>
  </channel>
</rss>

