<?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: How many log collectors can Panorama managed? in Panorama Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/panorama-discussions/how-many-log-collectors-can-panorama-managed/m-p/512333#M1074</link>
    <description>&lt;P&gt;Thanks for the post&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/209112"&gt;@darrenchew&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;since the latency between log collectors inside the same log collector group should be under 10 ms (Reference: &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmUnCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmUnCAK&lt;/A&gt;) and taking into consideration that all log collectors will be geographically separated over WAN, this leaves the only option to place each log collector into own log collector group. While documentation states that a collector group can have up to 16 log collectors, it does not say how many log collector groups are supported and total number log collectors that can be registered. I spent some time to search this information, but unfortunately I could not find it anywhere and have not found a reliable way to verify it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The scenario you described to have a log collector paired with each Firewall in branch site is non-standard design. To be honest, I think it is better to get a help from Palo Alto Professional Service to go over this design. I doubt that anybody in this community can give you any commitment on this setup. If your customer has enough budget to purchase 400+ log collectors, adding Professional Service should not make much difference &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am wondering, is there any reason why customer does not want to use Cortex Data Lake:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-started-with-cortex-data-lake/start-sending-logs-to-cortex-data-lake/start-sending-logs-to-cortex-data-lake-panorama-managed" target="_blank"&gt;https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-started-with-cortex-data-lake/start-sending-logs-to-cortex-data-lake/start-sending-logs-to-cortex-data-lake-panorama-managed&lt;/A&gt;&amp;nbsp; or why not centralize all log collectors in single or multiple Data Centers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
    <pubDate>Fri, 19 Aug 2022 01:23:20 GMT</pubDate>
    <dc:creator>PavelK</dc:creator>
    <dc:date>2022-08-19T01:23:20Z</dc:date>
    <item>
      <title>How many log collectors can Panorama managed?</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/how-many-log-collectors-can-panorama-managed/m-p/512064#M1067</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi Good day. Have some question wrt log collector.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Does anyone know how many log collectors can a pair of HA Panorama manage?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We have a customer who wants log collector to be distributed or the same location as the branch NGFW.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;They will be roughly 500+ branches and each with one unit of PA400 series. They want to have a dedicated log collector in each branch location to have high retention days storage. Means there will be 500+ NGFW and 400+ DLC that 1 pair of HA Panorama need to manage. Can this be supported? Thank you in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 03:39:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/how-many-log-collectors-can-panorama-managed/m-p/512064#M1067</guid>
      <dc:creator>darrenchew</dc:creator>
      <dc:date>2022-08-17T03:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: How many log collectors can Panorama managed?</title>
      <link>https://live.paloaltonetworks.com/t5/panorama-discussions/how-many-log-collectors-can-panorama-managed/m-p/512333#M1074</link>
      <description>&lt;P&gt;Thanks for the post&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/209112"&gt;@darrenchew&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;since the latency between log collectors inside the same log collector group should be under 10 ms (Reference: &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmUnCAK" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmUnCAK&lt;/A&gt;) and taking into consideration that all log collectors will be geographically separated over WAN, this leaves the only option to place each log collector into own log collector group. While documentation states that a collector group can have up to 16 log collectors, it does not say how many log collector groups are supported and total number log collectors that can be registered. I spent some time to search this information, but unfortunately I could not find it anywhere and have not found a reliable way to verify it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The scenario you described to have a log collector paired with each Firewall in branch site is non-standard design. To be honest, I think it is better to get a help from Palo Alto Professional Service to go over this design. I doubt that anybody in this community can give you any commitment on this setup. If your customer has enough budget to purchase 400+ log collectors, adding Professional Service should not make much difference &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am wondering, is there any reason why customer does not want to use Cortex Data Lake:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-started-with-cortex-data-lake/start-sending-logs-to-cortex-data-lake/start-sending-logs-to-cortex-data-lake-panorama-managed" target="_blank"&gt;https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-started-with-cortex-data-lake/start-sending-logs-to-cortex-data-lake/start-sending-logs-to-cortex-data-lake-panorama-managed&lt;/A&gt;&amp;nbsp; or why not centralize all log collectors in single or multiple Data Centers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2022 01:23:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/panorama-discussions/how-many-log-collectors-can-panorama-managed/m-p/512333#M1074</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2022-08-19T01:23:20Z</dc:date>
    </item>
  </channel>
</rss>

