---
title: "Faults Tool"
slug: "faults-tool"
updated: 2026-02-20T14:42:10Z
published: 2026-02-20T14:42:10Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Faults Tool

Resolve's Faults Tool enables you to investigate faults and their scope. The tool identifies the application faults that impacted a system during the selected time window.

To get started with this tool, [select a focus system](/documentation/docs/change-focus-in-resolve), configure a [Time Window](/documentation/docs/adjust-the-time-window-and-focus-time) for the data that displays on this page, and then proceed with the following sections.

![The Faults page in Resolve](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/FaultsFull.png)

## System Faults Section

In the **System Faults** section, the graph uses the following icons to indicate the nature of the faults and the dates on which they occurred:

- **Isolated:** The fault has occurred on only the focus system.

![The Isolated Fault icon in Resolve](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/IsolatedIcon.png)
- **Systemic:** The fault has occurred on the focus system and at least one other system.

![The Systemic Fault icon in Resolve](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/SystemicIcon.png)
- **Unknown:** Resolve was not able to gather sufficient data about the fault.

![The Unknown Fault icon in Resolve](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/UnknownIcon.png)

You can hover over these icons to see a box with more detailed data about each fault.

![The Details hover box in Resolve](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/FaultHoverDetails.png)

## Fault Data Section

In the **Fault Data** section, you see statistics about each individual fault. This section gives you many columns of data to investigate for each fault, such as **Incident Count**, **Application Version**, and **Mean Time Between Failures**. Double-click in the **Application** column for a fault from the list to open the Application in Visualizer.

## Investigate with the Faults Tool

When more than one user reports application faults for the same application, it is a good practice to determine the scope of the issue. For example, how many users and which specific users are affected by the application fault? This section explains how to use the Faults tool to investigate.

To begin, use the Faults tool to identify software package faults that have impacted a system during a selected time period.

1. In the Resolve menu, select **Faults**.
2. If you haven't already selected a system, use [Change Focus](/documentation/docs/change-focus-in-resolve) to find and select the system that you want to investigate.

The Faults Tool populates with data about the system.
3. Configure a [Time Window](/documentation/docs/adjust-the-time-window-and-focus-time) for the data that displays on this page.
4. In the **System Faults** section, look at the Isolated and Systemic faults. It is a good practice to further investigate systemic faults. Review the data and note the date when the fault occurred.
5. Switch into **Visualizer**.

You can use [Visualizer](/documentation/docs/systrack-visualizer) to further investigate the fault. In the **Application Faults - Basic section**, you see a graph of the fault summary by number of faults and affected systems. In the bottom section, named **Application Faults**, find the fault that occurred on the date you noted. To quickly determine which systems have been affected by the fault, double-click on an **Affected Systems** value to see a **Drilldown Detail** box with more information.

![Visualizer fault summary by number of faults and affected systems section](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/FaultsByAppInVisualizer.png)