Recommended configuration for synthetic monitoring: 2.5.01
BMC strongly recommends configuring the BMC Synthetic End User Experience Monitoring system to increase the effectiveness of filters and the grouping of results. The recommended configuration provides following benefits:
- Names of elements such as Execution Plans and TEA Agent Groups are displayed
- All related synthetic objects are grouped into sessions
- Session details are displayed in the Session Browser or in the Session Overview pages
This topic contains a description of the recommended settings for synthetic monitoring. Configure the system manually if you have a working system to which you want to add synthetic monitoring.
Perform all configurations in the Real User Analyzer or Monitor. You can adjust the recommended or automatic configuration to suit you and your organization's requirements.
Watchpoints for synthetic transactions
Define page Watchpoints (Administration > Watchpoint Management > Available Watchpoints) for detailed monitoring of the performance and availability for all synthetic transactions.
Watchpoints configuration for synthetic transactions
Custom error-detection rules
Create custom error-detection rules (Administration > Thresholds and problem detection > Error detection rules) to notify you about synthetic transactions with availability errors, accuracy errors, or execution errors.
Error-detection rules for synthetic transactions
Use the Move up and Move down arrows to ensure that the new rules appear before the first rule with a Stop match policy, as shown in the following image.
Example of the synthetic error-detection rules above the first Stop match policy
Click to enlarge image.
Session termination rule
Create session termination rules (Administration > Data flow settings > Session detection, click Termination rules) to define the conditions under which the system considers a session ended. For synthetic monitoring, each run of an Execution Plan is a session.
Session termination rule for synthetic transactions
Example of session termination rule
Click to enlarge image.
Extraction rules on custom fields
Add an extraction rule to custom fields (Administration > Data flow settings > Custom fields) to determine the POST parameter within a page that contributes its data to the field. Add rules to the following existing system custom fields:
- Group ID is a session custom field. The added rule enables the Session Browser to display the name of the Execution Plan in the Group ID column of the page.
- User ID is a session custom field. The added rule enables the Session Browser to display the name of the TEA Agent Group in the User ID column of the page.
- Application Name is a page custom field. The added rule enables the name of the Execution Plan to be displayed as an Application. You can use the name of the Execution Plan to create Application Watchpoints for monitoring through the BMC Application Performance Management Console.
Extraction rules for Group ID field
Example of extraction rule for Group ID
Click to enlarge image.
Extraction rules for User ID field
Example of extraction rule for User ID
Click to enlarge image.
Extraction rules for Application Name field
Example of extraction rule for Application Name
Click to enlarge image.
Object type detection
Add an object-type detection rule (Administration > Data flow settings > Object type detection) to the Default catch-all policy. The object-type detection rule defines synthetic objects as document-type objects.
Ensure that the document type is ordered above the container.
Example of object type detection rule
Click to enlarge image.
Where to go from here
Configure the confidentiality policy to view synthetic POST parameters.
Related topic
Configuring-synthetic-monitoring
Implementing-Synthetic-Device-Configuration-Pack-2-5-01
Viewing-the-results-of-synthetic-transaction-monitoring