I have added an Azure Functions C# project to my Aspire AppHost, and it contains several functions using various timer, storage queue, blob, and Cosmos DB triggers. We have Azurite spun up by Aspire as the Functions host storage and where the queues live. The storage queue trigger in particular is very noisy in the logs when running in Aspire. There are two main areas this affects: the console logs view, and the traces view.

For the console logs view, it's not as much of a problem, since you can filter to specific resources. But if you have it set to "(All)" resources or the storage account, it is showing every single polling request for the queue messages, with several entries per second. It quickly builds up to many thousands of lines of logs.

The traces view is much worse: it adds several traces per second, drowning out legitimate traces of real requests to the app. These are all for BlobContainerClient.GetBlobs (for the blob triggers) and QueueClient.Exists (for the queue triggers). It honestly is so noisy that it ruins the value of using Aspire for distributed tracing, when these traces are providing no value and the app is sitting there doing nothing. I only want to see traces if there is actually a blob or queue message that triggers a function.

Here is what my traces view looks like:

Has anyone found a good solution to this, without i.e. switching to a timer trigger? Even if the solution is just slowing down the polling to once a minute or something that would be better than this. Thanks in advance!