About Dietrich_Meier

Dietrich_Meier · ‎11-12-2023

Hi Cansel Its a SaaS Controller, so cannot run those commands on the Controller. AppD Support also informed me that this is not a controller-side issue, but rather general network issue.

Dietrich_Meier · ‎10-31-2023

We recently had a short metric gaps in the controller UI (SaaS Controller) for several apps and different agents (DB, App and Machine). The log files of all the different agents all have a common theme: "Connection back off limitation in effect" "Fatal transport error while connecting to URL" also comes up sometimes as a similar error logged by agents. I did a quick search online and this seems to be an AppD agent specific log file entry. The AppD community also had about 12 entries going back to 2017, all with no clear solution to this error message. (Summary below) Docs site search returns nothing. I opened an AppD support case and will see what they say, but it is frustrating to see that this is a common thing reported by different agents without a clear cause for it documented anywhere. I wonder why something like this is logged the way it is which makes me think its something to do with a limitation on the Controller side of things, when all other community posts and agent logs make it look like it is not Controller related. Examples of our recent issue: * I tried to redact the important bits DB Agent v23.2.2 [Entity-Registration-Scheduler-19] 31 Oct 2023 10:50:25,932 WARN EntityRegistrar - Fail to register [DBSession] entities: java.lang.RuntimeException: Connection back off limitation in effect: /controller/instance/***/registerServerSatelliteEntity at com.singularity.ee.agent.dbagent.task.reporter.EntityRegistrar.registerEntities(EntityRegistrar.java:276) ~[db-agent.jar:Database Agent v23.2.0.0 GA compatible with 4.5.2.0 Build Date 2023-02-22] Other DB Agent v23.2.2 [<**DB Collector Name***>-Transient-Event-Scheduler-2] 31 Oct 2023 10:51:22,737 WARN SystemAgentTransientEventChannel - Error sending event data to controller: Connection back off limitation in effect: /controller/instance/***/transient-channel Different DB agent v23.8.8 [<**DB Collector Name***>-Scheduler-3] 31 Oct 2023 10:51:52,288 INFO ADBCollector - Collected one-minute data for *** [Entity-Registration-Scheduler-2] 31 Oct 2023 10:51:52,850 WARN EntityRegistrar - Fail to register [Query] entities: java.lang.RuntimeException: Connection back off limitation in effect: /controller/instance/3945944/registerSQLQuery SIM (Machine)Agent **ServerName**==> [AD Thread-Metric Reporter0] 31 Oct 2023 10:51:56,554 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Connection back off limitation in effect: /controller/instance/***/metrics SIM Agent v22x ***Hostname***==> [AD Thread-Metric Reporter0] 31 Oct 2023 10:51:48,204 ERROR ManagedMonitorDelegate - Fatal transport error while connecting to URL [/controller/instance/***/metrics]: org.apache.http.conn.ConnectTimeoutException: Connect to ***:443 [***/***, ***, ***] failed: connect timed out ***Hostname***==> [AD Thread-Metric Reporter0] 31 Oct 2023 10:51:48,204 WARN ManagedMonitorDelegate - Error sending metric data to controller:Fatal transport error while connecting to URL [/controller/instance/***/metrics] ***Hostname***==> [AD Thread-Metric Reporter0] 31 Oct 2023 10:51:48,204 ERROR ManagedMonitorDelegate - Error sending metrics - will requeue for later transmission com.singularity.ee.agent.commonservices.metricgeneration.metrics.MetricSendException: Fatal transport error while connecting to URL [/controller/instance/***/metrics] Summary of other AppD community posts with a similar error from agent log files: 2017 Community post https://community.appdynamics.com/t5/NET-Agent-Installation/Azure-Cloud-Service-No-load-detected-App-agent-status-0/td-p/26538 No solutions in ticket/unresolved 2017 Community post no 2 https://community.appdynamics.com/t5/Dynamic-Languages-Node-JS-Python/Could-not-connect-to-the-controller-invalid-response-from/td-p/28680 Python agent issues Mentions proxy setup for outbound requests from agent server, but no clear answer other than bringing the node online on controller, whatever that means 2017 Community post no3 https://community.appdynamics.com/t5/NET-Agent-Installation/Failed-to-add-web-app-to-AppDynamics/td-p/23699 No confirmed solution, but last posts suggests using non ssl settings which is not a great solution if that is the fix 2017 Community post no4 https://community.appdynamics.com/t5/NET-Agent-Installation/net-Agent-registering-issue/td-p/29595 Proxy setting highlighted but no ultimate solution 2018 Community post https://community.appdynamics.com/t5/NET-Agent-Installation/BT-requests-and-survival/td-p/29629 Answers do not address the "Connection back off limitation in effect" issue 2018 Community post no2 https://community.appdynamics.com/t5/NET-Agent-Installation/After-NET-Agent-upgrade-to-4-3-7-1-we-are-not-seeing-load-for/td-p/34528 Issue shown in one log file extract but not addressed 2018 Community post no3 https://community.appdynamics.com/t5/Controller-SaaS-On-Premises/Unable-to-connect-to-the-controller/td-p/30857 No final solution 2018 Community post no4 https://community.appdynamics.com/t5/NET-Agent-Installation/Need-help-on-installation-of-agent/td-p/34673 Post never had a resolution 2019 Community post https://community.appdynamics.com/t5/NET-Agent-Installation/no-metrics-in-controller-after-net-agent-installation-in-linux/td-p/37848 Possible issue with AppDynamicsConfig.json No clear answer/solution 2019 Community post no2 https://community.appdynamics.com/t5/NET-Agent-Installation/Net-core-agent-Linux-is-not-connecting-to-the-saas-controller/td-p/37867 No solution 2021 Community post https://community.appdynamics.com/t5/Knowledge-Base/How-do-I-install-the-NET-Core-Microservices-Agent-for-Windows/ta-p/33191 Answers do not address the "Connection back off limitation in effect" issue 2023 Community post https://community.appdynamics.com/t5/Controller-SaaS-On-Premises/Could-not-connect-to-the-controller-invalid-response-from/m-p/50571#M3319 Suggests ignoring or disabling the errors Here is to hoping there is a solution or better answer to this issue.

