Help
Not a customer? Start a free trial

Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.

Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

.Net Core issues

Go to solution
jonathan.sauter
Builder

‎06-13-2018 10:00 AM - edited ‎06-13-2018 10:01 AM

Hi,

 

I am trying to follow https://docs.appdynamics.com/display/PRO44/Install+the+.NET+Core+Microservices+Agent+for+Windows to setup a .net core app to be monitored on my controller.

 

Not sure what I am missing, but nothing ever appears on the SaaS controller I have setup as a trial.

 

I attempted this in a console app like the example, a asp.net core app and a docker containerized asp.net core app all with the same results.

 

Is there something else that I should be looking at to get this working?  As I have not done anything with appdynamics before, I could very well be missing some crucial step in getting this functional.

0 Kudos
6 REPLIES 6

Go to solution
jonathan.sauter
Builder

‎06-13-2018 02:48 PM

Discovered .net core 2.1 was logging an error around InjectMEE.  I downgraded to 2.0 and it seems to get further in the process.

 

Now fighting with applicationAdoptionStatus=WAITING_FOR_AGENT_TO_CONNECT on messages being sent out to my SaaS instance.  Seems like progress?

0 Kudos

Go to solution
Cody.Naumann
AppDynamics Team (Retired)
In response to jonathan.sauter

‎06-16-2018 06:29 AM - edited ‎06-16-2018 06:30 AM

Hi Jonathan,

 

We are actively exploring an issue with .NET Core 2.1: https://github.com/dotnet/coreclr/issues/18448 and https://community.appdynamics.com/t5/NET-Agent-Installation/AppDynamics-profiler-compatibility-issue... -- thanks for your patience while we look into this.

 

As it concerns the "Waiting to Connect" issue I saw a few posts that might help you troubleshoot:

 

https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Tomcat-Installation-Waiting-fo...

 

https://community.appdynamics.com/t5/Controller-SaaS-On-Premise/Java-agent-not-able-to-connect-to-th...

 

Thanks,

 

Cody

 

0 Kudos

Go to solution
jonathan.sauter
Builder
In response to Cody.Naumann

‎06-18-2018 07:49 AM - edited ‎06-18-2018 07:52 AM

So I discovered that the waiting to connect message was because I had the "add new application" dialog from the controller open and it was firing that message as it waited for my application to connect.  This is as designed.

 

Now my problem is, is that I cannot get my application to connect to the controller.  I can see the logs of the application and profiler get all the way to "Sending Registration request with: Application Name [DotNetCoreApplicationTest], Tier Name [TestSite], Node Name [TestNode], Host Name [CGL073028] Node Unique Local ID [TestNode], Version [4.4.3.0]" and then the whole application hangs and freezes visual studio 2017.

 

I am using core 2.0 and the latest versions of the IDE.  This happens in both a simple console application as well as a core asp.net website (out of the box config from VS).

 

Below are the agent logs, as I cannot attach the file as it is blocked.  It hangs at the last statement.

 

Ideas?

 

************************************************************

 

