Hi Venkat, We're sorry for our late reply.  From the cookie file you retrieved in the 1st step, could you try to pick up JSESSIONID and X-CSRF-TOKEN and replace the following place-holder values?  curl -i -H "X-CSRF-TOKEN:<<TOKEN FROM STEP 1>>" -H "Cookie: JSESSIONID=<<JSESSIONID from Step 1>>; X-CSRF-TOKEN:<<TOKEN FROM STEP 1>>;" -H "Content-Type: application/json" -H "Accept: application/json" --data "<<application ID you want to delete>>" http://<<hostName>>:<<port>>/controller/restui/allApplications/deleteApplication ... View more

Hi Kadu,   Thanks for posting the question on the Community.   Application deletion API exists, and this needs authorization token retrieval first, so could you try these lines of execution? Caution to pass only your target application ID in <application_ID>.   curl -s -c cookie.appd --user <username>@<customer name>:<password> -X GET "http://<url>:<port>/ controller/auth?action=login" X_CSRF_TOKEN="$(grep X-CSRF-TOKEN cookie.appd|rev|cut -d$'\t' -f1|rev)"  X_CSRF_TOKEN_HEADER=$([ -n "$X_CSRF_TOKEN" ] && echo "X-CSRF-TOKEN:$X_CSRF_TOKEN" || echo '') curl -X POST <url>:<port>/controller/ restui/allApplications/ deleteApplication -H "Content-Type: application/json;charset=UTF- 8" --data "<application_ID>" -b cookie.appd -H "$X_CSRF_TOKEN_HEADER" Please run these queries by the user who has delete permissions on your applications.   Let me know if this helped you.   Many thanks, Naoto ... View more

Hi Srinivas, Thanks for posting the question on the Community.  Could you try to remove the 'agent-runtime-dir' xml tag from the agent controller-info.xml file, and restart the agent to check the results? If it does not work, could you try to put below jvm option to see the results? -Dappdynamics.agent.runtime.dir Also, could you share your machine agent version?  Let me know if this helped you. Many thanks, Naoto ... View more

Hi Udaya, Thanks for posting the question on the Community.    You can use this official docker image repo for your use case. Please follow the steps in README.   If you have any problem further, let me know. Many thanks, Naoto ... View more

Hi Vijay, Good to know agent started correctly. Could you try to add option “-XX:-UseSplitVerifier” in your Tomcat and restart your application? If it does not work still, then could you share whole logs? Let me know if this helped you. Many thanks, Naoto ... View more

Hi Alexander, It seems that mysql connector driver version is old one, so could you replace that with the latest one by the following steps? In <DB agent directory>/lib, please back up mysql-connector-<version>.jar file Download the latest mysql-connector JAR file from MySQL official site, selecting “Platform Independent” Copy mysql-connector-<new version>.jar file to <DB agent directory>/lib. Restart DB agent Let me know if this helped you. Many thanks, Naoto ... View more

Hi Mustafa, Thanks for contacting support. You can achieve correlation in C++ by adding some codes in your application as described in this SDK link, Correlate with Other Business Transactions section.  Basically, to instrument C++ code, you need to inject small codes into your application source manually.  Therefore, adding such correlation is also manual, and is similar way to instrument your application. On the other hand, Java/.Net application instrumentation does not need source code changes, and correlation is basically automatic.  Your indicated document is for the case that cannot be done automatically. Let me know if this helped you. Many thanks, Naoto ... View more

Hi Vijay, Thanks for contacting support. It seems that you missed the node name in your agent configuration. Could you check your configuration in <agent dir>/conf/controller-info.xml, node-name tag? Let me know if this helped you. Many thanks, Naoto ... View more

