Opening the ARC Analysis Screen

The Automated Root Cause (ARC) screen displays the source code, stack, variable state and log statements leading to an error or exception in staging or production.

The ARC screen can be opened from the following tools:

 

Logs Files

The OverOps JVM Agent captures the source code and variable state at the instant an event is logged. The snapshot capturing the event is assigned a unique log link. An example of an event log with the embedded log link is displayed below:

[20-07 07:32:51][BRT-1473 -S4247] ERROR - NullPointerException: Uu7XoelHfCTU/Ulvol6d2a9pU, in jar builder proto: J141531 [http://tkp.to/g1Tbkt-L] {StreamsCodeAnalysis} [SQS-prod_taskforce1_BRT-Executor-1-thread-2]

Log links connecting events in your logs directly to their root cause

 

Event List

The Event List displays all events in the current View and timeframe. Columns in the list - Location, Type, First seen, Last Seen - provide analytics that can be used to prioritize errors. Click an event in the list to open its Automated Root Cause. 

Event List

 

Event Chart

Click any point in the Event chart, or in an Automated Root Cause currently open to jump directly to the closest snapshot. Combined with Application/Server filtering, this provides an efficient tool to determine the cause behind and surge or spike of errors within the environment.

Click any point in the chart to jump to the closest snapshot

 

Splunk, ELK, Sumo Logic

Since log links are injected at the JVM level, they become an integral fabric of the log structure. This means that you can jump directly to the root cause of any error, from user interfaces such as Splunk, Sumo Logic, ELK, Loggly and more, regardless of the Log analytics solution you are using.

Log link in the event in Splunk leading to its root cause

 

Slack, HipChat, PagerDuty

The OverOps alerting mechanism notifies you of new events introduced to your application in real-time, through Slack, HipChat or PagerDuty. The alert contains information such as the application name, server, stack trace and more. Click the alert to open the event Automated Root Cause.

Alerts in Slack, HipChat and PagerDuty take you directly to the event root cause.

 

Email

The Alerts dialog box also enables setting up email alerts to be sent when new errors are introduced, and as a digest of events to prevent overload.

Email Digest

 

Jira

OverOps enables you to open a Jira ticket for any event directly from the Dashboard or the Automated Root Cause. This provides a way for teams to collaborate around errors and and issues in your environment and share critical information between developers, operations and QA.

Jira issue linking to the event

 

Sharing events with Team Members

Any root cause can be easily shared with team members by adding a note to it and tagging the team member to be notified.

To add a note:

  1. Click Edit Note in the Automated Root Cause toolbar,
    or
    right-click the event Dashboard Event list and then click Edit Note
  2. Write a note and, in Tag People, insert the relevant email addresses to invite to read the note.

    An email is sent to the added emails with the note linking to the event.
Have more questions? Submit a request