Dietrich_Meier · ‎10-23-2023

Just updating this old post with the info that we never reached the implementation part of this extension because the client went another route. So my knowledge on this is about as extensive as the above posts.

Dietrich_Meier · ‎05-11-2023

Thanks for the input

Dietrich_Meier · ‎05-11-2023

Thanks for that

Dietrich_Meier · ‎05-10-2023

Hi Is there a more comprehensive or full list of Controller APIs other than this documentation page? https://docs.appdynamics.com/appd/22.x/22.3/en/extend-appdynamics/appdynamics-apis I have come across several AppD users/extensions/tools that use AppD APIs that are not listed in the official documentation. For example, the is a configuration API to mark a node as historical, but surely there must be other commands to also execute with a node, like to delete it, but there is no documentation on it so how would a client know what the syntax is? POST /controller/rest/mark-nodes-historical?application-component-node-ids=value Hoping someone can assist. A quick search through the community posts about the APIs (Results are 800+), did not reveal anything.

Dietrich_Meier · ‎05-10-2023

Thanks for the input Arun and Atyuha. I am marking this as solved as I got the answers I needed. Just waiting for the client to come back to me before we can proceed with the actual testing. Dietrich

Dietrich_Meier · ‎05-03-2023

Hi Arun Thanks for the input. Do you know anything more about the permissions the user account requires that authenticates with vCenter?

Dietrich_Meier · ‎05-03-2023

We are looking to use the VMWare - Monitoring Extension I need some clarification if this extension uses Vcenter or if host info needs to be captured in the config file for each VM and Host managed by Vcenter? The documentation is not very clear on that or the specific permissions required for the user that does authentication. See image below for reference. What is the difference between the "host" in the servers section at the top of the config and the "host" in the hostconfig section further down. Which one do we use if our client's Vcenter is managing 200 Hosts? config.yml

Dietrich_Meier · ‎04-12-2023

Hi Sunil Thanks for the input. Its for the DB Collector setup, Controller-side. At this time we are waiting for the DBAs to finish setting up the DB and come back to us with more details, but I guess you will always require a host or IP for the AppD Collector to function. I think it would be helpful if the MS documentation on Bastion mentions that any app connecting to the VM would still require an IP. Dietrich

Dietrich_Meier · ‎04-05-2023

