In Application Performance Management (APM), the service that is called in an application environment is usually identified by specific properties, such as the host or port properties. However in an environment with a gateway or service proxy, the host and port actually identify a device instead of the ultimate downstream tier that handles the request.

This inaccurate identification of the backend destination causes the system to periodically change the association of the single backend with one of the potential target downstream tiers to which the gateway could route. This results in the joining of incomplete flow maps and inconsistencies between tiers that are included within Business Transaction snapshots, and the corresponding Business Transaction flow map.

The service proxy identification feature enables the system to resolve and identify the correct backend, and displays the correct component structure in the flow map. The service proxy detects these changes in the backend association and instructs the upstream Agent to identify the affected backend(s) as a service proxy.

As a result, the flow map shows a service proxy (represented by the icon ) between the upstream and downstream tiers. The service proxy is also visible in the Remote Services list.

If the upstream Agent is an older version than what is currently supported, an event is generated with the Agent Configuration Error message Automatic Service Proxy Discovery functionality has minimum agent version requirements for agents upstream of discovered proxies.

The service proxy icon is also available on these flow maps:

• Application Dashboard
• Tiers and Nodes
• Drill Down Backend Node
• Transaction Snapshot (Waterfall View)