-
-
Notifications
You must be signed in to change notification settings - Fork 207
Open
Labels
Layer: ConfigurationItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeLayer: Logger EngineItems related to the core logging engineItems related to the core logging engineLogging Source: ApexItems related to using Logger within ApexItems related to using Logger within ApexType: EnhancementNew feature or requestNew feature or request
Milestone
Description
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.
Metadata
Metadata
Assignees
Labels
Layer: ConfigurationItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeItems related to the custom hierarchy setting LoggerSettings__c or any included custom metadata typeLayer: Logger EngineItems related to the core logging engineItems related to the core logging engineLogging Source: ApexItems related to using Logger within ApexItems related to using Logger within ApexType: EnhancementNew feature or requestNew feature or request