How To Reach The Error Analysis Screen

The Root cause analysis screen shows the source code, stack, variable state and log statements leading to any error or exception in staging or production.

The Error analysis screen can be easily accessed through - 

Log files

The Event List

The Event Chart

Splunk, ELK, Sumo Logic

Slack, HipChat, PagerDuty

Email

JIRA

Sharing with teammates

 

Logs files

OverOps' JVM micro-agent captures the source code and variable state at the moment when the application decides to log an error. At that point the snapshot that's captured is assigned a unique tiny URL. Here's an example of a log error with the embedded link to take you to the cause behind the error. You can see an an example you can try 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 connect errors in your logs directly to their root cause.

 

The Event List

The dashboard's Event list enables you to see all errors in the current timeframe and view. Within the list columns such as Location, Type, First seen, Times, .. provide you with analytics that you can use to prioritize errors. Clicking any error in the list will tale you to its Error analysis. 

 

Click any error within the Event list to jump to its cause

 

The Event Chart

You can click any point within the dashboard's Event chart, or even within an Error analysis screen you're currently at to jump directly to nearest snapshot in that point in time. Combined with Application / Server filtering this provides a powerful way for you to see cause behind and surge or spike of errors within your environment.

 

Choose any point in the chart to jump to a snapshot from that point in time.

 

Splunk, ELK, Sumo Logic

Since log tiny links are injected at the JVM level, they become an integral fabric of the log structure itself. That means that no matter which Log analytics solution you use, you can always click on any error to jump directly to its root cause directly from Splunk, Sumo Logic, ELK, Loggly and more

 

 

Any error in Splunk will feature an embedded tiny link you can use to see the cause of the error.

 

Slack, HipChat, PagerDuty

OverOps' alerting capability enables you to be notified in real-time whenever new errors are introduced into your application(s) through Slack, HipChat or PagerDuty. The alert will contain information such as the application name, server, stack trace and more. Clicking the alert will take you directly to analysis screen for that error.

 

Alerts in Slack, HipChat and PagerDuty enable you to jump directly to the cause of new errors.

 

Email

The Alerts dialog also enables you to setup email alerts to be sent to you when new errors are introduced, but also in the form of grouped digests to prevent overload to your inbox.

 

The email digest shows you all the errors that were introduced in the last day

 

JIRA

OverOps enables you to open a JIRA ticket for any error you detect directly from the dashboard or the error analysis screen itself. This provides a streamlined way for teams to collaborate around errors and and issues in your environment and share critical information between developers, operations and QA. 

 

Opening a JIRA ticket linking to the error is a great way to collaborate between teams

 

Sharing with teammates

Any error analysis can be easily shared with teammates by adding a note to it and tagging the person whom you'd like to be notified of that error. You can add a note by clicking the "Edit note" button in the error analysis screen's toolbar, or by right clicking an error in the dashboard's Event list and clicking "Edit Note". An email with the note linking to that error will then be sent to that person.

 

Simply add a note and tag the person you want to let them know about it via email.

Have more questions? Submit a request