When Salesforce processing is performed off-platform (e.g., in an integration tool like Workato, MuleSoft, or a custom service), there's currently no built-in way to surface those log messages back in Salesforce via Nebula Logger. The only option is to manually construct and publish LogEntryEvent__e platform events, which requires the caller to know the internal field structure of the event.
I propose A @RestResource-enabled Apex class that accepts a simple payload and handles event construction internally would solve this cleanly. Callers could POST a minimal JSON body (logging level, message, optional record/record ID, optional exception details, optional tags) and Nebula Logger would take care of building and publishing the LogEntryEvent__e correctly — including field validation, truncation handling, and tag processing.
This would make Nebula Logger usable as a centralized logging layer across the entire Salesforce ecosystem, not just within the platform itself.
PS: Let me know if such a feature would be welcome; I'd be happy to take a stab at building this if so -- I may do so outside of the package anyways for an implementation in my organization.
When Salesforce processing is performed off-platform (e.g., in an integration tool like Workato, MuleSoft, or a custom service), there's currently no built-in way to surface those log messages back in Salesforce via Nebula Logger. The only option is to manually construct and publish LogEntryEvent__e platform events, which requires the caller to know the internal field structure of the event.
I propose A @RestResource-enabled Apex class that accepts a simple payload and handles event construction internally would solve this cleanly. Callers could
POSTa minimal JSON body (logging level, message, optional record/record ID, optional exception details, optional tags) and Nebula Logger would take care of building and publishing the LogEntryEvent__e correctly — including field validation, truncation handling, and tag processing.This would make Nebula Logger usable as a centralized logging layer across the entire Salesforce ecosystem, not just within the platform itself.
PS: Let me know if such a feature would be welcome; I'd be happy to take a stab at building this if so -- I may do so outside of the package anyways for an implementation in my organization.