You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a custom HttpApplication class defined in our Global.asax which has an event handler Application_EndRequest
When this handler executes, I expected it to be within the current Activity but it was not, as the event registered by TelemetryCorrelationHttpModule had executed first. This causes any spans (we're using open-telemetry) created in our EndRequest event to appear as if they started after the root span has finished.
Is there a way to ensure our Application_EndRequest event is executed before the one defined in this http module?
The text was updated successfully, but these errors were encountered:
We have a custom HttpApplication class defined in our
Global.asax
which has an event handlerApplication_EndRequest
When this handler executes, I expected it to be within the current Activity but it was not, as the event registered by TelemetryCorrelationHttpModule had executed first. This causes any spans (we're using open-telemetry) created in our EndRequest event to appear as if they started after the root span has finished.
Is there a way to ensure our
Application_EndRequest
event is executed before the one defined in this http module?The text was updated successfully, but these errors were encountered: