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

If telemetry correlation module is not first in the list of modules - correlation doesn't work #17

Open
SergeyKanzhelev opened this issue May 3, 2017 · 2 comments

Comments

@SergeyKanzhelev
Copy link
Contributor

Customer complained that telemetry from BeginRequest or custom IHttpModule wasn't correlated properly. We need to:

  • check that xdt will attempt to insert correlation module first in the list.
  • can we detect not being the first and report a warning that Application Insights can pick up and report to the customer.
@lmolkova
Copy link

lmolkova commented May 5, 2017

Was it implemented in AI already?

@SergeyKanzhelev
Copy link
Contributor Author

Nope. it doesn't matter much for Application Insights as Request Telemetry will be instantiated and start on the first telemetry item we try to report.

Telemetry Module have to be started before any telemetry.

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

No branches or pull requests

2 participants