Hi Alexander, Thanks for posting the question on the Community. It seems that this is caused by character set conflicts between DB collector and DB. Could you try below to solve this issue? Go to DB collector configuration by clicking “Databases”->”Configuration”->”Collectors”->double click your target DB collector. In “Custom JDBC Connection String” column, put “jdbc:mysql://<hostname>:<port>/<dbname>?characterEncoding=latin1”. Please ensure you replace with your real DB information to hostname, port, and dbname. After this executed, could you check its working, and share the log with us? Let me know if this helped you. Many thanks, Naoto ... View more

Hi Odair, It seems you are monitoring standalone Java application, so you can safely and easily test 4.4.x version. Download link for 4.4.3 version is here. If you have restriction to use 4.5.x version, then I am sorry to say that this is unresolved bug for 4.5.x agent now. I will keep the progress information updated here in that case. Let me know if this helped you. Many thanks, Naoto ... View more

Hi Ranjith, Thanks for posting the question on the Community. To delete machine agent, you also need to delete the machine associated with your agent from the servers list. You can do that by these steps: Click “Servers” tab in the top navigation bar Select server that is associated with your target machine agent Please ensure there is NO APM associated with this server Click “Delete” button After this, you can delete machine agent. Also, please ensure no application is associated with your machine agent by looking at “Application” field in your machine agent. This is documented here: https://docs.appdynamics.com/display/PRO45/Manage+Machine+Agents If you still have an error by this operation, please follow this solution as well: https://community.appdynamics.com/t5/Knowledge-Base/Delete-abandoned-machine-agent/ta-p/22547 You can do that by these steps from controller: Please make sure that machine agent is no longer running or reporting. Create a dummy application from controller UI. Associate the machine agents that you want to delete to that application. Delete the dummy app that you have created at step 1. Let me know if this helped you. Many thanks, Naoto ... View more

Hi Odair, Thanks for posting the question on the Community. We identified a similar issue on your agent version:4.5.x, so could you try below steps to use 4.4.x agent version instead? Please back up current agent directory Try 4.4.x agent version in new agent directory and restart JVM node process with new agent path. If you cannot use 4.4.x agent version for some reason, please try to add below arguments in JVM option: -Dappdynamics.agent.log4j2.disabled=true -Dlog4j.ignoreTCL=true Let me know if this helped you. Many thanks, Naoto ... View more

Hi Simon,    Thanks for posting the question on the Community.   We see BT log will have entry for any monitored transactions. Transactions will be monitored if any transactions are out of box eligible like Servlet.   If you see node in UI with JVM memory metrics but no BT entry in BT logs, it could be that load is not of type Servlet, Struts, and so on. In that case, we suggest below steps as a solution:   Please define POJO rule if you have API class and method details. This can be set in UI->”Application” tab->”Configuration” tab in bottom left->”Transaction Detection”. After that, please check if the log and UI have BT load. This step is documented here: https://docs.appdynamics.com/ display/PRO45/POJO+Entry+ Points  If you do not know BT API details, set node property find-entry-points to be true in UI and save changes. This step is documented here: https://docs.appdynamics.com/ display/PRO45/App+Agent+Node+ Properties. After that, please make transactions on JVM with agent configured, and share agent node logs folder for our review. Then, we can suggest possible entry points.    Let me know if this helped you. Many thanks, Naoto ... View more

Hi Ravi, Thanks for posting the question on the Community. Java agent installation is documented in this link: https://docs.appdynamics.com/display/PRO45/Install+the+Java+Agent As the overview of installation process, Download and unzip Java agent Edit your controller information in controller-info.xml Add -javaagent JVM option to your application startup script To check its working correctly, you can see “Started AppDynamics Java Agent Successfully” in log file of the agent. Also you can check by accessing your web application, and see transaction in controller UI. Let me know if this helped you. Many thanks, Naoto ... View more

Hi Richard, Thanks for posting the question on the Community. Could you check your agent server’s firewall outbound setting? You need to allow outbound connections for these IP range:103.28.248.0/22 for your SaaS controller. This is documented in here: https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges If it does not work, could you share your complete log directory? Many thanks, Naoto ... View more