When taking a snapshot of the variable values in a specific error or exception, OverOps records variable values 5 levels into the heap. The recording mechanism is based on a knapsack algorithm that balances the number of values recorded with minimizing the effect the snapshot has on the application performance. That mechanism is called “The Cart”, since it operates like a supermarket cart - it collect data until it’s full.
The out of the box cart size was designed to fit the needs of most companies, adding rich information on any error and exception, while minimizing the effect on application performance, and most OverOps customers use it as is.
However, some advanced users might want to customize the wealth of information that the micro-agent collects by increasing the cart size. To do so, you can use the following JVM argument when starting the application:
<recording size> represents the amount of data collected and can accept values from 0.1 - 4, where “1” represents the default algorithm set by OverOps.
Adding lower values causes the micro-agent to collect less data and can improve the application’s performance, while entering values higher than 1 tells the micro-agent to collect more data, while impacting application performance.
For example, using -Dtakipi.cart.factor=2 will increase cart size by 2x. That will allow the micro-agent to collect 2x data, but can affect application performance.
NOTE: Manually setting the cart size is an advanced feature that will impact application performance, potentially causing application slowdowns.