PlatformEventSubscriberConfigs for Nebula logging

[KumaranM2040]

Hi @jongpie

I am not seeing a PlatformEventSubscriberConfigs for Pub/Sub implementation of logging. Are we using the defaults ? Im currently seeing an issue where nebula logs are not being persisted, when Save Method is set to EVENT_BUS. I am seeing massive delays when processing logs and im not sure whether it related to the Platform subscriber configuration for the subscriber.

I am using Nebula v4.15.7 on developer pro org ( but am not seeing any visible limits being hit)

Kind regards
Kumaran M

[jonathankretzmer]

Further information on this one...

It appears almost as though the trigger subscription to the platform event fails and no longer delivers the event to Nebula for saving.

If we go into Setup, Platform Events, click on MANAGE the subscription to the LogEntryEvent event, click on Suspend then Resume, it reverts back to expected behaviour and saves logs again (only new ones). However, later in the day, it stalled again.

We have tried various avenues to try and find relevant logs for this but have come up short. We even tried liaising with Salesforce Support who seemed to be unable to give us any indication of why this may be.

Changing the behaviour to SYNCHRONOUS_DML works fine, but does not fix with our use.
Also, this seems to be isolated to only one of our sandboxes; the others and production seem to be okay.

[arunkumar15-shell]

Hi @KumaranM2040
I'm planning to use this logger in my project. I want to understand all the risks and limitations of this logger.
Can you please explain, what exactly the issue you are facing and how can I replicate in my environment .

[KumaranM2040]

Hi @arunkumar15-shell .

I would defintely recommend using the logger. We are currently using it in our production environment. As with any integration there are some risks involved however the value add that we have received from nebula outweigh any issues.

Our issue as described by @jonathankretzmer comment involves two scenarios:

1. No Log Entry rows were getting persisted in the LogEntry__c object. It was as if the Nebula Platform Event subscriber was not being notified of platform events.
2. Delayed processing of Log entries when save method is set to EVENT_BUS - This has occurred sometimes however we are not sure why there is a lag behind processing.

Regarding the point 1 above, we do not suspect that this is due to Nebula logger itself but a Salesforce Platform Issue which the SF support team are investigating. The toggling of the suspend/resume button does kick start the processing of events in Nebula however we are not sure why we have to do this, as the subscription is still active.