Missing Hosts in Tiers & Nodes

Sundarapandian_ — Wed, 27 Sep 2017 23:12:53 GMT

Hello,

we couldn't see a couple of nodes under a specific tier (can see only 2 nodes out of 4). I can see config.xml is updated on these 2 missing hosts. This is a .NET App

Tried to restart appdynamics agent service followed by app pool recyle, which didnt help.

When look in to the agent log , i see ....."Error MachineAgentManager Metrics Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart.Exception: com.appdynamics.ee.agent.commonservices.metricgeneration.metrics.spi.qe: Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart"

Log excerpt :

"2017-09-27 15:57:58.2744 163472 AppDynamics.Coordinator 1 6 Info Configuration creating new coordinator configuration instance
2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager ####################################################################################
2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Machine Agent started
2017-09-27 15:57:58.2994 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Machine Agent version: 4.2.15.10
2017-09-27 15:57:58.4064 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Started Agent Scheduler
2017-09-27 15:57:58.4064 163472 AppDynamics.Coordinator 1 6 Info MachineAgentManager Scheduling Machine Agent Registration ....
2017-09-27 15:57:58.4174 163472 AppDynamics.Coordinator 1 6 Info RegistrationChannel Reregistration Check is : [enabled].
2017-09-27 15:57:58.4254 163472 AppDynamics.Coordinator 1 6 Info CoordinatorService coordinator service initialized successfully
2017-09-27 15:57:58.4254 163472 AppDynamics.Coordinator 1 6 Info CoordinatorService Starting communicator...
2017-09-27 15:57:58.4474 163472 AppDynamics.Coordinator 1 17 Info CoordinatorCommunicator starting named pipe server
2017-09-27 15:57:58.4564 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel using controller host [wm-appdynamics-qa-ctrl02]; controller port [8090]
2017-09-27 15:57:58.5154 163472 AppDynamics.Coordinator 1 31 Info LogFilePreparer zipping up agent logs to file: C:\Windows\TEMP\AppDynamicsLogs1777a634-e7da-4019-be1c-7b8c34b44170.zip
2017-09-27 15:57:58.5154 163472 AppDynamics.Coordinator 1 32 Info LogFilePreparer zipping up agent logs to file: C:\Windows\TEMP\AppDynamicsLogs8a1ee9b5-53ca-4bbc-b90a-f31cd4835a67.zip
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting unique host information Host Name [DDWAS6162]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent version [4.2.15.10]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent properties []
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent install dir [C:\Program Files\AppDynamics\AppDynamics .NET Agent\\]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent type [MACHINE_AGENT]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent application(s) [EBCOther-QAPE, EBCReferenceData-QAPE, EBCClientFinancials-QAPE, EBC-CapitalMarketServices-QAPE, EBCClientDemographics-QAPE, EBC-Fainfo-QAPE, EBCAppInfrastructure-QAPE, EBCClientReportingServicing-QAPE, DIP-QAPE]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent tier name [Machine Agent]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel setting agent node name [DDWAS6162]
2017-09-27 15:57:59.6896 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Sending Registration request
2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Auto agent registration attempted: Application Name [EBCOther-QAPE,EBCReferenceData-QAPE,EBCClientFinancials-QAPE,EBC-CapitalMarketServices-QAPE,EBCClientDemographics-QAPE,EBC-Fainfo-QAPE,EBCAppInfrastructure-QAPE,EBCClientReportingServicing-QAPE,DIP-QAPE] Component Name [Machine Agent] Node Name [DDWAS6162]
2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info RegistrationChannel Auto agent registration SUCCEEDED!
2017-09-27 15:57:59.7726 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Registered machine/collector agent with machine ID [809]
2017-09-27 15:57:59.7816 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Starting Machine Agent ....
2017-09-27 15:57:59.7816 163472 AppDynamics.Coordinator 1 24 Info ControllerTimeSkewHandler Skew Handler is : [enabled].
2017-09-27 15:57:59.8626 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Metrics Metric Service is : [enabled].
2017-09-27 15:57:59.9006 163472 AppDynamics.Coordinator 1 24 Info IISMetricManager Started IIS metric collection
2017-09-27 15:57:59.9006 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager Scheduling metric polling period of 60 with cache timeout of 1
2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info MachineAgentManager starts EventLog listener
2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added EventLog for listening: [Application]
2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added EventLog for listening: [System]
2017-09-27 15:57:59.9226 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = Application Error]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = .NET Runtime]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Information, Source = Windows Error Reporting]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener added a new rule for monitoring .NET crash events: [Level = Warning, Source = WAS]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener starts listen EventLog: [Application]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener starts listen EventLog: [System]
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info EventLogListener schedules to clean entries older than [60] sec every [60] sec
2017-09-27 15:57:59.9366 163472 AppDynamics.Coordinator 1 24 Info ProcessMonitor starts process monitoring for all running and future IIS processes and running executables (standalones and windows services) instrumented by the Agent
2017-09-27 15:58:01.3007 163472 AppDynamics.Coordinator 1 36 Error MachineAgentManager Metrics Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart.Exception: com.appdynamics.ee.agent.commonservices.metricgeneration.metrics.spi.qe: Maximum metrics limit reached [200] no new metrics can be created. This exception will not repeat until restart."

DDWAS6162 in the log is one of the hosts that is missing

Do we need to increase the max number metrics & how? Please advise if there could be any other reason

Thanks!

Sundar

Re: Missing Hosts in Tiers & Nodes

Raunak_Mohanty — Fri, 29 Sep 2017 10:42:57 GMT

Hi Sundar,

Let's continue to work on this on support case #110226.

Thanks,

Raunak

Re: Missing Hosts in Tiers & Nodes

CommunityUser — Wed, 14 Feb 2018 15:46:42 GMT

Hi,

This is the similar case with me also, would like to know how to check which person has moved / deleted the Host in Tiers & Nodes,

Is there any log / events generated when someone is working on the Controller, If Yes then need to know how to get the logs for the same.

Regards

Stevon Gomez

312 696 6065

Re: Missing Hosts in Tiers & Nodes

Shraddha_Nair — Thu, 03 Jan 2019 05:07:33 GMT

I believe that whenever someone is loggin into the controller, an automatic recording session starts, in case on on-premise. I am not sure about the SaaS part. So you can compare the recorded sessions and cross check who had signed in as admin during the sessions which showed deleted tiers/nodes.

I hope this helped. I am open to any other alternative suggestions that might be a better way to solve this.

topic Re: Missing Hosts in Tiers & Nodes in Splunk AppDynamics

Missing Hosts in Tiers & Nodes

Re: Missing Hosts in Tiers & Nodes

Re: Missing Hosts in Tiers & Nodes

Re: Missing Hosts in Tiers & Nodes