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

# Log Storage

Understand how logs are stored in Salesforce orgs using native custom objects.

Pharos stores all log and issue data natively within your Salesforce org as custom objects, providing seamless integration with Salesforce's security, compliance, and data management capabilities. This native storage approach means Pharos data lives alongside your other Salesforce data, accessible through familiar tools and protected by your existing security model.

## The Native Storage Advantage

As a fully native Salesforce application, Pharos doesn't ship your logs to external systems or require separate infrastructure. Everything persists within your org's storage allocation, which brings significant operational benefits. Your logs inherit Salesforce's enterprise-grade security model automatically, benefiting from field-level security, sharing rules, and encryption without additional configuration. Data never leaves your org, ensuring compliance with HIPAA, GDPR, SOC2, and other regulatory frameworks that require data residency controls.

The native approach also means you can leverage existing Salesforce capabilities without learning new tools. Standard Salesforce reports and dashboards work directly with Pharos data, SOQL queries provide flexible programmatic access, and familiar tools like Data Loader and Workbench handle bulk operations. Your Salesforce backup and disaster recovery processes automatically include Pharos data with no additional setup required.

{% hint style="success" %}
**Key Benefit:** Native storage means zero integration complexity. If you know how to work with Salesforce custom objects, you already know how to work with Pharos data.
{% endhint %}

## Storage Fundamentals

Pharos primarily consumes **Data Storage**—the same storage allocation used by your Accounts, Contacts, and other custom objects. As your org generates logs, they accumulate as custom object records, gradually consuming available capacity. For most organizations, log storage remains a small fraction of overall usage, but understanding consumption patterns helps you plan capacity and implement retention strategies when needed.

{% hint style="info" %}
**Storage Types:** Pharos uses Data Storage for active logs, optionally leverages File Storage for large attachments, and can archive historical data to Big Object Storage (separate allocation, 1M records free per org).
{% endhint %}

## What Impacts Storage Consumption

Several factors determine how much storage Pharos uses in your org. Understanding these drivers helps you estimate capacity needs and plan retention strategies:

| Factor                    | Impact                                 | Typical Range                                    |
| ------------------------- | -------------------------------------- | ------------------------------------------------ |
| **Org Complexity**        | More automations = more logs           | 10x variation between simple/complex orgs        |
| **Error Rates**           | Configuration issues drive volume      | Can spike 50-100x during incidents               |
| **Integration Activity**  | External API calls generate logs       | Proportional to transaction volume               |
| **User Base**             | More users = more activity = more logs | Linear scaling with active users                 |
| **Instrumentation Level** | Triton logging increases volume        | 2-5x increase with comprehensive instrumentation |

**Storage consumption examples:**

* **Small org** (50 users, basic automation): 10-50 logs/day ≈ 18-90 MB/year
* **Medium org** (200 users, extensive flows): 200-500 logs/day ≈ 365-900 MB/year
* **Large org** (1000+ users, complex integrations): 1,000-5,000 logs/day ≈ 1.8-9 GB/year

{% hint style="warning" %}
**Plan for Growth:** Log volumes typically grow alongside your Salesforce implementation. As you add automations, integrations, and users, expect proportional increases in log generation.
{% endhint %}

## Explore Log Storage Topics

<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>💿 Native Data Model</strong></td><td>The Pharos log data model, and how logs are stored as custom objects.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-storage/native-data-model.md">Native Data Model</a></td></tr><tr><td><strong>📊 Storage Usage</strong></td><td>Data storage usage, file storage usage, and log volumes.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-storage/storage-usage.md">Storage Usage</a></td></tr><tr><td><strong>⏳ Data Retention</strong></td><td>Configure retention rules to manage log storage via archival and removal strategies.</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-storage/data-retention.md">Data Retention</a></td></tr></tbody></table>

## Storage Management Strategy

Effective storage management balances three competing priorities: preserving historical data for analysis, maintaining query performance, and staying within storage capacity limits. The right approach depends on your organization's specific situation.

**Abundant Storage (< 70% capacity):**

When storage is plentiful, the best strategy is often doing nothing. Keep all historical data indefinitely to enable year-over-year comparisons, long-term trend analysis, and comprehensive root cause investigations. This maximizes the analytical value of your observability data without operational complexity.

**Moderate Pressure (70-80% capacity):**

As storage fills, implement conservative retention policies that remove genuinely old logs while preserving data valuable for troubleshooting and analysis. Consider 1-2 year retention periods for most log types, with longer retention for critical categories. Archive to Big Objects before removal to preserve historical records without consuming primary Data Storage.

**Constrained Capacity (> 80% capacity):**

When storage approaches limits, more aggressive action is necessary. Implement shorter retention periods (6-12 months), archive aggressively to Big Objects or external systems, or purchase additional Data Storage capacity. The most cost-effective solution depends on your specific constraints and the business value of historical data.

{% hint style="info" %}
**Recommendation:** Start without retention rules and monitor actual consumption for 30-60 days. This establishes your baseline and prevents prematurely deleting valuable data before understanding your org's patterns.
{% endhint %}

## Monitoring Best Practices

Regular storage monitoring prevents surprises and ensures your Pharos deployment remains healthy. Establish a monitoring cadence appropriate for your log volume and storage situation:

| Org Profile        | Monitoring Frequency   | Storage Alert Threshold | Recommended Action             |
| ------------------ | ---------------------- | ----------------------- | ------------------------------ |
| **New Deployment** | Weekly (first 90 days) | 70% capacity            | Establish baseline patterns    |
| **High Volume**    | Weekly                 | 75% capacity            | Proactive retention planning   |
| **Medium Volume**  | Bi-weekly              | 80% capacity            | Monitor trends, plan if needed |
| **Low Volume**     | Monthly                | 85% capacity            | Minimal intervention needed    |

**What to monitor:**

* Overall Data Storage percentage in Setup → Storage Usage
* Pharos-specific consumption in the storage breakdown table
* Growth rate (MB or GB per week/month)
* Log generation trends (logs per day by category)
* Any unexpected spikes indicating new problems

{% hint style="success" %}
**Pro Tip:** Add storage checks to your regular Salesforce admin checklist alongside other health monitoring activities. Consistent monitoring is more valuable than perfect frequency.
{% endhint %}
