topic Re: XDR Agent Quota Exceeded in Cortex XDR Discussions

XDR Agent Quota Exceeded

T.Kepinski — Mon, 02 Jun 2025 16:37:34 GMT

Hello,

We receive numerous alerts of "XDR agent quota exceeded on ****"

I understand this means that the default storage is being exceeded but what exactly does that entail?

1. Are the old logs not being overwritten in time causing the alert to set off since the space has been exceeded? is it actually going over the default space or is there a hard stop where logs wont be collected?

2. Does cortex generate this alert any time an old log is overwritten?

3. Is there anyway to stop these alerts from happening without increasing the storage space?

Re: XDR Agent Quota Exceeded

mavega — Tue, 03 Jun 2025 16:46:24 GMT

Hi,

Thanks reaching out LV.

This message usually refers to the agent quota setting that is defined in the agent settings profile, being the default disk space allocated for agent logs is 5000MB, you can increase it up to 10,000 by creating a new agent settings profile.

Older logs will be overwritten but not all them at the same time.

If you feel this resolved your doubt, please mark is as solution.

Re: XDR Agent Quota Exceeded

T.Kepinski — Mon, 09 Jun 2025 14:30:16 GMT

We have deleted the old logs out of the system but we are still receiving the alerts. Is there a way to fix the "agent quota exceeded" without increasing the disk space?

Re: XDR Agent Quota Exceeded

Alex.Gerulaitis — Thu, 02 Jul 2026 20:44:45 GMT

Would anyone know the answer to this?

2. Does cortex generate this alert any time an old log is overwritten?

... and to this:

Does this condition (of exceeding the "quota" result in any negative impact on functionality or performance, such as failure to generate alerts and incidents? (Which may be the case in our environment thanks to inexplicable such failures.)

Thanks!

Re: XDR Agent Quota Exceeded

susekar — Mon, 06 Jul 2026 13:22:03 GMT

Hello @T.Kepinski ,

Greetings for the day.

The "XDR Agent quota exceeded" alert indicates that the local storage allocated for the agent's security data—such as forensic data, quarantined files, and EDR telemetry—has reached its configured limit.

1. Log Overwriting and Data Collection

When the quota is reached, the agent operates on a First-In, First-Out (FIFO) basis, automatically deleting the oldest data to make room for new data.

Is it a hard stop?
Not initially. The agent continues to protect the endpoint even after the quota is exceeded. However, if data is generated faster than it can be purged, or if communication issues prevent the agent from uploading data to the management console, the agent may enter a PARTIALLY_PROTECTED state and stop collecting EDR data.
Purge Delay:
By default, the agent checks and enforces the directory quota every 1 hour. If a large amount of data is generated before the next scheduled purge cycle, the quota exceeded alert may be triggered.

2. Alert Generation

The alert is generated to notify administrators that the agent has reached its configured storage limit and is actively enforcing its internal quota by pruning older data. This is expected behavior and serves as an informational notification.

3. Managing Alerts Without Increasing Storage

If you prefer not to increase the disk quota, consider the following approaches:

Policy Tuning:
Review high-frequency detections or processes generating excessive data and tune the relevant security profiles or allow trusted files where appropriate to reduce unnecessary logging.
Alert Exclusions:
Create an alert exclusion rule for the "Quota Exceeded" alert if you want to suppress these notifications from appearing in the console.
Forced Cleanup:
Temporarily reduce the configured disk quota (for example, to 100 MB) to force the agent to immediately purge older data. Once cleanup is complete, restore the original quota value.
Manual Cleanup (Windows):
If required, you can manually clear the prevention archive after disabling self-protection.

Disable file protection:"C:\Program Files\Palo Alto Networks\Traps\cytool" protect disable file

Delete the files under:C:\ProgramData\Cyvera\Prevention

Re-enable file protection:"C:\Program Files\Palo Alto Networks\Traps\cytool" protect enable file

-To verify the current event collection status and disk usage, run:"C:\Program Files\Palo Alto Networks\Traps\cytool" event_collection query

Note: If the issue persists despite these steps, we recommend opening a support case for further investigation and analysis of the agent logs.

If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".

Thanks & Regards,
S. Subashkar Sekar

Re: XDR Agent Quota Exceeded

Alex.Gerulaitis — Mon, 06 Jul 2026 13:29:12 GMT

AI response? (A wall of pretty text not really answering the question.)

(Yes, I easily get grumpy... lol)