> 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/logs/log-presentations.md).

# Log Presentations

Understand how Pharos presents log data for specific Salesforce technologies and why specialized presentations enhance debugging and analysis.

Pharos transforms raw Salesforce debug logs into context-aware presentations tailored to each technology's unique characteristics. Rather than presenting a one-size-fits-all view, the platform understands the nuances of Apex, Flow, Bulk API, integrations, and other Salesforce execution contexts to surface the most relevant debugging information.

{% hint style="success" %}
**Smart Presentation:** Pharos automatically recognizes the log type and presents information in the format most useful for that specific technology—reducing debugging time from hours to minutes.
{% endhint %}

## Why Technology-Specific Presentations Matter

Salesforce executes code through diverse mechanisms—from declarative flows to custom Apex to batch data operations—each generating logs with distinct structures and debugging needs. A Flow developer troubleshooting decision logic requires different information than an Apex developer investigating a SOQL performance issue or a data admin analyzing bulk import failures.

Traditional approaches force developers to parse through raw debug logs manually, searching for relevant details buried in verbose output. Pharos eliminates this friction by automatically recognizing the log type and presenting information in the format most useful for that specific technology.

## How Pharos Addresses Log Presentation

When Pharos ingests a log, it performs several enrichment steps before presentation. This transformation makes debugging faster and more effective:

| Processing Step                  | What Happens                                                                   | Developer Benefit                                  |
| -------------------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------- |
| **Recognition & Categorization** | Identifies technology source (Apex, Flow, Bulk API, etc.)                      | Drives which specialized features become available |
| **Metadata Extraction**          | Pulls key identifiers: class names, flow elements, API operations              | Makes data searchable instead of buried in text    |
| **Structure Parsing**            | Reconstructs execution paths: method hierarchies, flow traversal, job linkages | Visual debugging of execution flow                 |
| **Performance Analysis**         | Extracts timing data, governor limits, callout durations                       | Powers performance visualizations and optimization |

**The Result:** Developers spend less time searching through logs and more time understanding what happened and why.

## Common Elements Across All Log Types

While each technology has specialized presentation features, certain information is universal across all logs in Pharos. This consistent foundation ensures developers always have the core context they need:

| Element Category      | What's Included                                                                           | Why It Matters                                         |
| --------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| **Core Fields**       | Timestamp (ms precision), severity level, category, functional area, summary, description | Foundational metadata for every log                    |
| **Execution Context** | User permissions, organization, entry point, transaction boundaries                       | Understand where and how code executed                 |
| **Related Data**      | Object types, record IDs, impact statistics                                               | Link logs to business records and measure impact       |
| **Fingerprinting**    | Error patterns, code location, failure type                                               | Automatic grouping into Issues for pattern recognition |

{% hint style="info" %}
**Universal Navigation:** When viewing any log, you can immediately see whether it's an isolated incident or part of a recurring issue affecting multiple users or records.
{% endhint %}

## Technology-Specific Presentations

Beyond these common elements, each log type receives specialized treatment tailored to its debugging needs:

<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>🌊 Flow and Process Builder Logs</strong></td><td>Flow and Process Builder log presentations, including the flow debugger and element-level execution tracking.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/flow-and-process-builder-logs.md">Flow and Process Builder Logs</a></td></tr><tr><td><strong>💻 Apex Logs</strong></td><td>Apex-specific log presentations, including the stack trace visualizer and supporting class information.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/apex-logs.md">Apex Logs</a></td></tr><tr><td><strong>📦 Bulk API Logs</strong></td><td>Bulk API log presentations, including error summaries, pattern analysis, and batch operation details.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/bulk-api-logs.md">Bulk API Logs</a></td></tr><tr><td><strong>🔗 Integration Payloads</strong></td><td>Payload-driven integration presentations, including request/response visualizers, HTTP details, and Apex callout context.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/integration-logs.md">Integration Payloads</a></td></tr><tr><td><strong>🔗 Transaction (Parent) Logs</strong></td><td>Parent (transaction) log presentations and Triton transaction logging.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations/transaction-parent-logs.md">Transaction (Parent) Logs</a></td></tr></tbody></table>

## Presentation Modes and Views

Most log types support multiple viewing modes depending on debugging needs. Users can switch between these modes fluidly as their investigation progresses:

| View Mode            | Purpose                                                            | Best For                                   |
| -------------------- | ------------------------------------------------------------------ | ------------------------------------------ |
| **Summary View**     | High-level overview: what failed and why                           | Triage and prioritization                  |
| **Detailed View**    | Complete log content with all metadata                             | Thorough investigation                     |
| **Debug View**       | Interactive interface with execution trees and variable inspection | Step-by-step debugging (Apex, Flow)        |
| **Performance View** | Timing charts and governor limit analysis                          | Bottleneck identification and optimization |

## Accessing Log Presentations

Log presentations are accessed through multiple entry points, creating an interconnected debugging experience:

* **Logs Tab:** Direct access to individual logs with filtering and search capabilities
* **Issues Tab:** Pattern-level insights for recurring problems before drilling into individual occurrences
* **Transactions:** End-to-end traces for instrumented multi-step processes

Navigation between logs, issues, and transactions ensures that context is always available as debugging needs evolve from "What happened?" to "Why did it happen?" to "How do I fix it?"

## Summary

Log presentations in Pharos transform raw debug output into actionable insights by recognizing the technology that generated each log and surfacing information in the most useful format.

**What Makes Presentations Powerful:**

* **Technology Recognition:** Automatic categorization drives specialized presentation features
* **Metadata Extraction:** Searchable attributes instead of text buried in logs
* **Visual Debugging:** Execution trees, flow diagrams, and performance charts
* **Multiple View Modes:** Switch between summary, detailed, debug, and performance views
* **Unified Navigation:** Seamless movement between logs, issues, and transactions

**The Result:** Developers spend less time searching through verbose output and more time understanding and resolving issues. Each technology—Apex, Flow, Bulk API, Integration, Transaction—gets presentation tailored to its specific debugging needs.
