You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sfdx force:apex:log:tail -d DEBUGLEVEL IGNORES the specified debug level. I've done countless tests of this over weeks and can confirm that the above command will NOT use the debug level specified. The command will ONLY use the SFDC_DevConsole debug level. This is not optimal as the settings on that debug level aren't "sticky" resulting in too much data that a developer did not ask for in the logs.
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
Summary
sfdx force:apex:log:tail -d DEBUGLEVEL
IGNORES the specified debug level. I've done countless tests of this over weeks and can confirm that the above command will NOT use the debug level specified. The command will ONLY use the SFDC_DevConsole debug level. This is not optimal as the settings on that debug level aren't "sticky" resulting in too much data that a developer did not ask for in the logs.Steps To Reproduce:
sfdx force:data:record:create -s DebugLevel -t -v "DeveloperName=SFDX_Logging MasterLabel=SFDX_Logging Database=INFO Workflow=NONE Validation=NONE Callout=INFO ApexCode=DEBUG ApexProfiling=NONE Visualforce=INFO System=NONE Nba=NONE Wave=NONE"
to create a Debug Levelsfdx force:apex:log:tail -d SFDX_Logging
to start loggingExpected result
The log levels should 100% match the log levels associated with the named
DEBUGLEVEL
passed toforce:apex:log:tail
Actual result
The log levels used appear to be the levels associated with the
SFDC_DevConsole
Debug Level.System Information
Which shell/terminal are you using? bash
If you are using
sfdx
sfdx version --verbose --json
If you are using
sf
sf version --verbose --json
Paste the output here
Additional information
Feel free to attach a screenshot.
The text was updated successfully, but these errors were encountered: