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

# Surface Issues with Signal

> Enable Signal on a tracing project to surface ranked issues from production traces with investigation detail and trace links.

<Info>
  Signal is available in closed Enterprise beta. Contact your Arize account team for access.
</Info>

**Signal** is a built-in worker that scans a tracing project's traces on a schedule, groups recurring failure patterns into **issues**, and writes an investigation for each one (overview, trace evidence, suggested fix).

<Frame caption="The Signal tab in an Arize AX project with the option to enable Signal">
  <img src="https://storage.googleapis.com/arize-assets/doc-images/signal/signal-tab.png" alt="The Signal tab in an Arize AX project with the option to enable Signal" />
</Frame>

<Info>
  Requires a tracing project with traces in Arize. See [Set up tracing](/ax/instrument/set-up-tracing) if needed.
</Info>

No repo or extra skills are required to detect issues. To let Signal open fix PRs, use **Attach Repo** from the **Signal** tab menu (⋯ on the tab header). **Unattach Repo** in the same menu to revert to trace-only investigations.

## Enable Signal

<Frame>
  <video
    src="https://storage.googleapis.com/arize-assets/doc-images/signal/enable-signal.mp4"
    alt="Enabling Signal on a tracing project from the Signal tab"
    width="100%"
    height="100%"
    style={{
  display: 'block',
  objectFit: 'fill',
  backgroundColor: 'transparent',
}}
    controls
    autoPlay
    muted
    loop
  />
</Frame>

<Steps>
  <Step title="Open the tracing project">
    Signal only reads traces from the selected project.
  </Step>

  <Step title="Open the Signal tab">
    Select **Signal** in the project navigation.
  </Step>

  <Step title="Click Enable Signal">
    Arize creates a default automation using the Signal preset (recurring schedule, for example every 10 minutes). The tab stays linked to this automation until you disable Signal or delete it.
  </Step>
</Steps>

## Read issues

The **Signal** tab shows issue volume over time, a breakdown by entity when tagged, and a ranked issue list. Select an issue to read its investigation:

<Frame>
  <video
    src="https://storage.googleapis.com/arize-assets/doc-images/signal/signal-surfaced-errors.mp4"
    alt="Signal surfacing ranked errors from a tracing project's traces, each with its investigation and trace links"
    width="100%"
    height="100%"
    style={{
  display: 'block',
  objectFit: 'fill',
  backgroundColor: 'transparent',
}}
    controls
    autoPlay
    muted
    loop
  />
</Frame>

* **Overview**: summary of the failure pattern
* **Evidence**: trace IDs and filters
* **Proposed fix**: suggested prompt, code, config, or eval change

Click the **example traces** to open evidence in [Explore your traces](/ax/observe/tracing/view-and-manage-traces).

<Frame>
  <video
    src="https://storage.googleapis.com/arize-assets/doc-images/signal/signal-traces.mp4"
    alt="Signal tab for a tracing project showing issue volume over time and a ranked list of recurring failure issues surfaced from production traces"
    width="100%"
    height="100%"
    style={{
  display: 'block',
  objectFit: 'fill',
  backgroundColor: 'transparent',
}}
    controls
    autoPlay
    muted
    loop
  />
</Frame>

## Attach a repo for fix PRs

When Signal has a repo attached, it can clone the repository and open pull requests for proposed fixes, not just write investigations.

<Frame>
  <video
    src="https://storage.googleapis.com/arize-assets/doc-images/signal/signal-attach-repo.mp4"
    alt="Attaching a GitHub repo to Signal so it can open pull requests for proposed fixes"
    width="100%"
    height="100%"
    style={{
  display: 'block',
  objectFit: 'fill',
  backgroundColor: 'transparent',
}}
    controls
    autoPlay
    muted
    loop
  />
</Frame>

<Steps>
  <Step title="Open the Signal tab menu">
    On the **Signal** tab, open the **⋯** menu in the tab header.
  </Step>

  <Step title="Click Attach Repo">
    Choose an existing **GitHub skill** or **Create new GitHub skill** (name + personal access token). See [Skills and permissions](/ax/agents/skills-and-permissions) for token scopes.
  </Step>

  <Step title="Enter the repository">
    Provide the repo in `owner/repo` form. Click **Attach Repo**.
  </Step>
</Steps>

Arize creates or updates the Signal agent preset for this project automatically; you do not need to visit [Agent Presets](/ax/agents/agent-presets) first. To go back to trace-only mode, choose **Unattach Repo** from the same menu.