Troubleshooting with Sumo Logic Observability

Now that you have identified the issue and isolated the cause to a specific service or area, the next step is to get to the root cause and fix it so that the system could be restored to a healthy state.

Find Anomalous behavior in Metrics

Having trouble isolating the real issues when there’s an incident? You can use the Root Cause Explorer to quickly isolate issues by identifying services and metrics that have been behaving abnormally over the incident timespan. This will help you pinpoint the root cause of the issue.

Find Interesting Patterns in your Log Data 

You can also leverage Behavior Insights to understand interesting log signature patterns in your data, like connection timeouts, errors, or exceptions. This will help you uncover the needle in a haystack, so you can get to the root cause quickly, without having to go through tons of data manually.  

Ad Hoc Searching to get to the root cause

You can use Log Search to do ad hoc searches on your data to quickly validate or debunk hypotheses and narrow down your investigation scope. You can also do rich analytics on unstructured data to uncover patterns that will help you find interesting insights that help you find the root cause.