Hi,
I have 3 tiers set up as .Net Azure Cloud Services.
1 is a .Net MVC web role.
2 are .Net Api web roles.
All 3 are individual cloud services on azure. The MVC role communicates with both .Net Apis. Both Apis also talk to the same Azure SQL database.
The agents seem to have loaded up all 3, named correctly etc, however the following issues are seen:
- Load is only present for the .Net MVC tier.
- The MVC tier shows the communication to the 2 Apis as BackEnd services.
- No load is shown on the Api tiers.
The cloud service setups are near identical (except the names of projects and cloud services, etc) so I'm just wondering if anyone can advise.
Thanks,
I've been further investigating. If I create fresh applications (MVC -> WebApi -> Get google.com), then the OOTB support works. I can see the path through them and all the nodes are reporting.
I have THEN added a CNAME XXX.XXX.com to point at XXXXX.cloudapp.net. This was done for the WebApi.
The flow map then broke. MVC showed it was not talking to anything, but WebApi showed the backend service of google.com and that it was getting data from there.
Has anyone else done anything with CNAMEs infront of Azure Cloud Service's xxxx.cloudapp.net ?? I have a feeling that is the actual issue...
Thanks,
Remving the tier and allowing it to recreate fixes the CNAME issue.
Within the two api projects we are using OWIN.
One, the actual resources are being accessed through it. The other it is only validating a JWT token, but the resource is still on a WebApi controller within the project.
Has anyone had any experience of using AppDynamics on a .Net web project with OWIN?
Hi,
We see same issue when using Owin as underline technology.
Appdynamics is not able to capture transaction name automatically.
Few Setting can be changed here to capture transaction details
Application -> App Servers - > Agents -> Configuration -> find-entry-points - set it to true
( to check the entry point)
and in
Configuration
Select Application - > .Net -> Configure Rules -> Add rule (+) -> .net Class /method - >
add following details
Match Class ( with a class Name That ) Equals System.Web.HttpApplication
Method Name Equals BeginProcessRequestNotification
It will be good if you know the class name and method name( you can directly add these details) and app dynamics will start instrumentation