Binding Runtime Errors are not Associated with the operation_Name (Application Insights)

Hello Team -

Noticed that binding errors are not associating with a operation_Name and its not showing up in the Application Insights Portal though its there in the Exception schema table (App Insights Analytics ).

E.g , lets say, I have a model library..Contoso.API.Model.dll and I have few model classes in that dll..(eg. Employee, Department etc.)

Now, in the actual function referring that dll and using the model in the http trigger function method to get the model (from the API post) to be bind. While testing we saw that, when the model dll was not referenced client was getting an Internal Server error from the API but nothing logged in the monitor section / logs.

Same case with any missing dependencies like nugget package.

Was able to get it by digging into the Application Insights analytics using the following query ( exceptions | take 50 )

It was showing as System.TypeLoadException. Noticed that the operation_Name is empty for that type of exceptions. I think that might be reason it’s not showing up in the failures request category in Application Insights. I can see that anything with “Operation_Name” value coming up in the application inisghts UI reports. Is there a way to link these kind of errors into the same request as I think its going to be difficult to troubleshoot the issues without proper linking.

Function Runtime Host : 2.0

Regards,
Sowmyan