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

# Logs

Deep dive into Pharos log records—the foundation of observability. Learn about automated error collection, log types, enrichment processes, and storage.

Logs are the foundation of Pharos observability. They serve as the permanent system of record for all diagnostic events in your Salesforce environment. Unlike transient debug logs or email notifications, Pharos logs are persistent, enriched, actionable, and tamper-proof.

## Why Log Records Matter

In traditional observability systems, logs answer "what happened?" in your application. However, Salesforce's native logging capabilities are fragmented and ephemeral—exception emails get deleted, debug logs expire after hours, and bulk API failures hide in queues no one monitors.

**The Business Impact:**

* **Without logs:** Teams work blind, spending days reproducing issues from vague user reports
* **With fragmented logs:** Developers hunt across multiple systems to piece together what happened
* **With unified logs:** Issues detected immediately with full context, reducing MTTR from days to minutes

## Pharos Log Characteristics

✅ **Persistent:** Stored as Salesforce objects with configurable retention\
✅ **Enriched:** Automatically enhanced with contextual metadata\
✅ **Actionable:** Structured for querying, reporting, and analysis\
✅ **Tamper-proof:** Immutable snapshots of the moment of failure\
✅ **Secure:** Inherits all Salesforce security (profiles, permission sets, sharing)

## 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>📡 Log Ingestion Methods</strong></td><td>The three different means to intake logs in Pharos, and the use cases for each.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods.md">Log Ingestion Methods</a></td></tr><tr><td><strong>💾 Log Storage</strong></td><td>How logs are stored in Salesforce orgs using native custom objects.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-storage.md">Log Storage</a></td></tr><tr><td><strong>⚙️ Log Processing</strong></td><td>How Pharos processes logs and what data is added to log records.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-processing.md">Log Processing</a></td></tr><tr><td><strong>📊 Log Presentations</strong></td><td>How Pharos presents log data for specific Salesforce technologies, and why it matters.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-presentations.md">Log Presentations</a></td></tr><tr><td><strong>🔎 Accessing Logs</strong></td><td>How to find and access logs in Salesforce using standard Salesforce tools.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/accessing-logs.md">Accessing Logs</a></td></tr><tr><td><strong>🔐 Access Controls</strong></td><td>Safeguard log data that may contain sensitive information through permission sets and data masking.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/access-controls.md">Access Controls</a></td></tr></tbody></table>

{% hint style="info" %}
**Zero-Config Start:** Pharos begins capturing logs automatically once the managed package is installed and configured. No custom code or manual instrumentation required — errors are tracked from the moment the platform is live.
{% endhint %}

{% hint style="success" %}
**Next Steps:** Start with [Log Ingestion Methods](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods.md) to understand how errors enter the system.
{% endhint %}
