Hello,
I have problem collecting data from .NET-application in Azure Cloud Services.
Some background information
1) We are using Azure Cloud Services (Web & Worker roles)
2) We deploy our application to staging slot. We are using AppDynamics NuGet-package and startup.cmd is run after every deployment. After
deployment we swap staging & production slots and shutdown staging machine. This means one virtual machine does not live long.
3) Our Worker role we launches several executables we want to monitor. Executables are named Visma.AutoReport.ServiceHost.Loader64.exe and
have have 16 of these processes running. We also have one Visma.AutoReport.ServiceHost.Loader32.exe running.
Current situation with AppDynamics is:
- Website role is gathering data ok
- Data from worker role is not always delivered to AppDynamics. We see nodes in Tiers & Nodes, but they are randomly reporting data
We see following errors in log files:
2016-12-14 09:08:32.1633 2032 Visma.AutoReport.ServiceHost.Loader64 2 13 Warn MetricHandler Metric Reporter Queue full. Dropping metrics.
2016-12-14 09:08:40.2303 2032 Visma.AutoReport.ServiceHost.Loader64 2 13 Warn ConfigurationChannel Problem with appagent registration.
Status:Application Component Node with name [Visma.AutoReport.Service_IN_0] already exists for Component with name
[Visma.AutoReport.CoreService]. The existing Application Component Node has id [29811]. If you specified the JVM property
[appdynamics.agent.uniqueHostId] for the Application Agent, you MUST set this JVM property to the same value for the Machine Agent that is
associated with this Application
2016-12-14 09:08:40.2303 2032 Visma.AutoReport.ServiceHost.Loader64 2 13 Warn ConfigurationChannel Auto agent registration FAILED! Check the
controller log for details.
2016-12-14 09:08:58.8761 2908 WaWorkerHost 2 22 Warn ConfigurationChannel Problem with appagent registration. Status:Application Component
Node with name [Visma.AutoReport.Service_IN_0] already exists for Component with name [Visma.AutoReport.WorkerHost]. The existing Application
Component Node has id [29857]. If you specified the JVM property [appdynamics.agent.uniqueHostId] for the Application Agent, you MUST set this
JVM property to the same value for the Machine Agent that is associated with this Application
2016-12-14 09:08:58.8761 2908 WaWorkerHost 2 22 Warn ConfigurationChannel Auto agent registration FAILED! Check the controller log for
details.
Can you help us? For me it's not clear why metric reporter queue is full and why appagent registration fails.
Here is agentlog attached. I removed all sensitive data. In 09:18 there is couple of exceptions during VIP swapping due network connectivity drops for couple of seconds. In this setup we only have two Visma.AutoReport.ServiceHost.Loader64 executables running.