Feature Request: Add native capability to link file attachments to Log Entries

[vikashkrml]

New Feature Summary

Currently, developers frequently need to tie rich transaction data (such as raw JSON integration payloads, large XML packets, or debug CSV files) to a specific LogEntry__c record. While Nebula Logger easily logs string properties, string fields are strictly limited by Salesforce's field data limits and text area sizing.

Storing exceptionally large blobs within long text area fields can lead to truncation issues. Furthermore, downloading a physical, properly formatted file directly from the Salesforce Files related list offers a much cleaner user experience for administrators diagnosing complex errors.

[jongpie]

Hi @vikashkrml could you give some more details & examples of how you would want this functionality to work? Would there need to be new methods (or other changes) in Nebula Logger?

[vikashkrml]

Hi @jongpie I’d like to propose a new feature to allow users to attach files directly to Log Entry records.

Currently, when dealing with large JSON/XML payloads that exceed the Message field limits, we have to truncate the data. Providing an option to automatically generate and attach the full payload as a file would ensure no data is lost and keep the complete log accessible.

Implementation-wise, we could introduce a new method dedicated to creating and attaching these files to the corresponding log record.

I'm more than happy to own the development for this. Once we finalize the approach, I can get started. Let me know your thoughts, or if you're open to a quick sync to discuss further!

Thanks!

[jongpie]

Hi @vikashkrml you are more than welcome to explore this idea, but I am skeptical that it can implemented in a reliable way.

• If an exception occurs in Apex, the creation of a document/attachment would be automatically rolled back by Salesforce, so attachments wouldn't be possible when exceptions occur.
  • One of the only reliable ways to save data even when an exception occurs is using platform events/the event bus - they aren't rolled back when an exception occurs.
• Linking the attachment to a Log__c or LogEntry__c record will be somewhat difficult - those records are created asynchronously, but the attachments would (presumably) be created synchronously (before the Log__c or LogEntry__c records are created).

Let me know your thoughts on these concerns - if you know of ways to overcome them, then I think this could be doable, but I'm personally not sure how to handle them.