This FAQ section gathers questions and answers about configuring AppDynamics Lite, edge-case scenarios, and more.

Unless specified, all information applies to both .NET and Java products.

If you want to discuss an issue or have a question that is not answered here, visit our community.

General FAQs

Why are there no Business Transactions in the Viewer?

If the Viewer does not show any Business Transactions, there may be a configuration problem.

Verify that the Agent is enabled.

The AppDynamics Lite Agent must be enabled in order for it to report data to the Viewer. Verify that the Agent is enabled by looking at the Agent options at the top of the dashboard page in the Viewer. The Monitoring status should be ON.

Note: When you enable an Agent, it takes a few minutes for the Agent to start sending data to the Viewer.

Verify that you have load running on your application server.

Business Transactions cannot be detected by the Agent unless there is load running through your instrumented application server. Ensure that load is running by triggering requests manually in the application or by using an automated load test.

Verify that monitoring is properly configured for the supported entry points used by the application.

If you are not seeing transactions, use the "Transaction Detection" tab on the configuration screen of the Viewer to determine whether the entry points are supported. See:

• Supported Applications and Frameworks for .NET
• Supported Applications and Frameworks for Java

Verify that you have monitoring and automatic transaction detection turned ON for the entry points that your application uses.

If your application uses POJO, verify that you have configured custom POJO transaction matching rules (ie: on an OSGI container).

Verify that there are no errors or exceptions in the Agent logs.

Check the Agent logs for any exceptions or errors. Visit the community for more help.

Verify that the Business Transaction limit is not violated.

AppDynamics Lite keeps a maximum of 30 business transactions at a time. If you see some Business Transactions but not the ones you expect, you might need to exclude some existing ones before you can see additional ones. Exclude existing transactions by right-clicking on a transaction in the Business Transaction dashboard tab in the Viewer. See Organizing User Requests Into Business Transactions.

Upgrade to AppDynamics Pro if you want to see more than 30 Business Transactions at a time.

How do I change the default thresholds that indicate poor performance or problems?

AppDynamics Lite include default settings for performance thresholds that signify whether a transaction is slow, very slow, or stalled. These default thresholds may need to be changed to better monitor a specific application.

The Agent reports a maximum of 40 problem requests per minute to the Viewer.

Slow Requests

Set the thresholds for slow and very slow requests in the Request Thresholds tab in the Configuration screen of the Viewer. Specify a request as slow/very slow using the following options:

• Static threshold: when the request's duration exceeds a specific value.
  • The default slow threshold is 2000ms.
  • The default very slow threshold is 5000ms.
• Percent slower than average: when the request's average duration exceeds an average over a time range by a specific percentage.
• Greater than N standard deviations: when the request's duration is greater than a specific number of standard deviations within a time range.

Stalled Requests

Set the thresholds for stalled requests in the Error and Stall Detection tab in the Configuration screen of the Viewer.
Mark stalled requests by using either:

• Static threshold: set a static value for marking a request as stalled.
  • The default "stalled" threshold is 45000ms.
• Greater than N standard deviations: when its duration is greater than the number of standard deviations you define within a time range you define.

Errors

Set the thresholds for requests that have errors in the Error and Stall Detection tab in the Configuration screen of the Viewer. AppDynamics Lite supports all of the common methods for identifying errors in an application. Make sure you set the error configuration in the Viewer to identify the errors relevant to your application such as logging exceptions, response code settings, etc.

How do I change the default logging location?

If you start the Viewer from outside the LiteViewer directory, AppDynamics creates the /Logs directory in the path where you start the Viewer. To change the logging path to create logs in a different location, configure the following setting in log4j.xml:

Set the value= to the path where you want create the Lite logs.

What is the error "Detected duplicate HTTP-based FlexSessions"?

When multiple Lite Viewers are running in the same browser on different tabs, a Viewer may experience an intermittent Flex error:
"[FaultEvent fault=[RPC Fault faultString="Detected duplicate HTTP-based FlexSessions, generally due to the remote host disabling session cookies. Session cookies must be enabled to manage the client connection correctly."

To avoid this situation, use separate browsers for each instance of Lite Viewer.

Java FAQs

Why is the Java Agent not reporting to the Viewer?

Use following instructions to troubleshoot agent connectivity problems.

Ensure that your application server start script has been modified to include the -javaagent argument.

• Go to your application start script and verify that the -javaagent argument exists (-javaagent:/user1/local/liteagent/javaagent.jar). 
• Next, verify that the Agent started up successfully by checking the agent.log file in the agent's "logs" directory (ie: <agent path>/logs).

Verify that the Agent connects to the Viewer on the correct port.

• If you changed the default port (port 8990) during Viewer installation using the -Dadlite.port runtime option, make sure that the same port is set in the Agent runtime options on the application server. For details, see Java Configuration Properties.

Make sure you started/restarted the application server after you started AppDynamics Lite.

If you started the Viewer after you started the application server, you must restart the application server or wait for a few minutes for the Agent to attempt to reconnect. The Agent attempts to connect to the Viewer once every minute.