2018-06-15 15:40:51.0115 100756 dotnet 1 4 Info LifetimeManager Initializing via agent bootstrap
2018-06-15 15:40:51.0537 100756 dotnet 1 4 Info LifetimeManager Running non-obfuscated agent
2018-06-15 15:40:51.1105 100756 dotnet 1 4 Info LifetimeManager Agent version: 4.4.3.0
2018-06-15 15:40:51.1213 100756 dotnet 1 4 Info LifetimeManager .NET Version: 4.0.30319.42000
2018-06-15 15:40:51.1213 100756 dotnet 1 4 Info LifetimeManager .NET Framework Installation Registry Release DWORD: 461808
2018-06-15 15:40:51.1213 100756 dotnet 1 4 Info ManagedAgentAPI mscorlib version: System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e
2018-06-15 15:40:51.1399 100756 dotnet 1 4 Info ManagedAgentAPI mscorlib file version: 4.6.26328.01
2018-06-15 15:40:51.1399 100756 dotnet 1 4 Info ManagedAgentAPI using CLR4 function name resolver
2018-06-15 15:40:51.3559 100756 dotnet 1 4 Info ManagedAgentAPI Setting up CLR functionmap
2018-06-15 15:40:51.4536 100756 dotnet 1 4 Info ManagedAgentAPI Set CLR implemented methods map. Number of entries is: 576
2018-06-15 15:40:51.4536 100756 dotnet 1 4 Info ManagedAgentAPI Setting up CLR functionmap done
2018-06-15 15:40:51.4755 100756 dotnet 1 4 Info Configuration appDomainName=CoreConsoleTest appDomainId=1 iis-app=CoreConsoleTest.dll site=null port=null appPoolId= commandLine=C:\Users\dev\CoreConsoleTest\CoreConsoleTest\bin\Debug\netcoreapp2.0\CoreConsoleTest.dll
2018-06-15 15:40:52.3888 100756 dotnet 1 4 Info StandaloneConfigLoader {
"controller": {
"host": "********.saas.appdynamics.com",
"port": 443,
"account": "******",
"password": "***",
"ssl": true,
"enable_tls12": true,
"proxy": null
},
"application": {
"name": "DotNetCoreApplicationTest",
"tier": "TestSite",
"node": "TestNode"
},
"instrumentors": {
"enable": [],
"disable": []
}
}
2018-06-15 15:40:52.4063 100756 dotnet 1 4 Info Configuration Running Pro Agent
2018-06-15 15:40:52.5552 100756 dotnet 1 4 Info DotNetAgent ####################################################################################
2018-06-15 15:40:52.6339 100756 dotnet 1 4 Info AgentKernel Starting .NET Agent at 6/15/2018 9:40:52 PM ...
2018-06-15 15:40:52.6339 100756 dotnet 1 4 Info AgentKernel Time zone: Mountain Daylight Time
2018-06-15 15:40:52.8746 100756 dotnet 1 4 Info XMLConfigManager Orchestration is disabled - disabling virtualization resolvers by default.
2018-06-15 15:40:53.0886 100756 dotnet 1 4 Info XMLConfigManager Default IP Address Resolver found IP addresses [[10.0.75.1, 10.9.8.93, 172.30.246.17, 172.24.176.1]]
2018-06-15 15:40:53.1301 100756 dotnet 1 4 Info XMLConfigManager Full Agent Registration Info Resolver using selfService [False]
2018-06-15 15:40:53.1420 100756 dotnet 1 4 Info XMLConfigManager Full Agent Registration Info Resolver using application name [DotNetCoreApplicationTest]
2018-06-15 15:40:53.1420 100756 dotnet 1 4 Info XMLConfigManager Full Agent Registration Info Resolver using tier name [TestSite]
2018-06-15 15:40:53.1420 100756 dotnet 1 4 Info XMLConfigManager Full Agent Registration Info Resolver using node name [TestNode]
2018-06-15 15:40:53.1515 100756 dotnet 1 4 Info XMLConfigManager XML Controller Info Resolver found controller host [*************.saas.appdynamics.com]
2018-06-15 15:40:53.1515 100756 dotnet 1 4 Info XMLConfigManager XML Controller Info Resolver found controller port [443]
2018-06-15 15:40:53.1657 100756 dotnet 1 4 Info XMLConfigManager XML Agent Account Info Resolver using account name [singularity-agent@************]
2018-06-15 15:40:53.1657 100756 dotnet 1 4 Info XMLConfigManager XML Agent Account Info Resolver using account access key [****]
2018-06-15 15:40:53.1968 100756 dotnet 1 4 Info XMLConfigManager Configuration Channel is using ControllerInfo:: host:[************.saas.appdynamics.com] port:[443] sslEnabled:[true] keystoreFile:[DEFAULT:cacerts.jks] use-encrypted-credentials:[False] secureCredentialStoreFileName:[] secureCredentialStorePassword:[] use-ssl-client-auth:[unknown] asymmetricKeysStoreFilename:[] asymmetricKeysStorePassword:[] asymmetricKeyPassword:[] asymmetricKeyAlias:[] validation:[UNSPECIFIED]
2018-06-15 15:40:53.3832 100756 dotnet 1 4 Info AgentConfigWatchdog Agent overwrite set to False
2018-06-15 15:40:53.3832 100756 dotnet 1 4 Info AgentConfigWatchdog Parsed 0 filters from <sensitive-data-filters> section
2018-06-15 15:40:53.3832 100756 dotnet 1 4 Info AgentConfigWatchdog Parsed 0 filters from <sensitive-url-filters> section
2018-06-15 15:40:53.3979 100756 dotnet 1 4 Info XMLConfigManager Node will not be marked as historical at shutdown
2018-06-15 15:40:53.4205 100756 dotnet 1 4 Info AgentKernel Running non-obfuscated agent
2018-06-15 15:41:00.6087 100756 dotnet 1 4 Info AgentKernel No debugger attached
2018-06-15 15:41:00.7230 100756 dotnet 1 4 Info MetricHandler Metric Service is : [enabled].
2018-06-15 15:41:00.7339 100756 dotnet 1 4 Info LifeCycleManager Starting service [DynamicServiceManager]
2018-06-15 15:41:00.7339 100756 dotnet 1 4 Info DynamicServiceManager Loading dynamic service com.appdynamics.ee.service.analytics.Analytics
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Started service [DynamicServiceManager]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Starting service [AgentOperationService]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Service instantiated reflectively AgentOperationService :classcom.appdynamics.ee.agent.appagent.services.agentoperation.AgentOperationsService
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Started service [AgentOperationService]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Starting service [BCIEngine]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Started service [BCIEngine]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Starting service [CLRMetricsService]
2018-06-15 15:41:00.7639 100756 dotnet 1 4 Info LifeCycleManager Service instantiated reflectively CLRMetricsService :classcom.appdynamics.ee.agent.appagent.services.CLRService.CLRMetricsService
2018-06-15 15:41:00.7859 100756 dotnet 1 4 Info LifeCycleManager Started service [CLRMetricsService]
2018-06-15 15:41:00.7941 100756 dotnet 1 4 Info LifeCycleManager Starting service [SnapshotService]
2018-06-15 15:41:00.8085 100756 dotnet 1 4 Info TransactionSnapshotService Agent object monitoring is disabled
2018-06-15 15:41:00.8085 100756 dotnet 1 4 Info TransactionSnapshotService Coalesced Call-Stack Sampling is: disabled
2018-06-15 15:41:00.8085 100756 dotnet 1 4 Info TransactionSnapshotService CallStackSampler TryLock bounds in Micro Sec: 500
2018-06-15 15:41:00.8085 100756 dotnet 1 4 Info TransactionSnapshotService Enable-Contention-Tracking property set to: True
2018-06-15 15:41:00.9567 100756 dotnet 1 4 Info TopBackendsProcessor Started TopBackendsProcessor to process every [100] ms
2018-06-15 15:41:00.9567 100756 dotnet 1 4 Info TopBackendsProcessor Started TopBackendsReporter to report every [5] mins
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphConfigHandler Call Graph Config Changed callgraph-granularity-in-ms Value -
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphConfigHandler Call Graph Config Changed show-packages Value -
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphFilteringConfig Setting Callgraph package LOCAL always show []
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphConfigHandler Call Graph Config Changed dont-show-packages Value -
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphFilteringConfig Setting Callgraph package LOCAL excludes []
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info CallGraphConfigHandler Call Graph Config Changed hotspot-granularity-in-ms Value -
2018-06-15 15:41:00.9644 100756 dotnet 1 4 Info RequestSegmentDataReporter Request Segment Data reporter setup to report at interval [10000]
2018-06-15 15:41:00.9785 100756 dotnet 1 4 Info ApplicationStartupPolicy Startup policy False
2018-06-15 15:41:01.0088 100756 dotnet 1 4 Info LifeCycleManager Started service [SnapshotService]
2018-06-15 15:41:01.0088 100756 dotnet 1 4 Info LifeCycleManager Starting service [TransactionMonitoringService]
2018-06-15 15:41:01.0088 100756 dotnet 1 4 Info AsyncCorrelationADDRepository Started ADD registration thread to run every [10] seconds
2018-06-15 15:41:01.0088 100756 dotnet 1 4 Info AsyncCorrelationADDRepository Max ADD registrations allowed [500]
2018-06-15 15:41:01.0088 100756 dotnet 1 4 Info AsyncCorrelationADDRepository Reporting ADD registration failures every [5] minutes
2018-06-15 15:41:01.1693 100756 dotnet 1 4 Info SlowAndStallRequestMonitor Stall Request checker setup
2018-06-15 15:41:01.1693 100756 dotnet 1 4 Info SlowAndStallRequestMonitor Slow Request checker setup to check for requests slower than 300 ms, at interval 300 ms.
2018-06-15 15:41:01.1871 100756 dotnet 1 4 Info LoggerMessageProcessor LoggerMessageProcessor is scheduled to run: com.appdynamics.ee.util.csspecific.scheduler.AgentScheduledFutureImpl
2018-06-15 15:41:01.1961 100756 dotnet 1 4 Info AgentErrorProcessor AgentErrorProcessor is scheduled to run: com.appdynamics.ee.util.csspecific.scheduler.AgentScheduledFutureImpl
2018-06-15 15:41:01.1961 100756 dotnet 1 4 Info ErrorRegistry Error Registry initialized
2018-06-15 15:41:01.2243 100756 dotnet 1 4 Info ThreadCPUTimeCalculator BT CPU Monitoring will stay enabled ... Time taken to calculate Thread CPU Time for [1000] iteration [1] < [10]
2018-06-15 15:41:01.2282 100756 dotnet 1 4 Info ServiceEndPointADDRegistrar Starting ADD Registrar with registration period [10] secs
2018-06-15 15:41:01.2282 100756 dotnet 1 4 Info AsyncExitADDRegistrar Starting ADD Registrar with registration period [10] secs
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> setting [use-new-async-correlation] to True
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [use-flat-thread-chain-model] to True
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [bSyncMetricAggregator] to True
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [asyncAllMetrics] to
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [useNewEJB3NamingRule] to False
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [disableSocketCollection] to False
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [devModeSuspendCPM] to 500
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [jdbcLRUCacheSize] to 50
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [support-cross-app-correlation] to True
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> [support-federated-app-correlation] to True
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> ["+TransactionMonitorProperty.CHECK_BT_EXCLUDES_EARLY+"] to False
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> ["+TransactionMonitorProperty.disableInfoProviderMBean+"] to False
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> ["+TransactionMonitorProperty.infoProviderDetailMode+"] to False
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> ["+TransactionMonitorProperty.maxETELatencyTimestampRetentionInSeconds+"] to 300
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService TMS.Configure >> ["+TransactionMonitorProperty.eteLatencyTimestampScanRetentionIntervalInSeconds+"] to 60
2018-06-15 15:41:01.2443 100756 dotnet 1 4 Info TransactionMonitoringService Initialized [NEW] TransactionDelegate
2018-06-15 15:41:01.2659 100756 dotnet 1 4 Info LifeCycleManager Started service [TransactionMonitoringService]
2018-06-15 15:41:01.2974 100756 dotnet 1 4 Info ConfigurationChannel Sending node name: TestNode
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel Detected node meta info:
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:windows-process-id, Value:100756]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:dotnet-os-ver, Value:Microsoft Windows NT 6.2.9200.0]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:clr-architecture, Value:AMD64]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:appdomain, Value:CoreConsoleTest]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:process-identity, Value:SJRB\jsauter]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:configuration-file, Value:]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:appdomain-id, Value:1]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:ProcessID, Value:100756]
2018-06-15 15:41:01.4234 100756 dotnet 1 4 Info ConfigurationChannel [Name:iis-virtual-path, Value:/]
2018-06-15 15:41:01.4393 100756 dotnet 1 4 Info ConfigurationChannel Detected node meta info: [Name:appdynamics.ip.addresses, Value:10.0.75.1,10.9.8.93,172.30.246.17,172.24.176.1, Name:supportsDevMode, Value:true]
2018-06-15 15:41:01.4499 100756 dotnet 1 4 Info ConfigurationChannel Sending Registration request with: Application Name [DotNetCoreApplicationTest], Tier Name [TestSite], Node Name [TestNode], Host Name [CGL073028] Node Unique Local ID [TestNode], Version [4.4.3.0]

