-
-
Notifications
You must be signed in to change notification settings - Fork 230
Reconsider how LoggerScenarioRule__mdt and LoggerSettings__c apply #941
Copy link
Copy link
Open
Labels
Feature: Data MaskingFeature: Log RetentionItems related to LogBatchPurger or LogBatchPurgeSchedulerItems related to LogBatchPurger or LogBatchPurgeSchedulerFeature: Scenario-Based LoggingItems related to Logger.setScenario(), LoggerScenarioRule__mdt, etc.Items related to Logger.setScenario(), LoggerScenarioRule__mdt, etc.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: Log ManagementItems related to the custom objects & Logger Console appItems related to the custom objects & Logger Console appLayer: Logger EngineItems related to the core logging engineItems related to the core logging engineSalesforce Feature: SecurityItems related to the security model (object-level access, field-level security, record sharing)Items related to the security model (object-level access, field-level security, record sharing)Type: EnhancementNew feature or requestNew feature or request
Description
Metadata
Metadata
Assignees
Labels
Feature: Data MaskingFeature: Log RetentionItems related to LogBatchPurger or LogBatchPurgeSchedulerItems related to LogBatchPurger or LogBatchPurgeSchedulerFeature: Scenario-Based LoggingItems related to Logger.setScenario(), LoggerScenarioRule__mdt, etc.Items related to Logger.setScenario(), LoggerScenarioRule__mdt, etc.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: Log ManagementItems related to the custom objects & Logger Console appItems related to the custom objects & Logger Console appLayer: Logger EngineItems related to the core logging engineItems related to the core logging engineSalesforce Feature: SecurityItems related to the security model (object-level access, field-level security, record sharing)Items related to the security model (object-level access, field-level security, record sharing)Type: EnhancementNew feature or requestNew feature or request
Currently, there are 2 main (and overlapping) ways to control several features within Nebula Logger
LoggerSettings__ccustom hierarchy settings object: used to control the default org settings, as well as overrides for profiles and usersLoggerScenarioRule__mdtcustom metadata type: used to overrideLoggerSettings__cfor a particular scenario (denoted by specifying a string value as the scenario, via Apex, Flow, or Lightning Components)This was designed this way to help with large orgs/teams, where logging needs can vary within the codebase/metadata. For example:
INFOas the org default, andDEBUGfor some profiles & admins (configured viaLoggerSettings__c)LoggerScenarioRule__mdtto adjust settings for their "module"The problem currently is there's not a way to have different settings within a scenario. For example, if a developer wants to change the logging level to
FINESTfor a particular user(s), within a particular scenario, there's not currently a way to do that.All of this needs to be revisited (along with #940) to see if changing how scenario rules & user settings are applied could better handle these kinds of situations.