Discussion Feed

Edson.Emidio · ‎07-27-2018

My issue was solved after bring node online on controller

Edson.Emidio · ‎05-15-2018

Hi, everybody! Did you solve the issue? I am facing the same error in one of ours servers: 2018-05-15 08:46:26.9604 5600 AppDynamics.Coordinator 1 11 Info CoordinatorService Stopped Machine Agent. 2018-05-15 08:46:28.3175 5600 AppDynamics.Coordinator 1 8 Info CoordinatorService Starting communicator... 2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator starting named pipe server 2018-05-15 08:46:28.3335 5600 AppDynamics.Coordinator 1 7 Info CoordinatorCommunicator named pipe = \\.\pipe\AppDynamicsAgentIPC 2018-05-15 08:51:26.0453 5600 AppDynamics.Coordinator 1 17 Info ControllerTimeSkewHandler Controller Time Skew Handler Run Aborted - Skew Check is Disabled

Edson.Emidio · ‎03-28-2018

Hi, We use AppDynamics (SAAS) since 2013 and we have a very complex environment - about 80.000 call/min, 715 tiers, 1837 nodes. Basically, we reached all metric limits, and, due to it, we are looking for an architecture that allow us to be more scalable and at the same time be able to perform troubleshooting and analysis routine without losing visibility. I created a form where I ask some information that will help us answer those questions: Please, answer if you can. The link is shown below. [REMOVED LINK] Thanks a lot Edson [Email Redacted] ^ Edited by @Ryan.Paredez to redact email address. Please do not share email addresses in community posts for security and privacy reasons.

Date Registered	‎05-23-2016 07:30 AM
Date Last Visited	‎12-15-2018 02:21 AM
Total Messages Posted	3
Total Kudos Received	1

Discussion Feed

Re: Could not connect to the controller/invalid re...

Re: Unable to connect to the controller

AppDynamics Architecture - best practices