What is the best practice for creating Synthetic Watchpoints?
BMC strongly recommends implementing the Synthetic Device Configuration Pack so you can more quickly realize value from your monitored synthetic transactions. Implement the configuration pack on a new installation of the Real User Analyzer or Real User Monitor.
Do not implement the configuration pack on a system that already has manual configurations as the configuration pack resets all existing configuration to the default settings
If you want to implement the device configuration pack on a system that has manual configurations, be sure to back up your current configuration:
· Select the Administration tab. From Manage Configuration, select Download device configuration.
· Enter a passphrase. If you want to recover the backup configuration, you will need to reenter this passphrase.
If you prefer not to use the device configuration pack you will need to do these 5 steps manually on the Analyzer.
1) After implementing the synthetic device configuration pack you will see two new page watchpoints:
2) After implementing the synthetic device configuration pack you will have three new custom error detection rules to notify you about synthetic transactions with availability errors, accuracy errors, or execution errors:
3) After implementing the synthetic device configuration pack you will have a session termination rule to define the conditions under which the system considers a session ended. For synthetic monitoring, each run of an Execution Plan is a session:
4) After implementing the synthetic device configuration pack you will have rules added to the following existing system custom fields: Group ID, User ID, Application Name
5) After implementing the synthetic device configuration pack you will see an object-type detection rule. This defines synthetic objects as document-type objects.
And this is how Watchpoints appear in the Analyzer after implementing the device config pack (or implementing the steps manually):
UPDATE! With version 2.6.10, no synthetic configuration is required for the Collector.
After implementing the configuration pack and adding the Confidentiality policy, you can edit and add Watchpoints. Synthetic (as opposed to real) watchpoints are primarily based on POST parameters describing different Synthetic aspects.
In Synthetic EUEM you have pages and you have objects. With Synthetic there is one object for each page. It is a one-to-one relationship. You have one object and one page for each synthetic transaction execution.
With Synthetic EUEM there are more things you can do with pages than with objects. So for Synthetic, if you create watchpoints you should create watchpoints on pages.
The table below lists a few of the many queries available to you. This is not a complete list. It includes only queries most likely to be used. The rows shaded green are the most popular.
ID of the executing agent
Name of the executing agent
ID of agent group of this agent
Name of agent group of this agent
ID of executed Business Service
Name of executed Business Service
ID executed Execution plan
Name of executed Execution plan
ID of the script used
Name of the script used
Name of the script used
# of Availability errors
# of Accuracy errors
# of Execution errors
Did the session terminate