.NET Questions about WCF, HttpClient, Async-Await, Threads

[CommunityUser]

Hi,

i am evaluating for my company a APM solution.

The followinf things did not work OOTB and some other i have questions about.

1. I do not see our outgoing WCF calls anywhere. The code is generated from WSDL and the binding is basicHttpBinding. Any ideas?
2. Not all outbound calls are catched (only the ones using the older WebRequest)
   1. HttpClient is not supported?
   2. CouchBase client needs custom config?
   3. Redis?
3. On a slow transaction the monitoring shows onlty the Thrad.Join on a started thread, missing all the actual work that is done in the thread. Is this expected?
4. Is async-await and TPL supported?
5. Do i have control over the scaling of custom Performance counter?

Thanks

[Jean-Baptiste_M]

Dear Sotirios
We would need a bit more details to help you on this matter.
What is your application server?
You can check this supported environment list here:
https://docs.appdynamics.com/display/PRO42/Supported+Environments+and+Versions
That sometimes gives you details on how to configure for specific
technologies.

Are you in touch with an AppDynamics person or a partner of AppDynamics?
Best
JB

[Jean-Baptiste_M]

Dear Sotirios
We would need a bit more details to help you on this matter.
What is your application server?
You can check this supported environment list here:
https://docs.appdynamics.com/display/PRO42/Supported+Environments+and+Versions
That sometimes gives you details on how to configure for specific
technologies.

Are you in touch with an AppDynamics person or a partner of AppDynamics?
Best
JB

[CommunityUser]

Hi,

looking through that list we should be fine.

Windows Server 2008 R2

.Net 4.5.2 etc

I am in touch with Conrad Stevens and possibly a local (greek) partner.

[Jean-Baptiste_M · Accepted solution]

Ok so then maybe you need to check that:
https://docs.appdynamics.com/display/PRO42/Asynchronous+Exit+Points+for+.NET
And enabling thread correlation.

Sorry, I didn't see in the topic you put .Net, my bad 😉

JB

[CommunityUser]

Thanks very much.

Why is this not enabled by default? Parfomance impact?

[Jean-Baptiste_M]

Not performance impact but application impact. In certain cases, it might
break the downstream application receiving a message with a modified HTTP
header or an additional JMS property (our correlation ID).
To be tested in non-prod env first.
Sending you an email we can take this offline!
JB

[Jean-Baptiste_M]

Not performance impact but application impact. In certain cases, it might
break the downstream application receiving a message with a modified HTTP
header or an additional JMS property (our correlation ID).
To be tested in non-prod env first.
Sending you an email we can take this offline!
JB

[Jean-Baptiste_M]

Ok so then maybe you need to check that:
https://docs.appdynamics.com/display/PRO42/Asynchronous+Exit+Points+for+.NET
And enabling thread correlation.

Sorry, I didn't see in the topic you put .Net, my bad 😉

JB