Related information
During Tracer operation, the system by default saves unprocessed events in a temporary file that is limited to 500 items. In some tracing situations, this can cause the display to lag behind the processing being traced, or cause the Tracer display to be incomplete or fail.
If the buffer overflows the limit of 500 items, Tracer processing ends. To avoid this condition, you can cause the system to save more events in the temporary file. (To prevent runaway or looping operations, the disk file mechanism also has a maximum size; the default is 50,000 unprocessed events.)
Note: Ensure that the disk device holding temporary files has available space for this and other files produced by Pega 7 Platform operations. If the disk is full or the Tracer is unable to open a temporary file, the user may be prompted to restart the Tracer, which then falls back to the in-memory buffer.
When this option is configured, the buffer for unprocessed events is much larger. The Tracer is unlikely to fail because unprocessed events have caused the buffer to overflow.
To adjust the size of the Tracer file buffer:
<env name="tracer/queue/type" value="file" />
<env name="tracer/queue/file/limit" value="nnnnn" />Note: As an alternative to updating the prconfig.xml file, you can use Dynamic System Settings to configure your application. See Prconfig settings and classifications.
To allow a file with no limit on the number of events, set the value in the second line to zero (0). Use this setting only when necessary, since an infinite loop in program execution might cause the file to consume all free space on the disk.