Isolated Azure Function and logs generated by Triggers e.g. Service Bus and/or Event Hubs

We have migrated all of our Azure Functions from In-Process C# .NET 6 to Isolated Azure Functions based on .NET 8.

In our In-Process implementation we have been heavily using Telemetry Processors to filter what gets send to Application Insights, since the Triggers for Service Bus & Event Hubs are quite verbose when it comes to transient errors that will reported as error.

With the switch to the Isolated Azure Functions this concept isn't working any longer and just setting the SDK behind the Triggers to a Log Level Fatal might also suppress some of the Errors that might be relevant.

So my question is how can we filter those transient errors being send to application insights, since they happening a lot during function app scaling up/down.

Start by reviewing isolated Azure Functions logging and Application Insights configuration, focusing on the Service Bus and Event Hubs trigger logs and how telemetry processors differ from the In-Process model. Done should mean transient scaling-related errors can be filtered without suppressing relevant errors.

Written by the indexing model from the issue text.