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
With the logging property for host.json we've have the 6 levels as defined here and they are all working as expected, but the function runtime outputs a large amount of information about when a function is Executed/Executing. I couldn't find solid documentation when it comes to turning off the runtime Executed/Executing messages without also disabling my own log messages at the Information level as defined.
Given the following example it would be helpful to know if there is an option for more granular control:
loggging.logLevel.default = Information
Executed 'Functions.SomeFunction' (Succeeded, Id=SomeId)
Did some work in SomeFunction
Executing 'Functions.SomeFunction' (Reason='', Id=SomeId)
What I would expect is that Executed/Executing logs would be running at the Trace/Debug level rather than the Information level, but when setting the log level higher than Information to something like Warning is predictably suppressing my own log messages resulting in the following:
logging.logLevel.default = Warning
Are there ways of configuring the host.logging property to restrict the logging of the Executed/Executing information or do I just need to break the Log Level definitions and make my messages all 1 level higher? I'd prefer not to do the latter as that could cause some problems capturing invalid warnings and being altered to false positives.
The text was updated successfully, but these errors were encountered:
Unfortunately, the way the log categories are set currently, I think we need to specify a rule for every function. @brettsam is there a better way to do this or are there any improvements planned in this area?
With the
logging
property forhost.json
we've have the 6 levels as defined here and they are all working as expected, but the function runtime outputs a large amount of information about when a function isExecuted/Executing
. I couldn't find solid documentation when it comes to turning off the runtimeExecuted/Executing
messages without also disabling my own log messages at theInformation
level as defined.Given the following example it would be helpful to know if there is an option for more granular control:
loggging.logLevel.default = Information
What I would expect is that
Executed/Executing
logs would be running at theTrace/Debug
level rather than theInformation
level, but when setting the log level higher thanInformation
to something likeWarning
is predictably suppressing my own log messages resulting in the following:logging.logLevel.default = Warning
Are there ways of configuring the
host.logging
property to restrict the logging of theExecuted/Executing
information or do I just need to break the Log Level definitions and make my messages all 1 level higher? I'd prefer not to do the latter as that could cause some problems capturing invalid warnings and being altered to false positives.The text was updated successfully, but these errors were encountered: