Thanks Dorowo based on your comment after trying to fix this for hours I found the solution  1, Download agent from https://accounts.appdynamics.com/downloads  2. Run npm install /my/local/path/appdynamics-nodejs-standalone-linux-x64-v21-24.1.0.9734.tgz ... View more

1. Once an account is created will the user be able to login even if accounts.appdynamics.com is down or temporarily inaccessible? 2. is there a way to turn this off so we can transition to the new model in an orderly way instead of having the rug pulled under our feet after our last upgrade? 3. When we moved to SaaS we worked with our organisation's risk and cyber controls. We agreed to create local accounts only for specific rare cases. Now we have to redo our assessment. Why was this not communicated to us ahead of time? 4. How do we ensure only our org email are used. Right now it seems I can create any random gmail or hotmail email as users? 5. Do tools like Config Exporter, Dexter, Config Assessment tool work with the new accounts? ... View more

No Ryan I couldn't find an answer to my question in that link. Are you saying use the "title" field to name the report? ... View more

We have similar requirement too Using Python requests library directly works . This line works pageUrl="test.com/api/testing" r = requests.get(pageUrl, headers = {'x-v': '2'} ) Try the same with Selenium driver. The header doesn't get passed.  driver.header_overrides = { 'x-v': '2', } driver.get(pageUrl) So our workaround was to use the request library. However this means we don't get screenshots. This is a limitation with Selenium unfortunately. However posting it here in case someone finds a workaround. ... View more

Hi,  We had the same problem increasing the limit to 3000 helped us get past for a while.  However after a day we again had the process tabs not show any data. The host itself had 1500 processes approx. What's the purging logic?  It refers to a reset in the error message. Can we force a reset? I think increasing the limit again isn't a good idea.  server.log_2018-06-08T14-34-36:[#|2018-06-08T14:34:31.502+1000|WARNING|glassfish 4.1|com.appdynamics.SIM|_ThreadID=884;_ThreadName=http-listener-2(301);_TimeMillis=1528432471502;_LevelValue=900;|#SIM000121 The maximum number of monitored processes per machine allowed has been reached for machine 421. The limit sim.processes.count.maxPerMachine is set to 3000 processes. This limit will be reset after the next process purging or when some processes are deleted by the user. Could not create 78 processes for machine 421|#] ... View more