> 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/issue-tracker.md).

# Issue Tracker

How Pharos Issue Tracker turns thousands of individual log records into manageable, prioritized Issues through fingerprinting and de-duplication.

The Issue Tracker transforms thousands of individual log records into manageable, prioritized issues through intelligent fingerprinting and de-duplication—enabling teams to systematically address root causes rather than chasing individual error instances.

## Why Issue Tracking Matters

In observability systems, raw logs answer "what happened?" but they quickly become overwhelming. When the same error occurs 2,000 times across 50 users, you don't need 2,000 alerts—you need **one clear problem statement** with aggregate impact data.

**The Business Problem:**

* **Without aggregation:** Alert fatigue causes teams to ignore notifications
* **With poor grouping:** False positives waste time investigating "different" errors that are actually the same
* **With intelligent grouping:** Teams can systematically prioritize and resolve root causes

Traditional observability tools use keyword-based grouping which creates both false positives (grouping unrelated errors) and false negatives (splitting instances of the same error). Pharos uses **fingerprinting**—a deterministic algorithm that accounts for Salesforce-specific patterns—to achieve accurate de-duplication.

**The Outcome:**

* Reduce noise from thousands of logs to dozens of actionable issues
* Prioritize based on user impact, not chronological order
* Track resolution progress and measure system health trends

## What is an Issue?

An **Issue** in Pharos represents a **cluster of identical failures**, de-duplicated by fingerprint. Think of it as an automatically-generated bug tracker entry that evolves as more instances of the same error occur.

### Anatomy of an Issue Record

```mermaid
graph TD
    A[Issue Record: DML Exception on Opportunity Insert]
    A --> B[Fingerprint: abc123def456...]
    A --> C[Category: Apex - Type: DML Exception]
    A --> D[Functional Area: Apex]
    A --> E[Status: New - Priority: High]
    A --> F[First/Last Occurrence: May 15 - Oct 18, 2024]
    A --> G[Total: 3,247 occurrences - 47 users - 12,391 records]
    A --> H[Related Logs - Related Jira Ticket: PROJ-1234]
```

### Issue vs. Log: Key Differences

| Aspect         | Log Record                      | Issue Record                           |
| -------------- | ------------------------------- | -------------------------------------- |
| **Represents** | Single event occurrence         | Cluster of identical events            |
| **Creation**   | One per failure                 | One per unique error pattern           |
| **Lifecycle**  | Static (never changes)          | Dynamic (evolves with new occurrences) |
| **Purpose**    | Detailed debugging              | Triage and prioritization              |
| **Count**      | Thousands per day (high volume) | Dozens per month (manageable)          |

**Example:**\
A validation rule fails 500 times today across 20 users → 500 log records, 1 Issue record.

## Explore Issue Tracking

<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>💡 Why Issues?</strong></td><td>Why aggregating issues vs. logs makes issue management easier and more streamlined.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/why-issues.md">Why Issues?</a></td></tr><tr><td><strong>📋 Issue Details</strong></td><td>The comprehensive groups of data presented on the issue details page.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details.md">Issue Details</a></td></tr><tr><td><strong>♻️ Issue Lifecycle</strong></td><td>The Issue journey from creation to completion, with status transitions.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-lifecycle.md">Issue Lifecycle</a></td></tr><tr><td><strong>🔍 Accessing Issues</strong></td><td>How to find and access issues in Salesforce using standard tools.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/accessing-issues.md">Accessing Issues</a></td></tr><tr><td><strong>🔐 Access Controls</strong></td><td>Control issue access and understand permission requirements.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/access-controls.md">Access Controls</a></td></tr></tbody></table>

## Key Benefits

| Role           | Benefits                                                                                                                                            |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Admins**     | <p>• Triage without deep technical knowledge<br>• Use impact metrics to make informed decisions<br>• Track resolution progress</p>                  |
| **Developers** | <p>• Reduce time spent on duplicate investigations<br>• Access full context for faster debugging<br>• Verify fixes by monitoring for recurrence</p> |
| **Leadership** | <p>• Measure system health trends<br>• Track team velocity (issues resolved per sprint)<br>• Data-driven resource allocation</p>                    |

{% hint style="success" %}
**Next Steps:** Start with [Why Issues?](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/why-issues.md) to understand the core value proposition, then explore [Issue Details](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/issue-tracker/issue-details.md) to see what information is available.
{% endhint %}
