NebulaLogger
NebulaLogger copied to clipboard
Add the ability to declaratively ignore origin Apex classes
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 away from a legacy logging system to Nebula Logger
- It provides people a way to easily migrate away (😢 ) from Nebula Logger
In these situations, the additional Apex class created will show up in Nebula Logger's stack traces - to avoid this, Apex developers can call Logger.ignoreOrigin(System.Type). But that involves a strategically-placed extra line of code. It'd be nice to also introduce a new LoggerParameter__mdt record that can be used to declaratively ignore any specified origins.
I would be glad to start working on this, I don't know if this is something you already solution or actively working on @jongpie