0 Kudos

Go to solution
Raunak.Mohanty
AppDynamics Team (Retired)
In response to jonathan.sauter

‎06-19-2018 10:56 PM

Seems like Agent is not able to connect to Controller. Are you able to access the SAAS Controller from the same server? If yes can you try port 80 and turn ssl and tls off and see if Agent is able to register successfully.

Thanks,
Raunak

Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
0 Kudos

Go to solution
jonathan.sauter
Builder
In response to Raunak.Mohanty

‎06-20-2018 10:09 AM

Same result with:

 

{
"controller": {
"host": "*********.saas.appdynamics.com",
"port": 80,
"account": "*******",
"password": "********",
"ssl": false,
"enable_tls12": false
},
"application": {
"name": "DotNetCoreApplicationTest",
"tier": "TestSite",
"node": "TestNode"
}
}

 

Note that this is my developer machine... not a server.

 

I have a screen share booked with support today, so maybe it will help to have you all look at it directly.

0 Kudos

Go to solution
jonathan.sauter
Builder
In response to Raunak.Mohanty

‎06-20-2018 12:21 PM - edited ‎06-20-2018 01:03 PM

So, I spoke with one of your support people on a webex and discovered that it was visual studio hanging on debugging of the application. 

 

If I ran it as a standalone executable and let it sit long enough, it would connect and create the application.

 

Right now I am updating VS to see if that resolves the issue as there was a release today around other similar areas.  

 

Hope this helps someone out!

 

- EDIT:  I upgraded to the lastest VS version and had to disable intellitrace to get the debugger working again.  Not sure if the update was necessary though.

Join Us On December 10
Learn how Splunk and AppDynamics are redefining observability

Register Now!
Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!

Read the blog here
Top Kudoed Authors
View all

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form

By clicking subscribe, I have read and understood the Privacy Policy and Terms of Use.
Platform
Solutions
Learn

Company
Support