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

# How Interfere works

> Understand what a problem contains and how your team investigates it.

Interfere collects errors, traces, logs, and session replays from your apps and uses them to investigate problems. A problem brings the investigation and its supporting evidence into one place, alongside the users, companies, and releases involved.

```mermaid actions={true} theme={null}
---
config:
  fontFamily: BerkeleyMono, monospace
  themeVariables:
    fontSize: 12px
  themeCSS: |
    .label { font-family: BerkeleyMono, monospace; font-size: 12px; font-weight: 500; }
    .diagram-node { display: inline-flex; align-items: center; gap: 12px; box-sizing: border-box; width: 240px; min-height: 40px; padding-inline-end: 8px; }
    .diagram-icon { display: inline-flex; align-items: center; justify-content: center; box-sizing: border-box; width: 40px; height: 40px; flex: 0 0 40px; }
    .diagram-icon img { display: block; width: 20px !important; height: 20px !important; margin: 0; }
    .diagram-name { max-width: 160px; white-space: normal; text-align: start; line-height: 18px; }
    .edgeLabel p { padding: 3px 7px; border: 1px solid transparent; }
  flowchart:
    curve: linear
    wrappingWidth: 240
    useMaxWidth: false
    padding: 5
    nodeSpacing: 48
    rankSpacing: 72
    diagramPadding: 24
---
flowchart TB
  accTitle: From application evidence to a problem
  accDescr: Application errors, traces, logs, and sessions provide evidence for findings and investigations. Your team reviews the problem and follows recovery.
  App["<span class='diagram-node'><span class='diagram-icon'><img src='/icons/ui/layers.svg' width='20' height='20' alt='' /></span><span class='diagram-name'>Your app</span></span>"] --> Evidence["<span class='diagram-node'><span class='diagram-icon'><img src='/icons/ui/observability.svg' width='20' height='20' alt='' /></span><span class='diagram-name'>Errors, traces, logs and sessions</span></span>"]
  Evidence --> Investigation["<span class='diagram-node'><span class='diagram-icon'><img src='/icons/ui/agents.svg' width='20' height='20' alt='' /></span><span class='diagram-name'>Findings and investigation</span></span>"]
  Investigation --> Problem["<span class='diagram-node'><span class='diagram-icon'><img src='/icons/ui/inbox.svg' width='20' height='20' alt='' /></span><span class='diagram-name'>Problem in Inbox</span></span>"]
  Problem --> Team["<span class='diagram-node'><span class='diagram-icon'><img src='/icons/ui/shield-check.svg' width='20' height='20' alt='' /></span><span class='diagram-name'>Review, fix and follow recovery</span></span>"]
```

## From events to a problem

An error describes one failure. A trace shows the work around it, and a session replay can show what someone did before the failure. Interfere groups related occurrences into findings and uses that evidence to investigate the underlying problem.

For example, several customers might hit the same exception while choosing store pickup at checkout. Those occurrences can belong to one problem. The investigation can connect the exception to a release, inspect the affected code through your GitHub integration, and explain why that checkout path fails.

The available evidence determines how much the investigation can establish. Read the explanation alongside its linked traces and code before deciding on a fix.

## What you see in a problem

* **Timeline** contains the investigation, updates, and your team's discussion.
* **Findings** contains the recorded evidence. Open an occurrence to inspect its trace and stack frames.
* **Sessions** connects the problem to affected sessions and their replays.

Start with the [Inbox](/docs/product/inbox) to find problems that need attention. The [investigation walkthrough](/docs/product/problems.md) follows a checkout failure through its evidence and recovery.

## Understand the impact

[Users](/docs/product/users.md) are the people using your monitored app. [Companies](/docs/product/companies.md) represent customer accounts and group their users. Identifying users in your app gives your team a way to connect a reported failure to the customer's sessions and problems.

A **surface** is an app you monitor, such as a storefront or its backend API. Each surface has its own keys and releases. Your **workspace** holds your team's surfaces, integrations, members, and settings. Use environments to distinguish staging from production within a surface.

## Follow the fix

Assign a problem to a teammate, set its priority, and add context in the timeline. After deploying a fix, inspect new occurrences and the releases they came from. Interfere follows recovery and resolution as it observes events; a resolved problem can reopen as a regression.

> **[Connect your first app](/docs/quickstart.md)**
>
> Set up a surface, install its SDK, and verify incoming events.

> **[Investigate a problem](/docs/product/problems.md)**
>
> Read the investigation and check the evidence behind it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.