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
User functions have a single global log level. It would beneficial to enable an consistent mechanism to add filter logging prior to the logs hitting app-insights.
The text was updated successfully, but these errors were encountered:
As Anthony already mentioned, you could use host.json config to specify your log level. For Python specifically, we have a change that is pending deployment to fix DEBUG log level bug: #735
Many python libraries set their level to 'info' and include debug information at that level, including Azure SDK libraries. I want to set the info level for my app's logs, but not all of the logging from all of the libraries that I use.
If this was a standard python app, I would setup a logging.basicConfig with the default level to warning, then set my app specific logger to INFO. However, I don't have a direct handle to the azure functions worker's logging handle.
I could update the context of the azure_functions_worker.logger.handler on every execution to add this filtering, that seems fragile.
User functions have a single global log level. It would beneficial to enable an consistent mechanism to add filter logging prior to the logs hitting app-insights.
The text was updated successfully, but these errors were encountered: