https://docs.appdynamics.com/display/PRO42/Asynchronous+Exit+Points+for+.NET
And enabling thread correlation.
Sorry, I didn't see in the topic you put .Net, my bad ;)
JB
Thanks very much.
Why is this not enabled by default? Parfomance impact?
Hi all,
can some please let me know , if i have different customers for different location. can we install each location one controller server and all collectors send data to center controller (like manager of manager concepts )
Hi all,
We are installing a new controller in a new environment and was wondering if it was possible to transfer the following from the old controller:
Any feedback would be great, especially if you have experience with changing controllers. Any pointers, advice is very much appreciated.
Cheers.
Hi Kay,
automatic injection doesn't have the option to filter based on IP address. Using something like the load-balancer would be the best way forward.
Regards,
Mayuresh
Are you still facing the issue? I created a job with the same script and a timeout of 100 and it fails in verification:
0.00s [INFO] Starting measurement [161116_RQ_5BTS] 0.15s [INFO] Executing WebDriver script 14.90s [INFO] verifyTitle failed 14.90s [ERROR] Exception: Test failed. Traceback (most recent call last): Line 16, in <synthetic script> raise Exception("Test failed.")
What type of app agent is it? And what is the version? Also what application is the one in question?
Hello,
There's no such concept in AppDynamics and to my opinion, no need for that. The controller is highly scalable, the protocol can be HTTPS from agents to Controller and the Controller can be deployed in multi-tenant mode.
What are you trying to achieve?
If you want to manage multiple customers in different locations, maybe you should have a look at multi-tenancy:
https://docs.appdynamics.com/display/PRO42/Controller+Tenant+Mode+and+Accounts
Hope it helps
JB
This is most likely down to permission requirements in the server.policy file. See the 4.2 documentation on instrumenting Websphere jvms here: https://docs.appdynamics.com/display/PRO42/IBM+WebSphere+and+InfoSphere+Startup+Settings
Hi Raymond. Yeah we got past the problem with the server.policy amendment.
There's no rest interface to the AppDynamics downloads site as far as I can tell, you could however simply do a get as the filename can be determined:
https://aperture.appdynamics.com/download/prox/download-file/sun-jvm/4.2.7.1/AppServerAgent-4.2.7.1.zip - this is the agent for the SUN
https://aperture.appdynamics.com/download/prox/download-file/ibm-jvm/4.2.7.1/AppServerAgent-ibm-4.2.7.1.zip - this is the IBM agent
Alernatively, you could host the versions in your own internal network and simply get this by your own naming standard. You may want to deploy a later version of the agent (same major/minor version) than you are running on the controller so if you always copy/GET the latest 4.2.X version. This would require the versions/media to be maintained however.
I know you can pull transaction snatshot for an application with ..\request-snapshots?time-range-type=BEFORE_NOW&duration-in-mins=
How do you get the EUM browser snapshots?
I'm sort of still having this issue. The script failed for you because the username and password in the script I posted here are not valid.
Support has responded to my ticket and acknowledged there is a bug right now with how our site scripting operates and how the synthetic job emulates IE 10 and 11. The script works fine using Firefox or Chrome, so that's what we've done for now. I was told that a bug was created and would be resolved in a future release.
(those are the exclamations in the log, not mine)
I've installed the Controller, and I can't get it to generate an agent zip file (same error message as reported in the screenshot on this article: https://community.appdynamics.com/t5/Knowledge-Base/Error-while-retrieving-the-agent/ta-p/14891)
I've moved past that, and downloaded the agent and manually configured it. But when starting, I get the following in agent.2016_12_10__12_36_44.0.log (our server is a test system that's been put in the future for testing)
[Thread-0] 10 Dec 2016 12:36:44,294 INFO - Starting BT Logs at Sat Dec 10 12:36:44 CST 2016 [Thread-0] 10 Dec 2016 12:36:44,295 INFO - ########################################################### [Thread-0] 10 Dec 2016 12:36:44,295 INFO - Using Java Agent Version [Server Agent v4.2.9.1 GA #13591 ra9096e54aaa693777d019dc8682e23e8cc89f2b3 23-4.2.9.next-analytics] [Thread-0] 10 Dec 2016 12:36:44,295 INFO - Running IBM Java Agent [No] itscum@fxtestapp2-64:/usr/nlg/java/AppDynamicsAgent/ver4.2.9.1/logs/fxtestapp2$ cat agent.2016_12_10__12_36_44.0.log [Thread-0] 10 Dec 2016 12:36:44,295 INFO JavaAgent - #################################################################################### [Thread-0] 10 Dec 2016 12:36:44,295 INFO JavaAgent - Java Agent Directory [/usr/nlg/java/AppDynamicsAgent/ver4.2.9.1] [Thread-0] 10 Dec 2016 12:36:44,295 INFO JavaAgent - Java Agent AppAgent directory [/usr/nlg/java/AppDynamicsAgent/ver4.2.9.1] [Thread-0] 10 Dec 2016 12:36:44,295 INFO JavaAgent - Using Java Agent Version [Server Agent v4.2.9.1 GA #13591 ra9096e54aaa693777d019dc8682e23e8cc89f2b3 23-4.2.9.next-analytics] [Thread-0] 10 Dec 2016 12:36:44,295 INFO JavaAgent - All agent classes have been pre-loaded [Thread-0] 10 Dec 2016 12:36:44,296 INFO AgentKernel - Starting Java Agent at Sat Dec 10 12:36:44 CST 2016 ... [Thread-0] 10 Dec 2016 12:36:44,349 INFO XMLConfigManager - Orchestration is disabled - disabling virtualization resolvers by default. [Thread-0] 10 Dec 2016 12:36:44,373 INFO XMLConfigManager - Default Host Identifier Resolver using host name for unique host identifier [fxtestapp2-64] [Thread-0] 10 Dec 2016 12:36:44,374 INFO XMLConfigManager - Default IP Address Resolver found IP addresses [[fe80:0:0:0:250:56ff:feab:3c69%eth0, 192.168.3.77]] [Thread-0] 10 Dec 2016 12:36:44,381 INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false] [Thread-0] 10 Dec 2016 12:36:44,388 INFO XMLConfigManager - Full Agent Registration Info Resolver using selfService [false] [Thread-0] 10 Dec 2016 12:36:44,388 INFO XMLConfigManager - Full Agent Registration Info Resolver using application name [Felix] [Thread-0] 10 Dec 2016 12:36:44,388 INFO XMLConfigManager - Full Agent Registration Info Resolver using tier name [FelixApp] [Thread-0] 10 Dec 2016 12:36:44,388 INFO XMLConfigManager - Full Agent Registration Info Resolver using node name [fxtestapp2] [Thread-0] 10 Dec 2016 12:36:44,395 WARN XMLConfigManager - XML Controller Info Resolver found invalid controller host information [] in controller-info.xml; Please specify a valid value if it is not already set in system properties. [Thread-0] 10 Dec 2016 12:36:44,395 WARN XMLConfigManager - XML Controller Info Resolver found invalid controller port information [] in controller-info.xml; Please specify a valid value if it is not already set in system properties. [Thread-0] 10 Dec 2016 12:36:44,403 INFO XMLConfigManager - XML Controller Info Resolver found controller host [fxstageapp2] [Thread-0] 10 Dec 2016 12:36:44,403 INFO XMLConfigManager - XML Controller Info Resolver found controller port [8090] [Thread-0] 10 Dec 2016 12:36:44,416 INFO XMLConfigManager - XML Agent Account Info Resolver did not find account name. Using default account name [customer1] [Thread-0] 10 Dec 2016 12:36:44,416 INFO XMLConfigManager - XML Agent Account Info Resolver did not find account access key. [Thread-0] 10 Dec 2016 12:36:44,430 ERROR JavaAgent - Could Not Start Java Agent, Disabling !!!!! com.singularity.ee.agent.appagent.kernel.spi.c: Could not initialize configuration at com.singularity.ee.agent.appagent.kernel.l.start(l.java:95) at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:428) at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:242) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.singularity.ee.agent.appagent.AgentEntryPoint$1.run(AgentEntryPoint.java:481) Caused by: com.singularity.ee.agent.configuration.a: Could not resolve agent-controller basic configuration at com.singularity.ee.agent.appagent.kernel.config.xml.d.d(d.java:198) at com.singularity.ee.agent.appagent.kernel.config.xml.d.<init>(d.java:152) at com.singularity.ee.agent.appagent.kernel.config.m.a(m.java:24) at com.singularity.ee.agent.appagent.kernel.l.start(l.java:90) ... 7 more
any thoughts on how to proceed?
Missing the account name and accesskey in the controller-info.xml
Get it from the controller -> settings -> license page
Hi All,
We are using Appdynamics Realuser monitoring application in our entriprise producton environmnet, we noticed an issue in "adrum.js" failing to report Beacon frames to Appdynamics controller.
So wanted to check if there was any widespread issue from appdynamics or is it only us who got affected ??
Regards,
Sanjeev