> 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/open-telemetry/hermes.md).

# Hermes

Hermes is Pharos's Salesforce → OpenTelemetry product family: Iris and Argus turn Salesforce telemetry into OTel signals from inside your own cloud.

Hermes is Pharos's Salesforce → OpenTelemetry product family, generally available as part of the Pharos platform. It runs entirely in **your own cloud** — Pharos never phones home, and never receives or stores the telemetry Hermes exports. Hermes ships as a single Docker image, `pharosai/hermes:<version>`, bundling multiple runtime binaries; a given deployment runs only the ones it needs.

***

## Two Channels

Hermes converts two different kinds of Salesforce telemetry into OpenTelemetry signals:

| Channel   | Source                                                       | Code changes required                            |
| --------- | ------------------------------------------------------------ | ------------------------------------------------ |
| **Iris**  | Pharos/Triton application telemetry (`pharos__Log_Event__e`) | None beyond your existing Triton instrumentation |
| **Argus** | Salesforce Event Monitoring                                  | **Zero** — Argus runs standalone                 |

Iris bridges the application-level telemetry your Triton instrumentation already produces. Argus ingests Salesforce's own operational and security telemetry — no Triton, no code changes to your org.

***

## Deploy Targets

Hermes deploys the same Docker image to whichever platform your team already runs:

* **ECS Fargate** (AWS) — provisioned by four staged Terraform modules
* **Azure Container Apps** — provisioned by four staged Terraform modules
* Plain **Docker** / docker-compose — for local runs and trials

See [Architecture](https://docs.pharos.ai/open-telemetry/hermes/architecture.md) for how one image supports many runtime binaries, and [Configuration](https://docs.pharos.ai/open-telemetry/configuration.md) for the cloud deployment runbooks.

***

## Three Signals From One Event

A single Salesforce event — an Apex transaction, a login, a report run — carries more than one observable dimension. Hermes converts it into up to three correlated OTel signals: a **span** for the execution itself (something Event Monitoring alone can't produce on its own), a **metric** for volume, latency, and governor-limit consumption, and a **log** for auth, security, and state-change facts. Not every event produces all three signals — the shape is declared per event type in the mapping YAML — but the result is one coherent picture per event, across signals.

***

## 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>🏛️ Architecture</strong></td><td>One Docker image with many runtime binaries, deterministic trace identity, and a shared mapping engine.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/architecture.md">Architecture</a></td></tr><tr><td><strong>🌈 Iris</strong></td><td>The Triton/Pharos application-telemetry bridge, converting existing Triton instrumentation into OTel spans, metrics, and logs.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/iris.md">Iris</a></td></tr><tr><td><strong>👁️ Argus</strong></td><td>The Salesforce Event Monitoring bridge, ingesting operational and security telemetry across real-time (RTEM) and batch (ELF).</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/argus.md">Argus</a></td></tr><tr><td><strong>🔗 Cross-Surface Correlation</strong></td><td>How Hermes keeps one Salesforce session and request as one trace across the Iris and Argus channels.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/correlation.md">Cross-Surface Correlation</a></td></tr><tr><td><strong>🎯 Backends &#x26; Routing</strong></td><td>OTLP routes behind one shared exporter, with direct and Collector modes for sampling and fan-out.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/backends.md">Backends &amp; Routing</a></td></tr><tr><td><strong>📊 Scaling Profiles</strong></td><td>Shared local/standard/scaled tiers, with the achievable ceiling set by how Salesforce delivers each telemetry kind.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/scaling.md">Scaling Profiles</a></td></tr><tr><td><strong>📐 Sizing &#x26; Cost</strong></td><td>Starting compute shapes per profile, the ELF load-unit model, and the AWS/Azure cost model.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/sizing-and-cost.md">Sizing &amp; Cost</a></td></tr><tr><td><strong>🔐 Security</strong></td><td>Runs entirely in your own cloud with read-only Salesforce access, JWT Bearer auth, and configurable redaction.</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/security.md">Security</a></td></tr></tbody></table>
