> 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-ingestion-methods.md).

# Log Ingestion Methods

Learn about the three different means to intake logs in Pharos and the use cases for each one.

The foundation of effective observability starts with comprehensive log collection. In traditional systems, logging is often an afterthought—requiring extensive code changes, manual configuration, and constant maintenance. Pharos takes a fundamentally different approach by providing multiple ingestion pathways that work together to capture the full spectrum of system behavior, from automatic error detection to deliberate instrumentation.

## Why Log Ingestion Matters

In Salesforce environments, failures occur across many surfaces: Apex triggers silently error out, Flow automations fail with cryptic messages, bulk API jobs hide failures in queues, and integration callouts timeout without trace. Each of these represents a potential blind spot where critical business processes can fail without anyone noticing until users complain or revenue is impacted.

| Failure Type             | Traditional Problem            | Business Impact                   |
| ------------------------ | ------------------------------ | --------------------------------- |
| **Apex Triggers**        | Silent errors, no notification | Data workflows break undetected   |
| **Flow Automations**     | Cryptic email messages         | Admins can't troubleshoot         |
| **Bulk API Jobs**        | Errors hidden in queues        | Integration failures go unnoticed |
| **Integration Callouts** | Timeout without trace          | Revenue loss from failed sync     |

{% hint style="danger" %}
**Common Pitfall:** Many teams attempt comprehensive observability through manual instrumentation alone—expensive, slow, and creates gaps. **Pharos inverts this:** start with automatic coverage, then selectively enhance.
{% endhint %}

## The Pharos Approach

Three methods, each serving a distinct purpose:

| Method                            | Effort   | What It Captures              | Best For                            |
| --------------------------------- | -------- | ----------------------------- | ----------------------------------- |
| 🔄 **Automated Error Collection** | **Zero** | Unhandled exceptions          | Instant baseline monitoring         |
| 🛠️ **Triton Instrumentation**    | Medium   | Custom events, handled errors | Deep visibility, performance        |
| 🔗 **Connected Orgs**             | Low      | Cross-environment logs        | Multi-org, archival, centralization |

{% hint style="success" %}
**Strategic Advantage:** Operate at multiple levels simultaneously—gain immediate value from automation while strategically investing in custom instrumentation where it matters most.
{% endhint %}

## Explore Each Method

<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>🔄 Automated Error Tracking</strong></td><td>How Pharos automatically tracks errors from Salesforce events and emails, with zero configuration.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/automated-error-tracking.md">Automated Error Tracking</a></td></tr><tr><td><strong>🔗 Connected Orgs</strong></td><td>Push logs between different Salesforce environments for centralized observability.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/connected-orgs.md">Connected Orgs</a></td></tr><tr><td><strong>🛠️ Pharos Triton Instrumentation</strong></td><td>The Pharos Triton logger, and how to add custom instrumentation to your Salesforce applications.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/pharos-triton-instrumentation.md">Pharos Triton Instrumentation</a></td></tr></tbody></table>

## Implementation Path

| Phase | Timeframe | Method            | What to Do                                                  |
| ----- | --------- | ----------------- | ----------------------------------------------------------- |
| **1** | Week 1    | 🔄 Automated      | Pharos activates automatically—gain immediate visibility    |
| **2** | Weeks 2-4 | 🛠️ Triton        | Instrument critical processes (integrations, key workflows) |
| **3** | Month 2+  | 🔗 Connected Orgs | Configure multi-environment strategy if needed              |

{% hint style="info" %}
**Flexibility by Design:** These aren't sequential gates. Many orgs run Automated Collection alone for years with great value. Others deploy all three from day one. Choose what matches your needs.
{% endhint %}