We are trying to monitor a SQL DB in an Azure cloud VM that is making use of Bastion. Our DB agent in on-prem on a Windows server. The Bastion documentation claims that you would not need a public facing IP for the VM. We are still trying to figure out what the Host or connection details would be then for the DB on the VM to allow the AppD DB agent to monitor the DB. Hope someone else has had some experience with this. Regards Dietrich

Dietrich_Meier · ‎04-05-2023

We encountered an issue with with the v23.2 of the .Net agent for Windows where the Agent Config tool does not detect any IIS services. On the support ticket they just asked us to reinstall the agent, but later confirmed that it was a bug and there has been a new agent version released on 4 April 2023. (356531) Just wanted to point this out to anyone possibly still using the older agent version and to make people aware that it was just a bug. Going to an older agent version also worked for us. Agent with bug Older agent that did not have issue

Dietrich_Meier · ‎03-15-2023

Hi I would also like to know how to perform this conversion if its possible in an AppDynamics Dashboard. Regards

Dietrich_Meier · ‎01-10-2023

Hi Ashish The documentation only shows an example with a .sh script. Please test your YAML script in a non-prod environment if possible and let us know how it turned out. Regards

Dietrich_Meier · ‎01-08-2023

Hi Ashish I have not come across a good working example of this for executing something in Ansible. Way back when I last tried to get this working there was a limitation for custom actions that required the host server to be Linux. Not sure if that has been changed. Check out this link. https://docs.appdynamics.com/appd/23.x/latest/en/appdynamics-essentials/alert-and-respond/actions/remediation-actions Prerequisites for Local Script Actions The Machine Agent must be installed running on the host on which the script executes. To see a list of installed Machine Agents for your application, click View machines with machine-agent installed in the bottom left corner of the remediation script configuration window. To be able to run remediation scripts, the Machine Agent must be connected to an on-premises Controller or to a SaaS Controller via SSL. Remediation script execution is disabled if the Machine Agent connects to a SaaS Controller on an unsecured (non-SSL) HTTP connection. The Machine Agent OS user must have full permissions to the script file and the log files generated by the script and/or its associated child processes. The script must be placed in <agent install directory>\local-scripts. The script must be available on the host on which it executes. Processes spawned from the scripts must be daemon processes.

Dietrich_Meier · ‎11-24-2022

