Azure ServiceBus Trigger Log Filtering

Question

Azure ServiceBus Trigger Log Filtering

vincent219 256

I'm using Azure Functions v3 with .NET.

HTTP communication occurs when certain Azure ServiceBus Triggers process messages.

The problem is, if logLevel is set to Information in host.json, when I record at Information level through the Logger received through FunctionContext.GetLogger("FunctionName"), even HTTP logs are output to the console window, making it difficult to distinguish them.

If I set logLevel to Warning as a trick, the HTTP log is not output because it is at the Information level, and I can record the log as Warning level through the Logger.

It is not an expedient like the above method, but I would like to record only the contents I record with the code as information and not record the other logs.

Is there any way to solve this?

Accepted answer

0 additional answers

Your answer

Answer 1

MughundhanRaveendran-MSFT 12,506

@vincent219 ,

Thanks for reaching out to Q&A.

From the loglevel perspective, we have multiple options but "information" is the closest that you can get to log the flow of your function. There are other configurations however they will either get removed or add more information which will add complexity

Configure log levels: https://learn.microsoft.com/en-us/azure/azure-functions/configure-monitoring?tabs=v2#configure-log-levels

The best approach is using Application insights where you can record only specific contents and set the sampling settings as mentioned in the following article.

https://learn.microsoft.com/en-us/azure/azure-monitor/app/ilogger

https://learn.microsoft.com/en-us/azure/azure-functions/configure-monitoring?tabs=v2#configure-sampling

I hope this helps!

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

vincent219 256 Reputation points

2022-01-18T02:10:25.383+00:00

If you look at the picture above, the logs in dark green are logs that I do not need and are marked as Information level.

Yellow is the log I marked and marked as Warning level.

I'm not familiar with Application Insight.
If I use Application Insight, can I delete the information log visible on the console screen and record the log I wrote as a warning at the information level and display it on the screen?
MughundhanRaveendran-MSFT 12,506 Reputation points

2022-01-24T10:26:33.87+00:00

@vincent219 , Using iLogger, you can print only necessary output in the logs
https://learn.microsoft.com/en-us/azure/azure-functions/functions-dotnet-class-library?tabs=v2%2Ccmd#ilogger

Before trying the above approach, you can try setting the Host.Aggregator to Error in Host.json and see if that helps

"logLevel": {
"default": "Information",
"Host": "Error",
"Function": "Error",
"Host.Aggregator": "Error"
}
vincent219 256 Reputation points

2022-01-28T04:12:06.5+00:00

thank you.
It works the way I want it to.

vincent219 256

Even if you install the 'Microsoft.Extensions.Logging' Nuget package and follow the method below, the same filtering is applied and it is recorded at the shared level.

.ConfigureLogging((hostingContext, logging) =>
{
    logging.AddFilter("System.Net.Http", LogLevel.Warning);
    logging.AddFilter("Microsoft.Hosting.Lifetime", LogLevel.Warning);
    logging.AddFilter("System.Net.Http.HttpClient.Default.LogicalHandler", LogLevel.None);
    logging.AddFilter("System.Net.Http.HttpClient.Default.ClientHandler", LogLevel.None);
    logging.AddFilter("System.Net.Http.HttpClient.TimeoutHttpClient.LogicalHandler", LogLevel.None);
    logging.AddFilter("System.Net.Http.HttpClient.TimeoutHttpClient.ClientHandler", LogLevel.None);
})

Share via

Azure ServiceBus Trigger Log Filtering

0 additional answers

Your answer