Replies: 1 comment 4 replies
-
@bachuv, @sebastianburckhardt: is this something you two would know about? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I haven't seen too many people talking about this so trying to find some answers as to what I'm seeing here. I've used ITelemetryInitializer before and have a class
ExceptionDataInitializer: ITelemetryInitializer
that I'm registering in the Startup of my .NET 6 Azure Durable Function application like sobuilder.Services.AddSingleton<ITelemetryInitializer, ExceptionDataInitializer>();
I've done this with other projects (without durable functions/entities) and it works great to be able to add data into the
customDimensions
section of a record in the Azure Application Insights for any Exception that happens. But, for a new project we've decided to give Durable Entities a try, and want to use this same ExceptionDataInitializer. One thing I immediately noticed when trying it was that the properties we'd expect in the exception logs, are not there. We know that usingSignalEntityAsync
puts the handler into a queue that Durable Functions then handles in the background, but it seems to not be using the registered initializer when it runs into exceptions and sends them out to application insights.Is there something I'm missing here? I would assume that the runtime for the Durable Functions/Entities would still be using the registered services from the Startup.
Thanks :)
Beta Was this translation helpful? Give feedback.
All reactions