After setting up OverOps for the first time and connecting it to the JVMs you’d like to monitor, OverOps will begin analyzing your code. This is a one-time process that only happens during the first setup.
During the analysis, OverOps will display this message:
Analyzing your code is a complex process involving the OverOps agent on your server and OverOps' cloud. During this initial analysis, the OVerOps service may consume more CPU than usual, but it’s designed to have minimal effect on your application’s performance. Once this process is done, service will go back to normal, and OverOps will consume no more than 3% of the server’s CPU.
The duration of the analysis process varies, depending on the size of your bytecode, quality of your internet connection, and complexity of your setup, but should take no more than 30 minutes.
During the analysis, any exception thrown in your app will be displayed in the OverOps dashboard, but will have a “processing” message next to it:
Note: Please do not stop OverOps' service or restart your server during the analysis. This might cause some of the exception data to be lost.
Once the analysis is completed, the errors thrown within your application during this period will be fully processed, and you can click on them to open the exception analysis:
From that point on new exceptions will be fully processed within 30 seconds or less. Moving forward, when you deploy new code, OverOps won’t analyze the entire codebase again, only the parts that were changed.