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
The request ID is currently generated randomly; telemetry clients that get attached to the requests that are passed into the views have their parent operation ID set to the same. The missing piece is reading it in from the header.
I was wrong. The request id should continue to be generated randomly. The operation_ParentId and operation_Id should be read from the Request-Id and Correlation-Context headers according to the flat/hierarchical request specification
Add support for Correlation headers [1] in the Django Middleware.
Basic support would involve reading
Request-Id
in the header, and outputting asoperation_Id
in the telemetry.[1] https://docs.microsoft.com/en-us/azure/application-insights/application-insights-correlation#correlation-headers
The text was updated successfully, but these errors were encountered: