To bulk delete custom dashboards using a REST API, begin by fetching the  JESSIONID and X-CSRF-TOKEN  for the user with login access to the Controller UI: curl -i --user <<userName>>@<<accountName>> https://demo.saas.appdynamics.com/auth?action=login Next, execute the following CURL call with the JESSIONID and X-CSRF-TOKEN from the previous step. This will delete the dashboards. curl -X POST -H "Cookie:JSESSIONID=<<jsessionId>>;" -H "X-CSRF-TOKEN:<<tokenValue>>" -H "Content-Type: application/json" -H "Accept: application/json" https://demo.saas.appdynamics.com/controller/restui/dashboards/deleteDashboards -d [1,2,3,...<<dashbaordIds>>] ... View more

Older Controllers (prior to version 4.2.15) follow these instructions:  Modify the following element located in the controller_home>/appserver/glassfish/domains/domain1/config/domain.xml file:   <jvm-options>-Dappdynamics.controller.ui.deeplink.url=<<new_deeplink_url>></jvm-options> Restart the Controller App Server. This will change the deeplink URL for all accounts in the Controller. Newer Controllers (versions 4.2.15+) follow these instructions:  As of Controller version 4.2.15, there is an option to change the deeplink URL for each account and runtime.  Use the following command: curl -k --basic --user root@system --header "Content-Type: application/json" --data '{ "controllerURL": "http://<controller>:<port>" }' http://<controller>:<port>/controller/rest/accounts/<ACCOUNT-NAME>/update-controller-url Verify the change by querying the Controller database:  select id, name, controller_url from account where name like '%<ACCOUNT-NAME>%'; ... View more

How do I enable or disable Health Rules and policies using an API? Is there a way to delete Health Rules? In this article... HR Disable API HR Enable API Policy Disable API Policy Enable API How do I delete Health Rules? Related Links APIs for enabling and disabling Health Rules and policies The following REST API calls enable or disable Health Rules (HR) and policies HR Disable Request type: DELETE URL: http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/healthrules/<healthrule-id>/enabled Response status: 204 No Content  HR Enable Request type: PUT URL: http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/healthrules/<healthrule-id>/enabled Response status: 204 No Content Policy Disable Request type: DELETE URL: http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/policies/<policy-id>/enabled Response status: 204 No Content Policy Enable Request type: PUT URL: http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/policies/<policy-id>/enabled Response status: 204 No Content Retrieve HRs and Policies Request Type: GET URLs: http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/healthrules http://<controller-host>:<port>/controller/api/accounts/<account-id>/applications/<application-id>/policies Response status: 200 Ok How do I delete a Health Rule?  You use this cURL command to delete Health Rules: Get the JESSIONID and X-CSRF-TOKEN for the user having login access to controller UI: curl -i --user admin@customer1:admin http://localhost:8090/controller/auth?action=login​ HTTP/1.1 200 OK cache-control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Set-Cookie: JSESSIONID=8edd9e48f2ec26cbeeb6f24126b5; Path=/controller; HttpOnly Set-Cookie: X-CSRF-TOKEN=46f1d4590d4955d55a1428e53b8d495fd57bdcd7 Date: Fri, 28 Jul 2017 11:21:15 GMT Content-Length: 0 Run the following CURL call with JESSIONID and X-CSRF-TOKEN from step 1, replacing Controller host, port and credentials, and Health_rule_ids as required. curl -X POST -H "Cookie:JSESSIONID=8edd9e48f2ec26cbeeb6f24126b5;" -H "X-CSRF-TOKEN:46f1d4590d4955d55a1428e53b8d495fd57bdcd7" -H "Content-Type: application/json" -H "Accept: application/json" http://osxltnredd.local:8090/controller/restui/health_rules/delete -d [Health_rule_ids]​ Related Links You may find the following Documentation links useful: Health Rule APIs, Update a Health Rule Configuration Using the Controller APIs Health Rule Management Health Rules ... View more

Beginning with AppDynamics version 4.3.x, a user can enable and disable Collectors that they have created. Newly created Collectors are enabled by default. Users who want to discontinue monitoring a database without deleting the Collector profile can disable the Collector from the Controller UI. Example: ... View more

Question: How do I disable SAML, or use local login when SAML is enabled? Answer: When SAML is enabled, a user can login using "local login" with or without disabling SAML. Use the hyperlink "Use Local Login" shown on the login screen below. Use Local Login ... View more

  To find the Controller account ID using the REST API, use one of the following URLs to create a GET request. SaaS: https://<<accountName>>.saas.appdynamics.com/controller/api/accounts/myaccount On-Premise: http[s]://<<hostname>>/controller/api/accounts/myaccount Find more information about using the Controller API and authentication in the documentation. ... View more

Symptoms Issue:  Time range not supported error Diagnosis Log in into the controller database and verify the following properties: <Controller_Install_Dir>\bin\controller[.sh/.bat] login-db select name, value from global_configuration_cluster where name in ('disable.historic.transactional.flow', 'caches.retention.period'); You might see an output like the following: +-------------------------------------+-------+ | name | value | +-------------------------------------+-------+ | caches.retention.period | 24 | | disable.historic.transactional.flow | true | +-------------------------------------+-------+ 2 rows in set (0.00 sec) Solution If the disable.historic.transactional.flow is set to true, then the controller will display a maximum of up to 24 hours, defined by caches.retention.period. To modify this setting, log in to the controller admin console, and mark the disable.historic.transactional.flow value as false. For details about logging in, see: https://docs.appdynamics.com/display/PRO41/Access+the+Administration+Console To confirm this change, log out of the controller, then log in to the controller and check the behavior. ... View more