Quick Intro to Automated Root Cause

Contents

Analytics Pane

Error Graph

Call Stack

Source Code View

Variable and Object State

Log View

JVM View

Actions Toolbar

Related Articles

 

The Automated Root Cause page provides a powerful mechanism to get to the root of errors and exceptions in production and staging environments. The page is divided into three panes, that provide information about the event to create a complete picture.

Automated Root Cause 

 

Analytics Pane

The Analytics pane is located at the top left of the page, and displays important details relating to the impact of the error in the application: the type of the error, when it was first seen, the server/application it occurred in, and how many times it has been detected.

 

Error Graph

The Error Graph is located at the top of the page and it provides the context for the event by displaying its tendencies across servers/applications in a specific timeframe. Learn more about the Error Analysis Graph.

Click the JVM or Server labels to view the error volume on a specific machine or application directly. Hover over the occurrences label to display the error rate (the number of times this error has occurred and out of how many times the method containing it was called).

Click Open in Dashboard at the top right corner to open and select this event in the OverOps Dashboard. Click Go to snapshot on any point in the graph to jump to the code and view the current variable state.

Error Graph

 

Call Stack

The Call Stack pane displays the chain of methods within the JVM leading up to the event. The first method in line is the last method on a non 3rd party code within your application. The Screen_Shot_2016-08-18_at_7.58.51_PM.png icon in the method indicates that the variable state has been detected by the JVM micro-agent.

When an exception is caught and re-thrown once or more within the thread, Related Errors drop-down displays the error analysis (available only when such exceptions exist).

At the bottom of the stack the machine name and the JVM thread name in which this error occurred appear. 3rd party code is hidden by default and shown by switching on Show 3rd party methods at the bottom of the stack. To copy the full stack to the clipboard, click COPY STACK.

callstack2.png

Call Stack pane

 

Source Code View

By default, the Source Code View shows a decompiled Java version of the bytecode executing within the JVM at the moment of error. Hover over any highlighted variable to display its value and jump to see its full contents within the variable grid. The row in which the error occurred is highlighted, as depicted below.

Screen_Shot_2016-08-18_at_12.42.03_PM.png

The Source Code and Recorded Variables pane

 

The full error message appears in the title of the code pane. 

When configured, OverOps uses the original source code instead of decompiling it from the JVM.

Search the source code or the variable grid for any variable name or value using Search Variables. Click here to learn more about variable search.

 

Recorded Variable and Object State

Recorded Variables displays the variable values and objects accessible from the method. Objects can be explored up to five levels deep into the code. Click the button that appears when hovering over the object, to view its contents as a JSOB. The content can be copied to the clipboard.

The Recorded Variables pane contains all local variables and parameters (including "this" in non-static methods). The first method also contains thread-local variables defined for this thread as well as SLF4J and Log4J Mapped Diagnostics Context (MDC) values.

The choice of the collected variables most relevant within an allocated timeframe is determined by the micro-agent using an adaptive machine learning algorithm. The selection process involves which and how many variable to collect, the number of items to collect, the length of string to capture, etc.

Click here to learn more about object and variable state.

Recorded Variables displaying the variables state within the current method as well as thread local variables

 

The JSON representation of the object

 

Log View

The Log View displays the last 250 log statements leading up to the event. Since the log statements are collected directly from JVM memory, any DEBUG, TRACE or INFO statements are visible regardless of whether or not they were logged to file.

Click the Screen_Shot_2016-08-18_at_8.55.24_PM.png button to switch between code and log view.

Click here to learn more about the Log View.

Screen_Shot_2016-08-18_at_8.26.58_PM.png

Log View pane

 

JVM View

For each error and exception detected, OverOps displays a JVM view that displays the internal JVM state at the moment of the error, including memory usage (heap and non-heap), basic system information, CPU usage and more. This enables working with the OverOps code (“classic”), log and JVM data without leaving the application. Click here to learn more about the JVM View.

pasted_image_0__1_.png

 

Actions Toolbar

The Actions toolbar provides a set of capabilities to share, mark and search through the error analysis contents:

Actions include:

  • Send to Jira - Create a new Jira issue for an event linking it directly to the source, stack, state and statistics. Click here to learn more about Jira integration.
  • Hide - Hide the event from the Dashboard Events List and Chart. Furthermore, the micro-agents will no longer capture snapshots for this event. The event will appear under the "Archive" label in the Dashboard from which it can be unhidden. Click here to learn more about hiding errors.
  • Resolve - Mark an error as fixed and remove it from the Dashboard Events List and Chart. Should this error occur after a new code deploymentit will return to the Event List and Chart marked 'Resurfaced', and OverOps will notify you by email. Click here to learn more about resolving errors.
  • Label - Label events to classify them according to priority ('Critical' or 'Low'), responsibility ('John' or 'QA') and version ('V1 RC2'). Click here to learn more about creating and assigning labels.
  • Add/Edit Note - Attach a note to an event and share it with your teammates about which they are notified by email. Click here to learn more about sharing with teammates.
  • Add Timer - Track predefined methods for latency. OverOps sends an alert when the code runs longer than expected. Click here to learn more about Timers.

 

Related Articles

What is OverOps?

Automated Root Cause

Creating Custom Views

Have more questions? Submit a request