Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Correlation headers in the Django Middleware #55

Closed
twschiller opened this issue Sep 15, 2017 · 2 comments
Closed

Support Correlation headers in the Django Middleware #55

twschiller opened this issue Sep 15, 2017 · 2 comments

Comments

@twschiller
Copy link

Add support for Correlation headers [1] in the Django Middleware.

Basic support would involve reading Request-Id in the header, and outputting as operation_Id in the telemetry.

[1] https://docs.microsoft.com/en-us/azure/application-insights/application-insights-correlation#correlation-headers

@jjjordanmsft
Copy link
Contributor

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.

@twschiller
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants