Within the error analysis screen users can get all the information required in order to understand and fix an error - the state, stack, and source code that led to it. To complement this, OverOps also displays a log view for each error and exception, which shows the last 250 log statements leading up to the error, giving an easy way to work with OverOps' code (“classic”) and log data - without needing to leave the application.
This feature is available to OverOps users from version 3.22.0, and supports the following logging frameworks: logback and log4j.
The main way to reach the log view is by clicking on the tab, located in the error header. Clicking on this tab takes you from code view to log view, and back. You can also reach this view by creating a log view URL - just add “#log” at the end of your error’s URL.
The log view contains the 250 log lines by default that preceded the error.
The log view in the error analysis screen
In the log view you will be able to sift through your log entries (“info”), log warnings and error entries. Since OverOps create the log view directly from the JVM, you will get additional information not always available in the logs themselves, such as “DEBUG” and “TRACE” entries. Different log events are highlighted for your convenience, and you can use keyboard shortcuts to simply navigate between them (using the arrows keys and the page up/down/home/end).
Entering into the log view first takes you to the error or exception line, followed by the stack trace. OverOps will also display the context of the error, by highlighting the beginning of the relevant transaction in which the error happened.
Notice that all the advanced features and functionalities that are available in the error analysis screen are available in log view as well - handling the error (archiving, resolving, labeling), sharing it (via Jira or OverOps' notes) and searching within it.
In addition, just as we inject tiny URLs into your log files, you can see OverOps URLs within the log view, allowing you to open new errors and exceptions in a new tab directly from the log view, as you can do from the log file itself.
- Logback: TRACE level and up
- Log4j/Log4j2: According to the user's config
In order to change the number of characters recorded per log statement by adding the following argument to your JVM startup arguments (default 10K):