Why has all logging stopped in my org?

[longtallmatt]

We're running v4.16.5 and started using the tool back in October. We've been seeing logs on a semi-daily basis since. However, nothing has been logged for the last week, so, I used anonymous apex to create a log and got no result. The output looks okay, I tried querying the Log__c object directly and still no new records. Any ideas anyone?

15:02:54.759 (759551768)|CODE_UNIT_STARTED|[EXTERNAL]|execute_anonymous_apex
15:02:54.759 (793575739)|USER_DEBUG|[131]|INFO|Nebula Logger - Version Number: v4.16.5
15:02:54.759 (793690221)|USER_DEBUG|[132]|INFO|Nebula Logger - Transaction ID: 906a731d-5e12-4ff3-93b9-329c40572f49
15:02:54.759 (793735521)|USER_DEBUG|[133]|INFO|Nebula Logger - Request ID: SLB:edc6677b2016425ff4f6493ec4e98603
15:02:54.759 (794453560)|USER_DEBUG|[134]|INFO|Nebula Logger - Organization API Version: v65.0
15:02:54.818 (818953419)|CUMULATIVE_LIMIT_USAGE

[jamessimone]

I would try to see whether or not the LogEntryEvent__e platform event is actually getting delivered

[jongpie]

@longtallmatt I would also check the LoggerSettings__c data in your org (either with the included custom "Logger Settings" tab/LWC, or under Setup --> Custom Settings --> Logger Settings), it could be that someone has changed the settings in your org, resulting in logging data from being saved.

[AndyHaas]

You can try using Jetstream to subscribe to events.
https://getjetstream.app/app/platform-event-monitor

[jamessimone]

Nebula Logger has a built-in event streaming component within the Nebula Logger application

[AndyHaas]

Well that too lol. Many tools to stream the PE's lol.

[longtallmatt]

Good morning folks, thanks for getting back to me. I think that there may be nothing wrong, I've done some further research and found the following.
@jongpie, thanks for the suggestion, the created and modified dates match. This is the setup:

I spun up a new dev org and played around with the Save Method - I tried them all with no result. So I swapped to the Logging Level and ran through those and Hey Presto! I got a hit. I had been using Logger.debug(...) for my test and the level is set to ERROR. It was only when I lowered the Logging Level that I got the result.

So, my test to find a problem was the problem... I guess that the system really is working without a hitch - it'll never last!

@jongpie, so, can I assume that the Logging Level is the minimum level to trigger log entry creation?