Hi I've got some machine agent installations where I'm getting messages like this: [#|2021-08-02T14:38:39.254+1000|WARNING|glassfish 4.1|com.appdynamics.SIM|_ThreadID=80;_ThreadName=http-listener-2(7);_TimeMillis=1627879119254;_LevelValue=900;|#SIM000121 The maximum number of monitored processes per machine allowed has been reached for machine 33. The limit sim.processes.count.maxPerMachine is set to 1000 processes. This limit will be reset after the next process purging or when some processes are deleted by the user. Could not create 9 processes for machine 33|#] I then go look at machine 33, and find that it's got numerous duplicates of the same processes, varying only in start/end time. It seems like if I increase the maxPerMachine limit, we'll just delay running into the limit again because it's constantly using up the count for the same processes over and over. This seems like a bug. Is there some workaround? ... View more

A page about the .NET agent says: "The AppDynamics .NET Agent includes an embedded .NET Machine Agent that runs as part of the AppDynamics.Agent.Coordinator service. Among other things, the Machine Agent regularly gathers system performance data and reports it back to the Controller as metrics." To simplify our deployment I've uninstalled the standalone (java) machine agent from one of our servers in favour of the "embedded .NET Machine Agent" mentioned above, but now there's no machine level metrics coming through at all. I found the following in AgentLog.txt: 2021-08-03 14:44:00.0257 11408 AppDynamics.Coordinator 1 9 Info RegistrationChannel Auto agent registration attempted: Application Name [My application name] Component Name [Machine Agent] Node Name [My node name] 2021-08-03 14:44:00.0257 11408 AppDynamics.Coordinator 1 9 Info RegistrationChannel Auto agent registration SUCCEEDED! 2021-08-03 14:44:00.0257 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Registered machine/collector agent with machine ID [707] 2021-08-03 14:44:00.0257 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Starting Machine Agent .... 2021-08-03 14:44:00.0257 11408 AppDynamics.Coordinator 1 9 Info ControllerTimeSkewHandler Skew Handler is : [enabled]. 2021-08-03 14:44:00.0569 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Metrics Initialized with maxPublishQueueLength [5], aggregationFrequencyInMillis [60000] 2021-08-03 14:44:00.0569 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Metrics Metric Service is : [enabled]. 2021-08-03 14:44:00.0725 11408 AppDynamics.Coordinator 1 9 Info IISMetricManager Started IIS metric collection 2021-08-03 14:44:00.0725 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Scheduling metric polling period of 60 with cache timeout of 1 2021-08-03 14:44:00.0882 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager starts EventLog listener 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added EventLog for listening: [Application] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added EventLog for listening: [System] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = Application Error] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = .NET Runtime] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Information, Source = Windows Error Reporting] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = WAS] 2021-08-03 14:44:00.1038 11408 AppDynamics.Coordinator 1 9 Info EventLogListener starts listen EventLog: [Application] 2021-08-03 14:44:00.1194 11408 AppDynamics.Coordinator 1 9 Info EventLogListener starts listen EventLog: [System] 2021-08-03 14:44:00.1194 11408 AppDynamics.Coordinator 1 9 Info EventLogListener schedules to clean entries older than [60] sec every [60] sec 2021-08-03 14:44:00.1194 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Set up agent re-registration task 2021-08-03 14:44:00.1194 11408 AppDynamics.Coordinator 1 9 Info MachineAgentManager Started AppDynamics Machine Agent Successfully. 2021-08-03 14:44:00.7288 11408 AppDynamics.Coordinator 1 11 Info ConfigurationManager Skipping update of environment variable 'InternalAppDynamicsAgent_ProfilerProcesses', as the value is unchanged 2021-08-03 14:44:01.7913 11408 AppDynamics.Coordinator 1 6 Info CoordinatorService Starting communicator... 2021-08-03 14:44:01.7913 11408 AppDynamics.Coordinator 1 9 Info CoordinatorCommunicator starting named pipe server 2021-08-03 14:44:01.8069 11408 AppDynamics.Coordinator 1 9 Info CoordinatorCommunicator named pipe = \\.\pipe\AppDynamicsAgentIPC 2021-08-03 14:44:06.0101 10932 w3wp 4 13 Warn HttpSink Error occurred while attempting to send data to [http://localhost:9090/v2/sinks/bt] ...Then a little later... 2021-08-03 14:45:00.1355 11408 AppDynamics.Coordinator 1 10 Info MachineAgentManager Metrics URL = https://redacted:1234/controller/instance/707/metricregistration 2021-08-03 14:45:00.1355 11408 AppDynamics.Coordinator 1 10 Info MachineAgentManager Metrics Payload = <request><node-id>0</node-id><agent-type>MACHINE_AGENT</agent-type><account-key>redacted</account-key><metric time-rollup-type="AVERAGE" name="Hardware Resources|Network|Outgoing KB/sec" hole-fill-type="REGULAR_COUNTER" cluster-rollup-type="INDIVIDUAL" /><metric time-rollup-type="AVERAGE" name="Hardware Resources|Network|Incoming packets/sec" hole-fill-type="REGULAR_COUNTER" cluster-rollup-type="INDIVIDUAL" />.... But no other instance of "MachineAgent" appears after this in AgentLog.txt, and the server/node appears dead from the perspective of the controller. The "HttpSink Error" error is a new issue as of this morning and might be unrelated. How can I configure/debug to make this work? I'm wondering if the embedded .NET machine agent works at all, since there's practically no mention of it on any other AppDynamics pages. ... View more