Automation Framework¶

The architecture standards that govern all automation in the org: which tool to use when, orchestration patterns, and the discipline that keeps automation reviewable.

Observability and Logging¶

Every automation layer (Apex, Flow, and Lightning components) logs through one centralised, Platform-Event-backed logging framework rather than System.debug or console.log. Nebula Logger is the reference implementation: log entries publish as platform events, so they survive transaction rollbacks, and log levels can be tuned per org, profile, or user without a deployment.

Do not let logs stop at the org. Connect the logging framework to the observability or SIEM platform the rest of the engineering stack already uses (Splunk, Datadog, Elastic, or similar): platform-event log entries can be streamed off-platform through the Pub/Sub API, CometD, or existing middleware, and the major platforms ship supported Salesforce integrations. Forwarding runtime logs to the same place that receives pipeline telemetry (see Governance at Scale) gives one console to alert on production errors, correlate application failures with the deployments that caused them, and retain logs beyond org storage limits.

Two rules govern the connection:

• Log payloads never contain PII, PHI, credentials, or session material. Once an event streams off-platform it is outside Salesforce's access controls, so the data classification of the log content sets the boundary, not the convenience of the integration.
• Streaming log events outside the org is an integration like any other: it goes through the same security review as every outbound connection, with a dedicated integration user and least-privilege access to the event channel.