Metadata Reference
Auto-generated reference for Nebula Logger.
Groupings:
- logger-engine - global Apex classes for adding entries, building payloads, and orchestrating saves.
- custom-objects -
Log__c,LogEntry__c,LogEntryEvent__e, and every custom metadata type Nebula Logger ships. Includes every field with full metadata (length, required, formulas, picklist values, security classification, and more). - lwc -
loggerandlogEntryBuilderclient-side APIs. - plugins - reference for each official plugin under
nebula-logger/plugins/. Public API, unlocked-package only.
For narrative and code examples, see the Logging Guide.
Metadata Reference
Section titled “Metadata Reference”Custom Objects
Section titled “Custom Objects”Used by Nebula Logger to unify all log entries generated in a single transaction
Used by Nebula Logger to represent a single log message within a transaction - log entries can be generated via Apex, Flow, Process Builder, Lightning Web Components, and Aura Components.
Used to configure regex-based rules in Nebula Logger to mask sensitive data in log entry fields, such as LogEntryEvente.Messagec and LogEntryc.Messagec
Platform Event object used by Nebula Logger for publishing debug and exception log entries
Used by Nebula Logger as a junction object to represent a unique relationship between a LogEntryc record and a LoggerTagc record
Used to configure rules in Nebula Logger to assign additional tags to LogEntry__c records based on field values
Used to configure custom field mappings in Nebula Logger to map data between LogEntryEvente and the custom objects Logc, LogEntryc, and LoggerScenarioc
Used to configure key-value pair parameters in Nebula Logger to control systemwide features
Used by Nebula Logger to store unique scenarios (text/String) that can be used to identify Logc and LogEntryc records via the lookup fields Logc.TransactionScenarioc and LogEntryc.EntryScenarioc
Used to configure rules in Nebula Logger to provide scenario-specific customizations
Used to configure hierarchial settings in Nebula Logger to provide user-specific & profile-specific customizations
Used to configure Apex trigger handler classes in Nebula Logger that run on the included objects LogEntryEvente, LoggerScenarioc, Logc, LogEntryc, LogEntryTagc, and LoggerTagc
Used by Nebula Logger for storing unique tags (text/String) that can be associated with LogEntryc records via the junction object LogEntryTagc
Used to configure in Nebula Logger which picklist values in Logc.Statusc are considered open/closed and resolved/unresolved
Logger Engine
Section titled “Logger Engine”A class that implements the standard interface System.Callable . This provides 2 benefits:
- A loosely-coupled way to optionally integrate with Nebula Logger (useful for ISVs/package developers).
- The ability to log in OmniStudio's OmniScripts & Integration Procedures.
Handles adding new log entries in Flow for a particular SObject record collection
Handles adding new log entries in Flow
Handles adding new log entries in Flow for a particular SObject record
Builder class that generates each LogEntryEvent__e record
The core class for logging
Provides the ability to generate string messages on demand, using String.format()