---
id: troubleshoot
title: Troubleshooting with Sumo Logic Observability
sidebar_label: Troubleshooting with Observability
description: Use Observability to troubleshoot and diagnose issues across a variety of environments.
slug: /help/docs/observability/troubleshoot/
canonical: https://www.sumologic.com/help/docs/observability/troubleshoot/
---

import useBaseUrl from '@docusaurus/useBaseUrl';

<img src={useBaseUrl('img/icons/operations/troubleshoot.png')} alt="Troubleshoot icon" width="70"/>

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.

<img src={useBaseUrl('img/observability/root-cause-wheel.png')} alt="Root cause wheel" style={{border: '1px solid gray'}} width="600" />

## Find interesting patterns in your log data 

You can also leverage [Behavior Insights](/docs/search/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.  

<img src={useBaseUrl('img/observability/behavior-insights-example.png')} alt="Behavior insights example" style={{border: '1px solid gray'}} width="800" />

## Ad hoc searching to get to the root cause

You can use [Log Search](/docs/search/get-started-with-search/search-page) 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. 

<img src={useBaseUrl('img/observability/log-search-example.png')} alt="Log search example" style={{border: '1px solid gray'}} width="800" />