Hi Thats a lot of restarts, there must be something to change that would at the very least reduce that number. Here are some of our stats in case it can help you tweak things a bit. I try to make the Xmx value slightly more than the consumption we see. (Mine is probably higher than yours might be because of the other extensions on this MA. We monitor around 130 URLs with the extension. Metrics uploaded by the Extension Thread setting in extension config file numberOfThreads: 12 Regards Dietrich

Dietrich_Meier · ‎11-23-2022

Hi Avinash We experience a similar issue at times (once or twice a week) with the v2.1 version of the extension. The v22.1 Machine Agent runs on Windows with 2 other extensions. The URL monitoring metrics would stop reporting in while the SIM and other extension's metrics continue to report in as normal. MA metrics and memory allocation also updated over time, but it is difficult to tell if that worked as a temporary fix of if a simple MA restart does the trick. One thing I picked out from the logs the previous time it happened: 03RNB-APPDDBM==> [Agent-Monitor-Scheduler-4] 07 Nov 2022 06:31:04,956 ERROR MonitorExecutorServiceModule-URL Monitor - Queue Capacity reached!! Rejecting runnable tasks.. Screenshot from one of the dashboards used to monitor the MA that hosts extensions. (Shows when the URL monitoring extension breaks) URL Metrics stop reporting in At the moment I do maintenance restarts at least once a week, and not sure about the exact cause. Regards Dietrich

Dietrich_Meier · ‎11-09-2022

Hi Here is the link to the Idea Exchange topic. https://community.appdynamics.com/t5/Idea-Exchange/Node-JS-agent-build-support-on-Mac-M1/idc-p/49330/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExBOVJWOTNaMlBQQ1hVfDQ5MzMwfFNVQlNDUklQVElPTlN8aEs#M3557 Screenshot to path: Path Regards Dietrich

Dietrich_Meier · ‎11-09-2022

Hi Nikolas We have the same issue and just want to get my post in here so that I am subscribed to this when there is a fix. There is also already an enhancement request on the Idea Exchange for this also. Hope it gets looked at soon. Just got feedback from AppD support today on this: "Unfortunately, we do not support Apple’s M chips, either ARM architectures for Node.js agents at this moment" Dietrich

Dietrich_Meier · ‎10-10-2022

Update AppD Support supplied me with with the zip file for the 3.1.4 release of the extension and it works as expected. The issue seems to be related to the 3.1.1 release available on the this page below. https://github.com/Appdynamics/file-monitoring-extension Screenshot showing the data reporting in as expected: Metrics reporting in consistently

Dietrich_Meier · ‎10-07-2022

Hi Ryan Got this link from a colleague and will try it out as a solution. https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Transaction-tracing-in-Elasticsearch/td-p/30174 The issue with the session with our consultants is that there are no slots for this week and the available ones are very late in the evenings. Regards Dietrich

Dietrich_Meier · ‎10-06-2022

Hi Harris Thanks for the input. We had a WebEx call with AppD support after my previous post and got things sorter out. Check the comments from AppD following the call. Observations and actions performed: During the call, we noticed some incompatibilities in the versions of cluster-agent and operator. Upgraded both to latest versions and noticed cluster agent deployed fine and instrumentation was happening. But we noticed 2 nodes getting created for each application, although there is only one pod deployed per application. After inspecting the application, it turned out that the customer had already applied instrumentation at the Dockerfile. The image itself is coming with instrumentation and top of that, they were enabling auto-instrumentation. We had suggested them to remove the instrumentation in either of the place.

Dietrich_Meier · ‎10-06-2022

Hi Claudia and Ryan Thanks for following up on this. The ticket #335757 still has AppD support stating that this is a bug and being followed up with the engineering team. We also have the customer success team from AppD involved and they could preproduce the error on their demo Controller. Hope that the bug gets fixed sometime with an update. Regards Dietrich

Dietrich_Meier · ‎10-06-2022

Looking to use the file-monitoring-extension found on Github. https://github.com/Appdynamics/file-monitoring-extension FileWatcher-3.1.1 Got the extension working on Windows using the Standalone Machine Agent. Metrics are registered with the Controller and after each MA restart there is only 1 data point for each metric and the all the metrics are 0's after that. Any subsequent restarts only generate 1 data point again, and while accurate there are never any other data points for the metrics. See the screenshots below showing that. There are some Warnings in the MA Log file, but do not seem to be related to the issue we are experiencing. Log and Config file added below also. Hope someone is using this successfully and can offer some input. AppD support do not assist with extensions anymore. Shows data points and how they only have data after a restart All relevant metrics are there, but have no continuous metric s reporting in Logs LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:56,642 INFO SystemAgent - Starting Machine Agent.... LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:56,642 INFO ControllerTimeSkewHandler - Skew Handler is : [enabled]. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,191 INFO SystemAgent - Full certificate chain validation performed using default certificate file LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,677 INFO ManagedMonitorDelegate - Started Agent Metric Generation Service LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO ManagedMonitorDelegate - Event Service is : [enabled]. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO ManagedMonitorDelegate - Initialized with maxPublishQueueLength [2], aggregationFrequencyInMillis [60000] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO ManagedMonitorDelegate - Metric Service is : [enabled]. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO ManagedMonitorDelegate - Started Agent Env Properties Service LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO ManagedMonitorDelegate - Scheduled Continuous Task Monitor with frequency [30000]ms LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,692 INFO MonitorConfigReader - Reading monitor config file:C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\monitors\analytics-agent\monitor.xml LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO MonitorConfigReader - os name [windows 10] version [10.0] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO NodeMonitorManager - Initializing managed monitor [analytics-agent] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO ManagedMonitorDelegate - Not initializing managed monitor [AppDynamics Analytics Agent] - Disabled in configuration file. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO MonitorConfigReader - Reading monitor config file:C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\monitors\FileWatcher\monitor.xml LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO MonitorConfigReader - os name [windows 10] version [10.0] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO NodeMonitorManager - Initializing managed monitor [FileWatcher] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO ManagedMonitorDelegate - Initializing managed monitor [FileWatcher] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO ManagedMonitorDelegate - Executing managed monitor [FileWatcher], task name [File Watcher Extension Run Task] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,708 INFO ManagedMonitorDelegate - Task [File Watcher Extension Run Task] for monitor [FileWatcher] is continuous LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO ABaseMonitor - Using File Watcher Version [v3.1.1 Build Date 2020-05-06 17:49:45] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO ContinuousTaskMonitor - Continuous Task [FileWatcher] Started LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO NodeMonitorManager - Not running legacy system-agent monitor because SIM is enabled. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO NodeMonitorManager - Not running legacy system-agent monitor because SIM is enabled. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO NodeMonitorManager - Directory [C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\monitors\unmanaged] not found, continuing. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO AgentMonitorManager - Initialized System Monitor Manager with directory [C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\monitors] LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO SystemAgent - Set up agent monitor manager LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO SystemAgent - Orchestration is disabled - disabling one-way agent transport. The agent will not be able to execute workflow tasks. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO SystemAgentConfigManager - Scheduling configuration refresh at an interval of 60 seconds LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO SystemAgentConfigManager - Configuration refresh task interval is 60 seconds LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,746 INFO SystemAgent - Configuration manager successfully configured LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,761 INFO RunbookHandler - Runbook Operation Execution is : [enabled]. LAPTOP-41O4030E==> [system-thread-0] 06 Oct 2022 10:35:57,761 INFO SystemAgent - Started AppDynamics Machine Agent Successfully. LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:57,761 INFO ABaseMonitor - Started executing File Watcher at 2022-10-06 10:35:57 CAT LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:57,761 INFO ABaseMonitor - Using File Watcher Version [v3.1.1 Build Date 2020-05-06 17:49:45] LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:57,761 INFO PathResolver-File Watcher - Install dir resolved to C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458 LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:57,846 INFO MonitorContextConfiguration-File Watcher - Loading the contextConfiguration from C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\monitors\FileWatcher\config.yml LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,178 INFO ConfigProcessor-File Watcher - Extension config properties file for replacing placeholders not provided LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,193 INFO MonitorContextConfiguration-File Watcher - The metric prefix is initialized as Custom Metrics|File Watcher LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,193 INFO MonitorContext-File Watcher - Charset is windows-1252, file encoding is Cp1252 LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,209 INFO ControllerInfoFactory-File Watcher - The install directory is resolved to C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458 LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,225 WARN ControllerInfoFactory-File Watcher - Cannot unmarshall the config file from C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458\conf\controller-info.xml javax.xml.bind.JAXBException: Error while searching for service [javax.xml.bind.JAXBContextFactory] at javax.xml.bind.ContextFinder$1.createException(ContextFinder.java:72) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at javax.xml.bind.ContextFinder$1.createException(ContextFinder.java:69) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at javax.xml.bind.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:46) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at javax.xml.bind.ContextFinder.find(ContextFinder.java:354) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:691) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:632) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] at com.appdynamics.extensions.controller.ControllerInfoFactory.fromXml(ControllerInfoFactory.java:114) [?:?] at com.appdynamics.extensions.controller.ControllerInfoFactory.getControllerInfoFromXml(ControllerInfoFactory.java:102) [?:?] at com.appdynamics.extensions.controller.ControllerInfoFactory.initialize(ControllerInfoFactory.java:59) [?:?] at com.appdynamics.extensions.conf.modules.ControllerModule.initController(ControllerModule.java:54) [?:?] at com.appdynamics.extensions.conf.MonitorContext.initialize(MonitorContext.java:85) [?:?] at com.appdynamics.extensions.conf.MonitorContextConfiguration.setConfigYml(MonitorContextConfiguration.java:80) [?:?] at com.appdynamics.extensions.ABaseMonitor$1.onFileChange(ABaseMonitor.java:132) [?:?] at com.appdynamics.extensions.conf.modules.FileWatchListenerModule.createListener(FileWatchListenerModule.java:52) [?:?] at com.appdynamics.extensions.conf.MonitorContextConfiguration.registerListener(MonitorContextConfiguration.java:146) [?:?] at com.appdynamics.extensions.ABaseMonitor.initialize(ABaseMonitor.java:122) [?:?] at com.appdynamics.extensions.ABaseMonitor.execute(ABaseMonitor.java:186) [?:?] at com.singularity.ee.agent.systemagent.components.monitormanager.managed.MonitorTaskRunner.runTask(MonitorTaskRunner.java:149) [machineagent.jar:Machine Agent v22.9.0-3458 GA compatible with 4.4.1.0 Build Date 2022-09-28 07:21:43] at com.singularity.ee.agent.systemagent.components.monitormanager.managed.ContinuousTaskRunner.run(ContinuousTaskRunner.java:50) [machineagent.jar:Machine Agent v22.9.0-3458 GA compatible with 4.4.1.0 Build Date 2022-09-28 07:21:43] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?] at java.util.concurrent.FutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?] at java.lang.Thread.run(Unknown Source) [?:?] Caused by: java.util.ServiceConfigurationError: javax.xml.bind.JAXBContextFactory: Provider com.sun.xml.bind.v2.JAXBContextFactory not found at java.util.ServiceLoader.fail(Unknown Source) ~[?:?] at java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(Unknown Source) ~[?:?] at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(Unknown Source) ~[?:?] at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(Unknown Source) ~[?:?] at java.util.ServiceLoader$2.hasNext(Unknown Source) ~[?:?] at java.util.ServiceLoader$3.hasNext(Unknown Source) ~[?:?] at javax.xml.bind.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:39) ~[jakarta.xml.bind-api-2.3.3.jar:2.3.3] ... 22 more LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,240 WARN CryptoUtils-File Watcher - The password has not been set properly. Using empty password. LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,240 INFO ControllerModule-File Watcher - Initialized ControllerInfo LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,247 ERROR ControllerInfoFactory-File Watcher - The following properties [username, password, account, controllerHost, controllerPort, controllerSslEnabled, simEnabled, applicationName, tierName, nodeName] failed to resolve. Please add them to the 'controllerInfo' section in config.yml LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,247 WARN ControllerModule-File Watcher - ControllerInfo instance is not validated and resolved.....the ControllerClient and ControllerAPIService are null LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,247 INFO HttpClientModule-File Watcher - The httpClient is not initialized since the [servers] are not present in config.yml LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,247 INFO MonitorExecutorServiceModule-File Watcher - Initializing the ThreadPool with size 20 LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,363 INFO MetricCharSequenceReplaceModule-File Watcher - MetricCharSequenceReplacer initialized successfully LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,363 INFO EventsServiceModule-File Watcher - Events Service parameters not set for monitor: File Watcher. Skipping LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,363 INFO HealthCheckModule-File Watcher - Running extension health checks LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,363 INFO PathResolver-File Watcher - Install dir resolved to C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458 LAPTOP-41O4030E==> [pool-10-thread-1] 06 Oct 2022 10:35:58,410 INFO MonitorHealthCheck-File Watcher - Running monitor health checks LAPTOP-41O4030E==> [pool-10-thread-1] 06 Oct 2022 10:35:58,410 INFO AppTierNodeCheck-File Watcher - Starting AppTierNodeCheck LAPTOP-41O4030E==> [pool-10-thread-1] 06 Oct 2022 10:35:58,410 ERROR MonitorHealthCheck-File Watcher - Exception when running com.appdynamics.extensions.checks.AppTierNodeCheck@25abf5aa java.lang.NullPointerException: null at com.appdynamics.extensions.checks.AppTierNodeCheck.check(AppTierNodeCheck.java:54) ~[?:?] at com.appdynamics.extensions.checks.MonitorHealthCheck.validate(MonitorHealthCheck.java:62) [?:?] at com.appdynamics.extensions.checks.MonitorHealthCheck.run(MonitorHealthCheck.java:90) [?:?] at com.appdynamics.extensions.executorservice.MonitorThreadPoolExecutor$TaskRunnable.run(MonitorThreadPoolExecutor.java:113) [?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?] at java.util.concurrent.FutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?] at java.lang.Thread.run(Unknown Source) [?:?] LAPTOP-41O4030E==> [pool-10-thread-1] 06 Oct 2022 10:35:58,410 INFO ExtensionPathConfigCheck-File Watcher - Starting ExtensionPathConfigCheck LAPTOP-41O4030E==> [pool-10-thread-3] 06 Oct 2022 10:35:58,410 INFO MachineAgentAvailabilityCheck-File Watcher - Starting MachineAgentAvailabilityCheck LAPTOP-41O4030E==> [pool-10-thread-2] 06 Oct 2022 10:35:58,410 INFO MetricLimitCheck-File Watcher - Starting MetricLimitCheck LAPTOP-41O4030E==> [pool-10-thread-2] 06 Oct 2022 10:35:58,410 INFO PathResolver-File Watcher - Install dir resolved to C:\AppDynamics\machineagent-bundle-64bit-windows-22.9.0.3458 LAPTOP-41O4030E==> [pool-10-thread-1] 06 Oct 2022 10:35:58,410 ERROR MonitorHealthCheck-File Watcher - Exception when running com.appdynamics.extensions.checks.ExtensionPathConfigCheck@a7efa1b com.appdynamics.extensions.util.AssertUtils$ValidationException: The ControllerAPIService is null at com.appdynamics.extensions.util.AssertUtils.assertNotNull(AssertUtils.java:31) ~[?:?] at com.appdynamics.extensions.checks.ExtensionPathConfigCheck.check(ExtensionPathConfigCheck.java:57) ~[?:?] at com.appdynamics.extensions.checks.MonitorHealthCheck.validate(MonitorHealthCheck.java:62) [?:?] at com.appdynamics.extensions.checks.MonitorHealthCheck.run(MonitorHealthCheck.java:90) [?:?] at com.appdynamics.extensions.executorservice.MonitorThreadPoolExecutor$TaskRunnable.run(MonitorThreadPoolExecutor.java:113) [?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?] at java.util.concurrent.FutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?] at java.lang.Thread.run(Unknown Source) [?:?] LAPTOP-41O4030E==> [pool-10-thread-3] 06 Oct 2022 10:35:58,410 ERROR MonitorHealthCheck-File Watcher - Exception when running com.appdynamics.extensions.checks.MachineAgentAvailabilityCheck@7df807ed com.appdynamics.extensions.util.AssertUtils$ValidationException: The ControllerAPIService is null at com.appdynamics.extensions.util.AssertUtils.assertNotNull(AssertUtils.java:31) ~[?:?] at com.appdynamics.extensions.checks.MachineAgentAvailabilityCheck.check(MachineAgentAvailabilityCheck.java:65) ~[?:?] at com.appdynamics.extensions.checks.MonitorHealthCheck$1.run(MonitorHealthCheck.java:75) [?:?] at com.appdynamics.extensions.executorservice.MonitorThreadPoolExecutor$TaskRunnable.run(MonitorThreadPoolExecutor.java:113) [?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?] at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?] at java.lang.Thread.run(Unknown Source) [?:?] LAPTOP-41O4030E==> [Worker-1] 06 Oct 2022 10:35:58,579 INFO DerivedMetricsModule-File Watcher - The DerivedMetricsCalculator is not initialized. Config: #For shared directories on windows the path should be like # path: "\\\\1.2.3.4\\abc\\def\\ProductI #Use this metric prefix when SIM is enabled. metricPrefix: "Custom Metrics|File Watcher|" # To find the <COMPONENT_ID> in your environment, please follow the screenshot https://docs.appdynamics.com/display/LATEST/Build+a+Monitoring+Extension+Using+Java #metricPrefix: "Server|Component:<Component_ID OR Component_Name>|Custom Metrics|File Watcher|" pathsToProcess: #Matching only the configured directory - displayName: "TestPath2 MA_OLD - Specific Directory" path: "C:\\\\AppDynamics\\\\OLD_machineagent-bundle-64bit-windows-21.2.0.3052\\\\logs" ignoreHiddenFiles: true excludeSubdirectoriesFromFileCount: false recursiveFileCounts: false recursiveFileSizes: true #Matching a specific file - displayName: "TestPath3 Logs- Specific File" path: "C:\\\\AppDynamics\\\\machineagent-bundle-64bit-windows-22.9.0.3458\\\\logs\\\\machine-agent.log" ignoreHiddenFiles: true excludeSubdirectoriesFromFileCount: false recursiveFileCounts: false recursiveFileSizes: true metrics: fileSize: alias: "File Size (Bytes)" multiplier: 1 delta: false aggregationType: "Average" timeRollupType: "Average" clusterRollupType: "Individual" oldestFileAge: alias: "Oldest File Age" multiplier: delta: aggregationType: timeRollupType: clusterRollupType: fileCount: alias: "File Count" multiplier: delta: aggregationType: timeRollupType: clusterRollupType: numberOfLines: alias: "Number of Lines" multiplier: delta: aggregationType: timeRollupType: clusterRollupType: lastModifiedTime: alias: "Last Modified Time" multiplier: delta: aggregationType: timeRollupType: clusterRollupType: available: alias: "Available" multiplier: delta: timeRollupType: clusterRollupType: convert: "true": 1 "false": 0 # A metric to view the count of files in a directory and all its subdirectories. #Set recursiveFileCounts to true for any configured paths to see this metric. Will only work for directories. recursiveFileCount: alias: "Recursive File Count" multiplier: delta: timeRollupType: clusterRollupType: modified: alias: "Modified" multiplier: delta: timeRollupType: clusterRollupType: convert: "true": 1 "false": 0 recursiveFileSize: #Calculates the size of a directory on disk alias: "Size on Disk (Bytes)" multiplier: delta: timeRollupType: clusterRollupType: numberOfThreads: 20 #One thread per base directory + 1 # The sections [customDashboard] and [controllerInfo] need to be enabled for uploading dashboard to the controller UI customDashboard: enabled: false dashboardName: "File Watcher Dashboard" # Update the path to the dashboard file. pathToSIMDashboard: "monitors/FileWatcher/SIMDashboard.json" pathToNormalDashboard: "monitors/FileWatcher/APMDashboard.json" periodicDashboardCheckInSeconds: 300 # If any of the following fields are not set, the values of the specific fields are set from the system properties of the corresponding fields as specified in the comments. # If the system properties are not set for the field, then the data is retrieved from machine agent configFile. Please refer to ControllerInfoFactory for more details. enableHealthChecks: true # If not set, will be retrieved from "-Dappdynamics.agent.monitors.healthchecks.enable=true". Defaults to true.

Dietrich_Meier · ‎09-26-2022

There is a bug on the Custom Dashboards page with the functionality of the "Show My Dashboards Only" check box. The option either does not display the dashboards related or errors out. In earlier versions of the Controller, enabling this option would apply a filter that would only show dashboards related to the current logged in user. We have worked with AppD support on this to point out the error and support did acknowledge this, but in the following controller upgrades the error persists. AppD Support ticket Request #335757 Created back on August the 11th. Pre-Prod Controller: AppDynamics Controller build 22.8.1-715 Prod Controller: AppDynamics Controller build 22.9.1-1134 Pre-prod: Before filter, dashboards for "dietrich" Pre-prod: After Filter Prod: Before filter, dashboards for "dietrich" Prod: After Filter

Posts	50
Solutions	3
Karma Given	17
Karma Received	24
Member Since	‎11-01-2017

Online Status	Offline
Date Last Visited	‎02-28-2025 11:09 PM

Common agent error in logs: Connection back off li...

Controller APIs full list

VMWare - Monitoring Extension

Monitor SQL DB in Azure that uses Azure Bastion

.Net agent v23.2 bug with detecting IIS services

file-monitoring-extension

Show My Dashboards Only functionality broken

Custom Dashboard displaying dashes when there is n...

AppDynamics DB Agent v22.6.0.2803 not showing Load...

.Net App Agent Metric Data Point (Metric Browser)

Re: Common agent error in logs: Connection back of...

Common agent error in logs: Connection back off li...

Re: VMWare - Monitoring Extension

Re: Controller APIs full list

Re: Controller APIs full list

Controller APIs full list

Re: VMWare - Monitoring Extension

Re: VMWare - Monitoring Extension

VMWare - Monitoring Extension

Re: Monitor SQL DB in Azure that uses Azure Bastio...

Monitor SQL DB in Azure that uses Azure Bastion

.Net agent v23.2 bug with detecting IIS services

Re: How do I convert epoch time to Normal time

Re: How do I create custom action in SaaS controll...

Re: How do I create custom action in SaaS controll...

Re: URL Monitoring Extension Crashing intermittent...

Re: URL Monitoring Extension Crashing intermittent...

Re: NodeJS: Building project with appdynamics depe...

Re: NodeJS: Building project with appdynamics depe...

Re: file-monitoring-extension

Re: file-monitoring-extension

Re: Application component node id:13222 is not ass...

Re: Show My Dashboards Only functionality broken

file-monitoring-extension

Show My Dashboards Only functionality broken