Discussion Feed

Suppose your application is throwing an exception that contains some confidential or secret data exposed in the exception message and you don't want to display that information on the Controller.   You could add a block like below in <AgentHomeDir>/ver.x.x.x/conf/app-agent-config.xml   <sensitive-message-filters> <sensitive-message-filter message-type="throwable" match-type="CONTAINS" match-pattern="<Exception Message Static Text>" redaction-regex="<Regular Expression>"/> </sensitive-message-filters>   Example Suppose there is an exception thrown like the one below: com.TestException("AccountNumber1111111111")   If you don't want to expose the actual account number on the Controller, use below block:   <sensitive-message-filters> <sensitive-message-filter message-type="throwable" match-type="CONTAINS" match-pattern="AccountNumber" redaction-regex="[0-9]+"/> </sensitive-message-filters>   Agent restart is required for the changes to take effect. After the changes and restart, this is what it should look like on the Controller:    Attached a sample app-agent-config.xml ... View more

Microservices are available for AppDynamics version 4.3+ Controller and Agents. For more information, see AppDynamics and microservices.   To allocate purchased licenses for microservices, create a new license rule.   Licenses screen   1. Create a new license rule for all 250 Any Language Micro Services licenses: Enter 250 of 280 licenses for microservices     2. Select default options for Application and Server scope and save the rule.       3. Copy the access key corresponding to microservices, and use it as an access key for the agent. ... View more

To change the Controller from default port 8090 to an open HTTP port, make the following changes to file  <controller>\appserver\glassfish\domains\domain1\config\domain.xml .   1. Search for the following:   <network-listener port="8090" protocol="http-listener-1" enabled="true" transport=" tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>   2. Edit the file:   <network-listener port="<new-port>" protocol="http-listener-1" enabled="false" transport=" tcp" name="http-listener-1" thread-pool="http-thread-pool"></network-listener>   3. Add the new port details in place of <new-port>.   4. Restart the Controller app server:   To achieve this run the following commands: If Windows: <Controller_Home>/bin/controller.bat stop-appserver <Controller_Home>/bin/controller.bat start-appserver If Linux: <Controller_Home>/bin/controller.sh stop-appserver <Controller_Home>/bin/controller.sh start-appserver   5. After restarting the app server, access the Controller using the new port in the URL.   Example: http://hostname:port/controller ... View more

Table of Contents Issue Scenario 1 Scenario 2 Solution   Issue Specific Business Transactions (BTs) are registered in both the main BT list and all other traffic under the same tier. This happens for two reasons: Scenario 1 Scenario 2   Scenario 1 There are multiple nodes under a tier. BT - X is registered under node-1 of a tier. You have selected "Enable Business Transaction lock down" in the following screenshot. This is selected by choosing Configuration > Instrumentation > Select App.      After performing the aforementioned actions, the transactions that are already selected are frozen, and any BTs attempting to register will be moved to "All other traffic." Suppose the same transaction BT - X is trying to register from node-2 of same tier. Though there is the same BT from another node of the same tier, this would be pushed into "All other traffic." The BT will appear in both places (BT list and All other traffic). Conclusion/Solution: If you still want to register the same BT from second node again, disable the lock down on the BT. Ref doc: https://docs.appdynamics.com/display/LATEST/Organize+Business+Transactions#OrganizeBusinessTransactions-LockDownBusinessTransactions   Scenario 2 Similar to the aforementioned example, there are multiple nodes under a tier. BT - X is registered under node-1 of the tier. node-2 has similar jvm instance and it hasn't detected the same BT yet. node-2 has met the BT limit, which is in excess of 50. After the limit has been reached, the BT - X attempts to register from node-2. BT - X would be moved into "All other traffic", which results the same BT appearing in both the BT list and All other traffic. BT - X of node-1 is showing in BT list and BT - X of node-2 will display in "All other traffic".   Solution Figure out the node from which the BT is appearing in "All other traffic," as we aren't sure it is from node-2. Open transaction snapshots of all other traffic and figure out in which node BT - X is registered. Exclude some business transactions from the aforementioned node. On "All other traffic" select BT - X, then click Register so that it appears in the main BT list. ... View more