OverOps provides you deep insight into your errors. One part of that is by showing you the code and variable state right at the time of the error you're analyzing. In the error analysis screen, you can see recorded variables throughout your call stack.
OverOps records the variables in the code when your error occurred. There are two ways to see a variable value in the analysis screen. The first is to hover over the variable.
Value shown when hovering over the variable “input”
The second is to look at the Recorded variables table on the right hand side of the method in question. Here you can see every variable recorded in the method. By clicking on the little arrow next to a variable, you can expand the table and see further object values, up to 5 levels deep into the heap.
The Recorded Variables table, with expanded object values
OverOps does not record 100% of variable values by default. There are certain types of personally identifiable variables that OverOps redacts automatically. In the error analysis screen, these errors will be depicted as asterisks. To read more about personally identifiable information filtering in OverOps, go here.
A redacted variable
Recorded Variable Limits
For performance reasons, variables of certain datatypes have limits by default:
- Strings have a max length of 300 characters.
- Arrays have a max length of 25 elements.*
*Note: Some data structures are backed by arrays(like ArrayList and HashMap), the 25 element limit also applies to these data structures.