Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

Transaction Correlation Overview

Updated 7/30/18

 

This topic describes how transaction correlation works in the Java environment. In principle, it works largely the same for .NET and the other language agents.

 

Transaction correlation enables AppDynamics to do distributed transaction tracing in modern web applications. Transaction correlation provides the ability to draw the application flow map and depict the flow of business transactions across multiple tiers and to external services.

 

Transaction correlation maintains the business transaction context across all tiers and threads as the requests are processed. Whatever the transaction does across all these tiers is counted as an activity for that business transaction.

 

Contents

 

Terminology

Originating tier/segment - Tier 1 in the diagram is where the first significant entry point is discovered, named, and instrumented. This is called the originating tier.

 

Continuing tier/segment (or downstream tier) - every other thread spawned in the same JVM or externally is considered a continuing segment or continuing tier. In the diagram, tiers 2, 3, and 4, and the JMS /Messaging Bus are continuing/downstream segments. Metrics are reported to the controller for each segment.

Business Transaction .png

 

AppD Maintains the Transaction Context

For Remote Calls (JVM->JVM and CLR->CLR)

  • AppDynamics agents decorate the protocol headers to add transaction contextual information.

For Async threads (intra-JVM and intra-CLR)

  • AppDynamics agents save transaction context against thread hand-offs to be picked up when the async segment starts.

When done the right way, this does not change application behavior. AppDynamics agents only add where there is extensibility, such as found in HTTP headers and JMS properties. Every "transaction segment" reports its own metrics. 

 

Typical Cross-JVM calls and Correlation Medium

This diagram shows how the context is maintained across tiers for various mediums.

Typical Cross JVM Calls.png

 

Correlation for HTTP

We add a header for HTTP calls, because by definition, the headers are extensible. Adding custom headers to carry transaction information is safe when:

  • you don't use any well-understood header names like "Accept-Language"
  • the contents of the header value is "HTTP-safe"

This diagram illustrates the generic structure of an HTTP request. When a client tier makes an HTTP call, the AppDynamics byte code interceptor adds a safe header that uniquely identifies this transaction. The AppDynamics byte code interceptor on the receiving Servlet (for example), reads the header and carries forward the transaction context. The controller reconstructs the flow based on the information received from each node in the flow.

HTTP Request.png

 

Correlation for JMS

We add a message property for JMS calls, because by definition, the message properties are extensible. Adding custom message properties to carry transaction information is safe when:

  • you don't overwrite any existing properties
  • you choose a unique property name
  • the value of the property is valid content

This diagram illustrates the generic structure of a JMS call.

JMS Call.png

 

Correlation Header 

The following diagram shows the contents of the AppDynamics correlation header.

 

Screen Shot 2018-06-28 at 2.52.18 PM.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

appId=5*ctrlguid=1520068834*acctguid=1f125f4c-d69d-4bbb-a66b-
bb896f3515d0*nodeid=849*ts=1524772123010*btid=2218*snapenable=true*guid=6ba9c1f8-ab55-4c00-9193-
95fbcd1b6ddd*exitguid=9|1*unresolvedexitid=144*tcop=1:611*cidfrom=57*etypeorder=HTTP*esubtype=HTTP*cidto=66

 

Custom Correlation

If the underlying framework/API is not supported by out of the box correlation by AppDynamics, then there is a provision to come up with the custom configurations by analyzing the flow of the transaction.

 

For more details, refer to:

 

Cross Application and Federated Cross Application Flow

Cross application flows show the performance impact between business applications within a Controller account. For environments that require a larger picture of business performance, federated cross application flows allow AppDynamics to correlate business transactions across business applications in different accounts that may be on different Controllers. For details, refer to:

 

Published on ‎05-06-2015.

Version history
Revision #:
15 of 15
Last update:
‎09-07-2018 01:23 PM
Updated by:
 
Labels (1)
Comments

With the new SAP agent it uses the HTTP listner to collect data from SAP but when I set it up is complains about the HTTP header

 

2018-07-13 10:59:57.570435| 2|httpclient| Not using an HTTP proxy
2018-07-13 10:59:57.570562| 2|env| Starting AppDynamics Agent libagent v4.4.4 v4.4.1.0 SHA (id: )
2018-07-13 10:59:57.570599| 2|env| Instrumenting process 20533 with working directory /opt/appdynamics/appdhttpsdk
2018-07-13 10:59:57.570609| 2|env| Running on OS: Linux (version #1 SMP Mon Feb 20 02:26:38 EST 2017), CPU architecture x86_64
2018-07-13 10:59:57.570621| 2|env| Controller: Telkom@41.148.130.135:8080, ssl: 0
2018-07-13 10:59:57.570632| 2|env| Analytics processor: localhost:9090
2018-07-13 10:59:57.570852| 2|agent| Agent state reset
2018-07-13 10:59:57.570896| 2|env| Application name: SAP_BW
2018-07-13 10:59:57.570929| 2|env| Tier name: BW
2018-07-13 10:59:57.570939| 2|env| Node name: SAP_BW_bisit_BW5_02
2018-07-13 10:59:57.612085| 2|agent| Scheduling new config update request
2018-07-13 10:59:57.705277| 3|httpclient| Invalid header in Http response
2018-07-13 10:59:57.705351| 3|agent| Agent configuration update error {http status 401}

 

How can one fix this?