Jonathan Gillespie
Jonathan Gillespie
@arbokrad asked [on SFXD](https://discord.com/channels/246568944213819393/561552810009952278/1438597990888767568) about giving non-admins the ability to make some edits to logging data: > nebula question for you - if we want to have some users able...
For many orgs/teams/people, the usage of Nebula Logger is abstracted away to an org-specific class. This is done for a variety of reasons, including... - It can help with migrating...
In Apex, certain Apex classes can be omitted from stack traces (and stack trace parsing) using `Logger.ignoreOrigin(System.Type)`. In the `logger` LWC, there should be an equivalent option to support skipping...
In [the current version](https://github.com/jongpie/NebulaLogger/blob/v4.16.4/nebula-logger/core/main/logger-engine/classes/LogEntryEventBuilder.cls#L943) of `LogEntryEventBuilder`, it only checks the field `LoggerSettings__c.IsApexSystemDebugLoggingEnabled__c` to determine if it should call `System.debug()`. But for the managed package (any managed package), calling `System.debug()` won't...
Using the `LoggerParameter__mdt` record `RequireScenarioUsage`, admins/devs can choose to enforce the usage of logger scenarios in their orgs. This feature was added in [release `v4.13.3`](https://github.com/jongpie/NebulaLogger/releases/tag/v4.13.3), but it looks like (the...
There should be some way within the `logBatchPurge` LWC to... - View any scheduled instances of `LogBatchPurgeScheduler` - The ability to delete scheduled instances - The ability to add new...