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

add feature - track header data for ajax & fetch requests' response and put to part c properties bag #946

Merged
merged 11 commits into from
Jul 23, 2019

Conversation

xiao-lix
Copy link
Contributor

@xiao-lix xiao-lix commented Jun 25, 2019

Adding feature of tracking response headers data of ajax and fetch requests in dependency plugin. This feature is off by default. It can be turned on by setting the config flag "enableHeaderTracking: true" when initializing the ApplicationInsights instances. All data are stored in customer properties bag.

Example of Fetch request result in Azure Portal:
fetch

Example of Ajax request result in Azure Portal:
ajax

Related issue: #736

Copy link
Contributor

@markwolff markwolff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also include in your PR a screenshot of the result in the Portal. as well as a description of what it does? off-by-default, etc

@markwolff markwolff added this to the 2.1 milestone Jul 2, 2019
@markwolff markwolff modified the milestones: 2.1, 2.2 Jul 16, 2019
Copy link
Contributor

@markwolff markwolff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this also track correlation headers that this SDK sets on http requests?

@xiao-lix xiao-lix merged commit 70650f1 into master Jul 23, 2019
@xiao-lix xiao-lix deleted the users/lxiao/trackingHeader branch July 23, 2019 22:01
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

Successfully merging this pull request may close these issues.

4 participants