Page tree

This topic provides information about how to resolve synthetic transaction results that are not displayed in the Real User Analyzer.

Cannot see parameters and some data for the synthetic URI

Issue

Some data cannot be displayed because the synthetic parameters are not available in the Real User Analyzer.

Probable cause

The configuration of the confidentiality policy in the Real User Collector is not configured to collect the parameters for synthetic data.

Resolution

Configuring a confidentiality policy for synthetic transactions

 

Partial data or no data is displayed in the Real User Analyzer

Issue

Partial data or no data is displayed in the Real User Analyzer. On the TEA Agents page under the Synthetic tab, the Rejected Transactions column shows many rejected transactions.

Probable cause

The computer with the BMC Synthetic Transaction Execution Adapter (TEA) Agent installation is not synchronized with the Real User Collector computer, resulting in data that is dropped because it is detected as in the future or as old data.

Resolution

Synchronize the BMC Real End User Experience Monitoring Analyzer and Collector, and all TEA Agents, with the same Network Time Protocol (NTP) server.

 

No data is displayed in the Real User Analyzer or Real User Collector

Issue

No data is displayed in the Real User Analyzer or Real User Collector.

Probable cause

The TEA Agent cannot connect to the Real User Collector.

Resolution

Check the logs for the TEA Agent. The following message in the TEA Agent log file indicates that the Real User Collector connection credentials are invalid:

ERROR [RESULTS_QUEUE] Unable to send results , got status code=500

To change the Real User Collector credentials that the TEA Agent uses to connect, update the TEA Agent and enter valid credentials.

 

Partial data or no data is displayed after TEA Agent starts or restarts

Issue

After the BMC Synthetic Transaction Execution Adapter (TEA) Agent starts or restarts, synthetic transaction data is not displayed in the Real User Analyzer or Real User Collector. On the TEA Agents page under the Synthetic tab, the Rejected Transactions column shows many rejected transactions.

Probable cause

All at once, several Execution Plans execute scripts on the TEA Agent, which causes a spike in the TEA Agent computer's memory and CPU usage. Results are sent to the Real User Collector late, and therefore, they are rejected.

Resolution

To spread out the start of Execution Plans, adjust the random delay period. The longer the delay period, the more the Execution Plan start times are spread out.

Ensure that the delay period is less than the Execution Plan run frequency.

To adjust the random delay period
  1. On the TEA Agent computer, open the agent_config.xml file, located in the C:\Program Files (x86)\BMC Software\BMCTEAAgent\WorkingFolder\Conf directory.
  2. Locate the <MaxDelayOnStart> element and adjust the value:

    <!--Max execution delay (in sec) on EP start: minimum is 1; maximum is 900-->
    <MaxDelayOnStart>60</MaxDelayOnStart>

    The value represents the amount of time (between 1 and 900 seconds) within which the TEA Agent randomly delays the first execution of a script.

  3. Save the file.
  4. Restart the TEA Agent.

 

For example, if the delay period is set to 600 seconds (10 minutes), you can expect Execution Plans to take up to 10 minutes to start in each of the following situations:

  • TEA Agent restarts
  • End of a blackout period
  • Inactive Execution Plan becomes active