Troubleshooting Introscope Agent Recording Issues

Document ID : KB000091828
Last Modified Date : 17/04/2018
Show Technical Document Details
Introduction:
This Knowledge Document supplements the official documentation on Agent Recording Troubleshooting. It may be helpful after enabling Introscope Agent Recording, and recording some Business Transactions.

Some  possible issues may be 
- Why a Business Transaction you recorded does not appears under agent Business Segment node.
- Why a business transaction is not matching the incoming traffic received by the agent.
Background:
Note that for Introscope Agent Recording and monitoring, a TIM server is not required.
Environment:
Introscope Agent 9.x, 10.x
Instructions:
The first thing to do is to confirm the procedure to enable Introscope Agent Recording is followed correctly.
Then, to track the entire process, it is recommended to enable trace in DEBUG on the Agent.

Once you enabled Introscope Agent Recording, recorded a Business Transaction, and promoted it to a Business Service, then you need to make sure to Synchronized monitors.
You do this from CEM UI->Setup->Monitors

The synchronization sends the Business Transaction definitions to the Agents. you can set up an Agent Filter, in case you want to restrict the agents will monitor Business Transactions.
https://docops.ca.com/ca-apm/10-7/en/administrating/cem-configuration/transaction-definition/introscope-agent-recording/setting-up-an-agent-filter

Once the Agent receives the Business Transactions to monitor, the procedure to monitor that follow up the agent is the next step:

1. On every URL accessed on the agent, the agent will try to match the traffic to a pattern rule of Business Transaction. The next message in logs indicates the agent will try to match the URL accessed.

Attempting to match Business Parameter Set to a Business Pattern Rule Set.

2. Just after the above line, you will see the traffic seen by the agent, and that it will try to match with the pattern rules it receives from the Collector

HttpParameterName=Path HttpParameterType=PATH HttpParameterValue=/BillViewer/DeployBill.do 

In the above line, the URL the agent is seeing is what appears as HttpParameterValue 

3. Then it will try to match to the current pattern rules it received from the Collector. For instance, the next message indicates it did not find a match for one of the rules 

Business Pattern Rule Set Contains the Following Parameters: Pattern Name = Path,Pattern Value = /MyBox/boxes,Pattern Type =PATH,Pattern NameType Operation = LITERAL_NAME_OPERATION,Pattern Action Operation = SIMPLE_MATCH_VALUE_OPERATION,Pattern Case Sensitive Name = false,Pattern Case Sensitive Value = false 
Business Parameter Set did not find a match 

Clearly Pattern Value = /MyBox/boxes do not match with the traffic the agent is seeing HttpParameterValue=/BillViewer/DeployBill.do 
And next indicates it found a match 

Business Pattern Rule Set Contains the Following Parameters: Pattern Name = Path,Pattern Value = /BillViewer/DeployBill.do,Pattern Type =PATH,Pattern NameType Operation = LITERAL_NAME_OPERATION,Pattern Action Operation = SIMPLE_MATCH_VALUE_OPERATION,Pattern Case Sensitive Name = false,Pattern Case Sensitive Value = true 
Business Parameter Set found a match to a Business Pattern Rule Set 

in this case, Pattern Value = /BillViewer/DeployBill.do matches HttpParameterValue=/BillViewer/DeployBill.do 
-
In the above example, properties, like the following are defined at Business Transactions components
Pattern Action Operation = SIMPLE_MATCH_VALUE_OPERATION

Other like the following are set at the Business Application definition.
Pattern Case Sensitive Value = true

If in the agent logs, the pattern rule does not attempt to match, after the agent detect any URL is accessed, it could means the collector has not sent the Business Transaction rules to the agent.
Reviewing the Collector logs may be needed to understand why.

 
Additional Information:
Known Problem
https://comm.support.ca.com/kb/after-successful-agent-recording-of-application-the-agent-business-segment-node-does-not-appear-in-the-investigator-during-monitoring/kb000005731

Documentation
https://docops.ca.com/ca-apm/10-7/en/administrating/cem-configuration/transaction-definition/introscope-agent-recording

Enabling TRACE on DEBUG
https://comm.support.ca.com/kb/apm-logs-and-how-to-enable-debug/kb000033600