-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Logging level debug does not work in local or portal logs #735
Comments
Just synced with my team offline @vrmdr and @stefanushinardi The I think the Thanks for reporting this issue. |
@ijoosong - can you please share your Default log level is set to {
"version": "2.0",
"logging": {
"LogLevel": {
"Default": "Debug"
}
},
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[1.*, 2.0.0)"
}
} |
@pragnagopa I've tried this and it doesn't work :( |
@ijoosong We've figured out the fix and I'll send out the fix post-testing. |
Thanks @pragnagopa, @vrdmr and @stefanushinardi for the offline sync up.
Since the GRPC logging handler is attached onto the root logger, currently we have a concern on the performance when dropping the |
How do we configure debug logging for workers logs from the host side? Is there an app setting that the host can pass in? |
@vrdmr The host redirect all stdout and stderr from the Python process into asp.net logging infra. They don't control logging level in Python worker, they're just filtering the worker logs. |
Awesome thanks @vrdmr when will this change go live? |
We are planning to get the new releases of the Python worker to go out by next week, I'll update you once that is done. |
@vrdmr is this out now? |
@ijoosong it is released in function runtime v4 right now. Please refer to https://docs.microsoft.com/en-us/azure/azure-functions/functions-app-settings#python_enable_debug_logging for more details how to turn on user function debug logging. |
Investigative information
Please provide the following:
In any python function, log level debug does not display in both local and portal logs.
Repro steps
Provide the steps required to reproduce the problem:
Expected behavior
Provide a description of the expected behavior.
Actual behavior
Provide a description of the actual behavior observed.
Known workarounds
Provide a description of any known workarounds.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Related information
Provide any related information
The text was updated successfully, but these errors were encountered: