How to disable Storage Queue logs from spamming?

Question

I get so much of

Request [xxx] GET xxx

and

Response [xxxx] 200 OK (00.0s)

I tried multiple of logLevel setting

"logLevel"
	 
	"Host.Results"
	"Function"
	"Host.Aggregator"
	"Azure.Storage.Queues"
 },

        "logLevel": {
            "default": "Information",
            "Host.Results": "Information",
            "Function": "Information",
            "Host.Aggregator": "Information",
            "Azure.Core": "Warning"
        },

and bunch of other combinations. nothing works.

Answer 1

@engineer

You’ve already tried adjusting the log levels, but let’s refine it further.

Modify your host.json to set the Azure.Core log level to "Error"

"logLevel": {
            "default": "Information",
            "Azure.Core": "Error"
        }

This should suppress the detailed request and response logs for the Azure.Storage.Blobs assembly.

Refer: https://stackoverflow.com/questions/73901031/how-to-remove-azure-storage-blobs-logging-from-azure-function-app-logs

---

If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.

Answer 2

Hi @engineer , I understand that you want to disable your Storage Account - Queue - Diagnostics Setting.

As you mentioned that you're getting a lot of logs, there's a Diagnostic Setting configured in your Azure Storage Queue. You can delete the Diagnostic Setting to stop collecting logs, or modify the setting to collect less logs.

Open your Azure Portal, go to your Storage Account, click on "Diagnostic settings" under Monitoring menu on the left.

Click on "queue", then delete or modify your existing Diagnostic setting.

Refer to Azure Queue Storage Diagnostic Setting for more information on the categories of operations that you can collect logs on.

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.