A split exit point is identified using dynamic application values. AppDynamics can evaluate runtime information associated with an exit call and use that value to divide a single exit-point definition into separately monitored backend destinations or logical exit points.
Dynamic values may be obtained from method arguments, object properties, return values, headers, or other runtime data exposed through the configured getter chain. For example, an application may use one shared client method to call several external services. Although the class and method remain constant, a dynamically supplied host name, service name, destination identifier, or URL can distinguish the actual backend being invoked. Splitting on that runtime value allows AppDynamics to display and measure each destination independently.
Static values do not change between invocations and therefore cannot meaningfully separate one exit-call destination from another. “Variable application values” is not the formal configuration term used for this feature, while Tetration values relate to a separate Cisco workload and security platform.
Relevant CAAPA Study Guide topics include Exit-Point Detection, Custom Exit Points, Split Exit Points, Dynamic Runtime Values, Getter Chains, Backend Identification, and Cross-Tier Correlation.
