Unable to get Transaction Traces for defects using Webservices Calls. Transaction traces are missing for Slow Time defects.

Document ID : KB000048480
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Transaction Traces are missing for defects using a Webservices call.

Details:

CEM > Incident Management tab's Overview of the "Slow Time" defect shows 0 for "Defects with Transaction Trace" under the Introscope Transaction Trace section.

There are a number of "Slow Time" defects but none of them show any Transaction Traces. The "Transaction Trace Time Threshold" in Setup > Introscope Settings tab in APMCM UI is set to 5, but the problem persists.

All of the steps in the technical document, TEC599818 to configure Introscope Transaction Traces have been taken, but the problem persists.

Solution:

APMCM and Introscope problem resolution triage integration (transaction traces) works for non-Web Service transactions. It does not work for

Web Service transactions when APMCM is matching on XML elements in the SOAP body. When removing the XML matching criteria in the APMCM Web Service business transactions and matching only on the URL, the integration works again- APMCM is able to trigger transaction traces on the agent successfully.

APM does not support XML in the transaction tracing integration due to the high overhead inherent with parsing XML. It is not on the roadmap to support XML tracing. What is on the roadmap is generic/improved webservices/XML support consisting of generic matching of text inside the request body.

Typically, most users do XML matching in APMCM using custom http plugins. CA Technologies is making this use case a part of the core product in the future. This use case can be easily added to the transaction tracing integration since it is only doing simple text matching.

Note: Only get(query), Cookie, Request Header and some types of POST values are supported for transaction trace integration with APMCM. Nothing is supported in the body of the message.