---
title: "Signals and errors"
subtitle: "Spot error spikes above your logs and drill into the spans behind them."
---
The signals panel sits above the table in [Logs](/docs/documentation/features/observe/explore-spans). It charts your spans, errors, and [behaviors](/docs/documentation/features/pulse/behaviors) over the time range you pick. Click a card, row, or cell, and the table filters to the spans behind it.
![The signals panel: Spans, Errors, Issues, Wins, and Info cards over a day of spans, with an error spike and outlined cells in the Errors row]({"/docs/images/signals-behaviors/signals-panel-light.png"})
![The signals panel: Spans, Errors, Issues, Wins, and Info cards over a day of spans, with an error spike and outlined cells in the Errors row]({"/docs/images/signals-behaviors/signals-panel-dark.png"})
| Part | What it shows |
| --- | --- |
| **Spans** | Every span that matches your filters. Errors fill the base of each bar in red, and incident windows are shaded. |
| **Errors** | Failed spans and the error rate. A red "1 ongoing" means an incident is live. |
| **Issues**, **Wins**, **Info** | The share of spans with at least one behavior of that type. These show when behaviors are on. |
Each card compares the range with the period before it. A cell's shade is its share of the spans in that column, and an outlined cell stands out from the rest of its row. The panel shows while Logs is grouped by **Spans**.
## Drill into an error spike
Go to **Observability** › **Logs** and pick **5m**, **1h**, **1d**, **7d**, or **Custom** in the panel. A spike shows as red in the **Spans** bars and a darker cell in the **Errors** row.
Click the **Errors** card. The table filters to failed spans, and the panel lists "Incidents" first, then "Other error groups". An error group collects failures with the same error type, provider, endpoint, and status code. Click the card again to go back to every span.
Drag across the columns and release, or double-click a column. Press Escape to step back, or click **Reset zoom** to see the whole range again.
Click a cell. The table lists that row's spans from that window. Click the same cell again to zoom into it.
Click the group's name. The table filters to the group, and the row opens with its status code, fault, provider, and endpoint, then the sample span's **Error**, **Warning**, and **Recommendation**. **Errors by model** splits the errors by model; switch it to **Errors by customer** to see who's affected.
![The errors view with two incidents, and the Context window group open: a 400 from OpenAI chat/completions with its Error, Warning, Recommendation, and errors by model]({"/docs/images/signals-behaviors/errors-view-light.png"})
![The errors view with two incidents, and the Context window group open: a 400 from OpenAI chat/completions with its Error, Warning, Recommendation, and errors by model]({"/docs/images/signals-behaviors/errors-view-dark.png"})
Click a span in the table to see its full request and response. See [Inspect spans and traces](/docs/documentation/features/observe/view-debug-traces).
## Triage an error group
An open error group has these actions:
- The resolution menu, which reads **Unresolved** until you triage the group: **Resolve**, **Ignore**, or **Reopen**. Resolved and ignored groups are dimmed.
- **Copy fix prompt**: copies a prompt for your coding agent. It asks the agent to inspect the failing spans through the [Respan MCP server](/docs/documentation/mcp) and propose the smallest safe fix, and it carries the fingerprint, status code, fault, time range, filters, counts, sample span ID, and error message.
- **⋯** menu: **Create monitor**, **Copy fingerprint**, **Copy sample span ID**, and **Copy link**. **Create monitor** makes a monitor for this group with your current filters, turned off, and opens it so you can finish it. See [Monitors](/docs/documentation/features/monitoring/monitors).
Under the details, **Reach** counts the customers and models affected. It's hidden when you filter by anything other than environment.
| Field | Values |
| --- | --- |
| Error type | Provider rate limit, Provider down, Network transient, Context window, Content policy, BYOK auth, Managed auth |
| Fault | Provider, Your requests, Respan |
## Work an incident
An incident is a window where errors spike or drift above their usual rate. Incidents count every request in the environment, not only the spans that match your filters. An ongoing incident refreshes every minute.
Click an incident under "Incidents" to open it. It shows **Status**, **When**, **Error rate**, **Peak**, **Failed**, and the customers, providers, models, and endpoints it hit, followed by its error groups.
- **Acknowledge** tells your team someone owns it. Click **Acknowledged** to undo.
- **Zoom to incident** zooms the chart to the incident, with a little time on either side, and filters the table to its error groups. **Zoom out** goes back.
- The **⋯** menu has **Add note**, **Copy incident ID**, **Copy link**, and **Copy summary**. Everyone who can see the incident can read its notes, so keep secrets and customer content out of them.
## Share a link
**Copy link** gives you a Logs URL that opens the error group or incident directly. You can also add these parameters to a Logs URL yourself:
| Parameter | Opens |
| --- | --- |
| `?error_detail=` | The error group, with the table filtered to it. |
| `?incident_detail=` | The incident. |
| `?behavior_detail=` | The behavior, with the table filtered to it. |