topic Re: PC Compute License information is missing in Prisma Cloud Discussions

PC Compute License information is missing

cm-patterson — Wed, 02 Jul 2025 14:08:47 GMT

Hi,

Our license usage is always incorrect (missing). This has been an issue as far back as I can remember (n-3 versions?). I can tell you that the licensing information from the API is the same (missing). Any idea what the cause is and how to fix it?

Re: PC Compute License information is missing

WLejulus — Thu, 03 Jul 2025 16:01:38 GMT

Hello Cm-Patterson,

Is this licensing issue occurring in a self-hosted console or Saas tenant?

We will need some further details about your console that should not be shared here. Can you please open a ticket with our support team to look further into this.

Regards,

Re: PC Compute License information is missing

cm-patterson — Thu, 03 Jul 2025 16:20:22 GMT

Prisma Cloud Compute - self hosted.

Re: PC Compute License information is missing

LMegrelis — Thu, 10 Jul 2025 14:19:54 GMT

Hello! I may have a theory as to why the 0 is displayed.

When are the license credits consumed for the 'Agentless Scan' function?

The agentless credit usage is calculated when a scan function has completed and is based on the count of total hosts/VMs that are scanned. If user just enables agentless and no scan is done, then no credits are charged.

How are credits calculated for Agentless Scanning if defender is deployed?

The image can be configured to be scanned with both Agentless and Defender, though Agentless scan is skipped if defender is deployed. As we charge Agentless credits only when scan is completed and not just that its configured, Agentless Scanning credits would not be calculated for a host/container if a defender is deployed.

Please let me know if you have any additional questions and I will happily assist.

Re: PC Compute License information is missing

cm-patterson — Thu, 10 Jul 2025 16:57:12 GMT

The response I received from Palo Alto is that this is / was a known issue up until major PCC release 34. I'm not able to test this at present, as my k8s cluster is not compatible with the latest version of PCC.