When taking a snapshot of the variable values in a specific error or exception, OverOps records variable values 10 levels deep 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. This mechanism is called 'The Cart', since it operates like a supermarket cart - it collects data until it is full.
The out-of-the-box cart size is designed to fit the needs of our clients: adding rich information on any error and exception, while minimizing the effect on application performance.
The cart size can also be increased for advanced users that require expanding the information collected by the Micro-Agent.
//For JVM languages only, use the following JVM argument when starting the application -Dtakipi.cart.factor=<recording depth>
// For JVM and CLR languages, use the following property: takipi.cart.factor=<recording depth>
The refers to the amount of data collected and can accept values from 0.1 - 4, where “1” represents the default algorithm set by OverOps.
- Entering lower values causes the Micro-Agent to collect less data, which can improve the application’s performance.
- 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 the cart size by 2x. This allows the Micro-Agent to collect twice the amount of data, but can affect application performance.
Manually setting the cart size is an advanced feature that will impact application performance, potentially causing application slowdowns.
Updated about 2 years ago