> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/tracing/issue-tracing.md).

# Issue Tracing

Learn about the entry point of tracing and how it relates to an issue.

Tracing in Pharos is **Issue-based**—you create trace schedules from an Issue, not from a user or component. This keeps debugging context tied to the problem you're solving and lets Pharos automatically manage trace flags across affected users.

***

## Entry Point: The Issue

Tracing starts from an Issue:

1. Open the **Issue** you need to debug
2. Navigate to the **Tracing** tab
3. Click **New Trace Schedule**
4. Configure users, error pattern, and duration
5. Save—Pharos handles the rest

The Issue provides the context: which users are affected, what error message to look for, and when the problem started.

***

## Trace Schedules

A **trace schedule** defines when and how to capture debug logs:

| Component          | Purpose                                                          |
| ------------------ | ---------------------------------------------------------------- |
| **Trace schedule** | Parent config; one active schedule per Issue                     |
| **Trace windows**  | Time periods when tracing is active (like calendar appointments) |
| **Error pattern**  | What to look for in the debug log (message, stack trace)         |
| **Target users**   | All affected users, or specific users                            |

Pharos creates trace flags during the windows, monitors for matching logs, and fetches them when found.

***

## Trace Results

When a matching debug log is captured:

* A **Trace Result** record is created and linked to the Issue
* You're notified (Slack, Teams, Email, PagerDuty)
* The log appears in the Tracing tab with full parsing and search
* You can add notification rules on trace results for additional alerts

***

## One Active Schedule Per Issue

You can have only **one active trace schedule per Issue** at a time. To change strategy (e.g., different users or duration), deactivate the current schedule and create a new one. After the last trace window passes, the schedule deactivates automatically—whether or not a log was captured.

***

## In This Section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>📅 Trace Schedules</strong></td><td>The data model behind trace schedules and trace request structure.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/tracing/issue-tracing/trace-schedules.md">Trace Schedules</a></td></tr><tr><td><strong>📊 Trace Results</strong></td><td>View trace results with visual presentations and debug log visualizers.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/tracing/issue-tracing/trace-results.md">Trace Results</a></td></tr></tbody></table>

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🔬 Tracing Overview</strong></td><td>Full tracing guide</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/tracing.md">Tracing</a></td></tr><tr><td><strong>🔱 Triton Tracing</strong></td><td>Combining Triton with trace schedules</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/tracing/triton-tracing.md">Triton Tracing</a></td></tr><tr><td><strong>🔬 Configuration Guide: Tracing</strong></td><td>Admin configuration steps</td><td><a href="https://docs.pharos.ai/configuration-guide/tracing.md">Tracing</a></td></tr></tbody></table>
