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

# Extensibility & Integrations

Pharos is open by design — native APIs, platform events, webhooks, a rules engine, external integrations, AI-agent operability, and OpenTelemetry export.

Being native to Salesforce doesn't make Pharos a closed system—it makes it an *open* one. Because every observability record is a standard Salesforce object, everything you can do with Salesforce data you can do with Pharos data. On top of that native foundation, Pharos adds deliberate extension points at every layer: data goes **in** through open instrumentation, flows **out** through standard APIs and OpenTelemetry, and the platform itself can be **operated and automated**—by your tools, your rules, and even AI agents.

***

## Get Data In: Open Instrumentation

Pharos captures signals automatically, but you're never limited to what it captures out of the box.

* **Triton** — an open-source instrumentation framework for **Apex, LWC, and Flow**. Add explicit log points to your own code, propagate a single transaction identity across runtimes, and feed those signals into the same pipeline as everything else. See [Pharos Triton Instrumentation](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-ingestion-methods/pharos-triton-instrumentation.md).
* **Connected orgs** — bring logs from multiple Salesforce environments into one place.
* **Standard entry points** — automated error tracking, platform events, and email services capture signals with zero custom code.

## Get Data Out: Open Standards, No Lock-In

Your observability data belongs to you, and Pharos is built to let it travel.

* **Native Salesforce APIs** — because logs, issues, and everything else are custom objects, they're fully available through REST/SOAP/Bulk APIs, reportable with standard tools, and queryable via SOQL.
* **OpenTelemetry export** — stream Salesforce telemetry (Triton application logs *and* Salesforce Event Monitoring) as standard OTel spans, metrics, and logs to Honeycomb, Splunk, Datadog, Grafana, and other OTLP backends. Salesforce stops being the one system your enterprise observability stack can't see. See [Open Telemetry](https://docs.pharos.ai/open-telemetry/open-telemetry.md). *(Early-access capability.)*
* **Webhooks** — push events to any HTTP endpoint for custom downstream automation.

## Act on Signals: Integrations

Pharos plugs into the tools your teams already work in, so observability drives action instead of sitting in a dashboard.

* **Notifications** — Slack, Microsoft Teams, PagerDuty, Email, and Webhooks.
* **Ticketing** — two-way integration with Jira and Azure DevOps.
* **Change tracking** — GitHub-backed metadata history for correlating errors with deployments.
* **AI** — bring your own AI provider to power Org Genie analysis.

See the [Integrations](https://docs.pharos.ai/configuration-guide/integrations.md) overview for the full set.

## Automate: The Rules Engine

A flexible, native rules engine drives behavior across the platform—**alerting, ticketing, monitoring, retention, and masking** all run on the same configurable foundation. Rules react to the signals Pharos captures and take the actions you define, so the platform adapts to your org's conventions rather than forcing you into a fixed workflow. See [Rule-based Configuration](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/rule-based-configuration.md).

## Operate with AI Agents

Extensibility isn't only about data and rules—it's about *operability*. Through the **`@pharosai/mcp`** server, any MCP-capable AI agent can operate Pharos directly: investigate issues, correlate logs and changes, run AI root-cause analysis, and (with confirmation) triage, trace, and open tickets—all in plain language. It's the read/act counterpart to Triton's write side. See [AI Agents & MCP](https://docs.pharos.ai/configuration-guide/integrations/ai-agents-mcp.md).

***

## Why It Matters

| Extension point                | What it enables                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------ |
| **Native APIs & objects**      | Report, extend, and export with standard Salesforce tools—no proprietary layer       |
| **Triton instrumentation**     | Capture exactly the signals your custom code should emit                             |
| **OpenTelemetry export**       | Unify Salesforce into your existing enterprise observability stack                   |
| **Webhooks & platform events** | Wire Pharos into any downstream system                                               |
| **Rules engine**               | Automate alerting, ticketing, monitoring, retention, and masking to your conventions |
| **AI-agent operability**       | Investigate and act in natural language, from the tools you already use              |

The throughline: Pharos gives you **broad insight into Salesforce operations** and then gets out of your way—open enough to fit whatever else you run.

***

## Related

<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>🛰️ Open Telemetry</strong></td><td>Export Salesforce telemetry to any OTLP backend</td><td><a href="https://docs.pharos.ai/open-telemetry/open-telemetry.md">Open Telemetry</a></td></tr><tr><td><strong>🤖 AI Agents &#x26; MCP</strong></td><td>Operate Pharos in natural language from any MCP agent</td><td><a href="https://docs.pharos.ai/configuration-guide/integrations/ai-agents-mcp.md">AI Agents &amp; MCP</a></td></tr><tr><td><strong>🧩 Integrations</strong></td><td>Notifications, ticketing, change tracking, and AI</td><td><a href="https://docs.pharos.ai/configuration-guide/integrations.md">Integrations</a></td></tr><tr><td><strong>📐 Rule-based Configuration</strong></td><td>The engine that automates platform behavior</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/rule-based-configuration.md">Rule-based Configuration</a></td></tr></tbody></table>
