Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I suppose you have already gone through following document
In case you have any specific questions/issues please let us know.
Indeed .... we have it configured like that ... but think there is a gap in some respect.
BizTalk generally has receive and process hosts in addition to send hosts ...
Why does AppD only look at the send hosts ....
Biztalk has components built in both C++ and .net. .Net agent would not be able to instrument unmanaged code in Biztalk(c++). Which restricts .net agents ability to add visibility on non .net components.
When some application makes the exit calls to biztalk is important point to track and that is why .net agent supports WCF Send Port or the SOAP Send Port.
On recive ports the messages are recieved and processing is done inside an unmanged part of the Biztalk, which mostly can not be tracked by .net agent.
Using the BizTalk performance counters you get some more insights into overall Biztalk execution.