cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
pclark
AppDynamics Team (Retired)

This flowchart describes the steps to confirm BT instrumentation when you are using a web framework. For a complete description of the BT Life Cycle, see: Business Transaction Discovery Life Cycle.

 

bt-discovery-web-tkb.png

 

Supported Framework?

First check our lists of supported environments to see if your framework is one that is discovered automatically by your agent: App Server Agents Supported Environments

 

1. Review the BCT Log

Retrieve the Bytecode Transformer Log and look for entry point interceptors starting with entry.<your_framework> - for example, "entry.servlet" or "entry.struts". See Agent Log Files for details on requesting the agent logs.

 

2. Look for Entry Point Exceptions

If you find evidence in the BCT log that the entry point was instrumented, look in the agent logs for entry point exceptions. See Request Agent Log Files for details on requesting agent logs. 


If you find exceptions for your entry point, contact AppDynamics support for additional assistance. 

 

If you do not see exceptions, review this article Business Transaction Discovery Life Cycle and use the steps at Phase 2 to verify registration with the controller.

 

3. Run Find Entry Points

Use the procedure here Find Entry Points

 

4 Configure POJO or POCO Custom Match Rule

For details see POJO Entry Points or POCO Entry Points.

 

5. Contact AppDynamics Support

http://www.appdynamics.com/support/

 

6. Verifying BT Registration

If your entry point was instrumented and there were no related entry point exceptions, you can move to phase 2 - BT registration: Business Transaction Discovery Life Cycle.

Version history
Last update:
‎11-19-2018 07:55 AM
Updated by:
Join Us On December 10
Learn how Splunk and AppDynamics are redefining observability


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here
Contributors