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

# Argus

Argus is the Salesforce Event Monitoring bridge — it ingests operational and security telemetry with zero code changes over two surfaces, RTEM and ELF.

Argus is the channel of Hermes that bridges Salesforce's own **Event Monitoring** telemetry into OpenTelemetry — with **zero code changes** to your org. Unlike Iris, Argus doesn't depend on Triton instrumentation at all: it reads operational and security events Salesforce already produces. Argus runs standalone across two surfaces:

| Surface  | Delivery                             | Nature    |
| -------- | ------------------------------------ | --------- |
| **RTEM** | Platform Events over the Pub/Sub API | Real-time |
| **ELF**  | `EventLogFile` records over REST     | Batch     |

***

## Three Signals From Event Monitoring

Argus applies the same "three signals from one event" model as the rest of Hermes, wired through a **logs-half conformance model**:

* **"Errors become exceptions" (global).** Any Event Monitoring row that carries an error field also emits an OTel **log** with `exception.type`, `exception.message`, and `exception.stacktrace`. The stacktrace is populated **only when a real column exists** — Argus never fabricates a stacktrace.
* **Per-family primary logs.** Five event families — **Auth & session**, **Security**, **Content & files**, **Metadata / setup-audit**, and **Platform-integration** — name **Log** as a primary signal in their own right, each with a stable `event.name` (for example `salesforce.auth.logout` or `salesforce.security.*`), independent of whether an error occurred.

![Salesforce operational and security events as OpenTelemetry logs (e.g. salesforce.auth.logout) in Grafana Loki.](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-f4998b1dfad786a512a177a2bb2d48c059ec1043%2Fgrafana-logs-drilldown.png?alt=media)

***

## Signal-Shape Taxonomy

Not every Event Monitoring type emits the same combination of signals. Each type is mapped to one of the following shapes:

* **S + M** — span and metric, no log.
* **S + M + error-log** — span and metric, plus an error log when the failure signal fires.
* **S + M + always-emit event-log** — span and metric, plus an unconditional audit log.
* **L + M, no span** — a primary log and metric, with no span at all.
* **L only** — a primary log, with no span and no metric.

The shape is declared per event type in the shared YAML mapping engine — see [Pipeline Config](https://docs.pharos.ai/open-telemetry/configuration/pipeline-config.md).

***

## 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>⚡ Real-Time Event Monitoring</strong></td><td>Platform Events over the Pub/Sub API — threat-detection, channel coverage, scaling</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/argus/rtem.md">Real-Time Event Monitoring</a></td></tr><tr><td><strong>📑 EventLogFile</strong></td><td>Batch CSV log pulls over REST — sharding, live vs. backfill, coverage</td><td><a href="https://docs.pharos.ai/open-telemetry/hermes/argus/elf.md">EventLogFile</a></td></tr></tbody></table>
