Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Wcf Service calling another Wcf service loose track #149

Open
vdesmedt opened this issue Jun 15, 2018 · 4 comments
Open

Wcf Service calling another Wcf service loose track #149

vdesmedt opened this issue Jun 15, 2018 · 4 comments

Comments

@vdesmedt
Copy link

I have built a very simple web app calling a wcf service calling itself another wcf service. Using fiddler, I can see that the x-ms-request-root-id is different for both wcf calls which result in the correlation to be lost. Any idea what could help ?

@SergeyKanzhelev
Copy link
Contributor

is it async wcf service? CC: @lmolkova

@lmolkova
Copy link
Member

@vdesmedt
Unfortunately, we do not support correlation within WCF service. You may implement the workaround from this issue: https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/941.

By the way, this is Labs repo - WCF support here is not included when you install ApplicationInsights Web SDK.

@vdesmedt
Copy link
Author

@SergeyKanzhelev No it isn't even async, just pure old fashion WCF calls ;)
@lmolkova I'll investigate the workaround. Thanks

@mlooise
Copy link

mlooise commented Jul 23, 2018

@vdesmedt Have you got more info on this subject? Does the workaround of https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/941 work to track the dependency to another AI resource ?

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

No branches or pull requests

4 participants