The Complete Guide: Step-by-Step Implementation
If you are looking to build this exact architecture yourself, here is the complete, advanced implementation process from start to finish.
Phase 1: Environment Readiness & Nebula Installation
Before configuring the framework, you must deploy the Nebula Logger managed package or unmanaged source code into your Dev Org.
Log in to your Salesforce Developer Org.
Open a browser tab and navigate to the latest stable release on the official Nebula Logger GitHub Repository.
Scroll down to the Installation section. For a standard Dev Org environment, click the Production/Developer Org package link.
Select Install for All Users to ensure your profiles and permission sets map correctly across system contexts, then click Install.
Alternative (CLI Method): Run the following SFDX command in your terminal:
sf package install --package 04t5G000004Yv9dQAC --wait 10 --target-org my-dev-org
Phase 2: Architecting the Custom Logger Security Layer
Nebula Logger ships with robust, pre-built permission sets to ensure data integrity and prevent unauthorized access to sensitive application logs.
Go to Setup > Users > Permission Sets.
Locate the two primary permission sets deployed by the framework:
LoggerAdmin: Grants complete administrative control to view, purge, and modify configuration settings.
LoggerLogCreator: Grants runtime execute and create permissions allowing code contexts to write logs without viewing administrative data.
Click on LoggerAdmin, select Manage Assignments, click Add Assignments, select your System Administrator user, and click Assign.
Phase 3: High-Performance Configuration (Logger Settings)
Hardcoding logging parameters limits scalability. Nebula uses hierarchical custom settings to control logging behavior dynamically based on user, profile, or organization-wide defaults.
Navigate to Setup > Custom Code > Custom Settings.
Find Logger Settings (LoggerSettings__c) and click Manage.
Click New directly above the organization-wide defaults section.
Configure the following high-performance parameters:
Is Logging Enabled: True (Checked)
Default Logging Level: Set to DEBUG for comprehensive developer visibility.
Enable Apex System Logging: True
Default Log Retention Days: Set to 7 days to prevent excessive data consumption in your Dev Org.
Click Save.
Phase 4: Declarative Automation Integration (Flows)
Your logging framework should catch errors wherever they occur. Let's configure a declarative Flow with a resilient fault-handling pattern.
Go to Setup > Process Automation > Flows and click New Flow.
Select Record-Triggered Flow on the Account object, optimized for Actions and Related Records.
Drag an Update Records element onto the canvas to perform a standard update on the parent account.
Hover over the element, click Add Fault Path to branch execution if the transaction fails.
Add an Action element to the Fault Path wire. Search for the core Nebula action: Logger: Record Log Entry.
Map the parameters as follows:
Connect the output of the action to an immediate Save or screen element if applicable to handle the exception gracefully.
Phase 5: Writing Enterprise Backend Code (Apex)
To leverage the full capabilities of the logging engine, we implement a defensive coding pattern using a dedicated controller class.
If you are looking to build this exact architecture yourself, here is the complete, advanced implementation process from start to finish.
Phase 6: Building the Frontend Interface (LWC)
Frontend runtime environments frequently mask critical user exceptions. We build a Lightning Web Component to bridge client-side telemetry into the unified backend log records.
Phase 7: Verification and End-to-End Testing
Open any Account Record Page in your Dev Org and click Edit Page via the gear icon.
Drag the newly built nebulaLogButton component onto your page canvas and save/activate it.
Return to the live application workspace and click Trigger Runtime Exception.
Navigate to the App Launcher (grid icon in the top left) and search for Log Entries or Logs.
Open the latest log record. You will see a comprehensive diagnostic breakdown—including the full client-side JavaScript stack trace, user profile context, running browser specifications, and platform limits utilization metrics—captured cleanly within your Salesforce dashboard!