Discussion Feed

  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

REST API calls to 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   Related Links: Using the Controller APIs 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.   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