Avoid performance issues when monitoring applications with size limit for Tracer files (8.6)
You can now monitor and debug your applications without experiencing high disk usage issues because Tracer generates event files that have a maximum size of 10 GB. The file size limit prevents your system from using excessive disk space so that your applications can operate without any interruptions. To support a wide range of use cases, the file size limit applies to the following systems:
- on-premises Pega Platform™ deployments
- Pega Cloud® deployments
- deployments of Pega Platform on client-managed clouds
The file size limit is node-wide, which means that every node in your system can use up to 10 GB of disk space for the Tracer file. If you run multiple Tracer sessions on one node, the sessions share the 10 GB limit. When one of the sessions exceeds the 10 GB file size, the session stops, while the system deletes the relevant Tracer file and reclaims the disk space. To deliver essential information even after resetting the file size limit, you can still download a file with error messages that occurred during the Tracer session.
For example, if you have two Tracer sessions, S1 and S2, that run on one node, and S1 uses 8 GB, S2 can use up to 2 GB before the session S2 stops and the system deletes the file.
The following figure shows a Tracer window that includes information about a failed Tracer session as a result of an exceeded file size limit:
To meet your unique business needs, you can adjust the file size limit.
For more information, see Tracer disk usage FAQ and PEGA0129 alert: Tracer file limit reached.
Previous topic Debug your Cosmos React applications faster with Tracer (8.6) Next topic Link objects in your application conveniently with fields to capture data (8.6)