Transactions generated by ASM are synthetic and users may wish to exclude these transactions from live end user monitoring.
How can I differentiate ASM web traffic from normal web traffic incoming to an application?
This solution applies to Full Page, Real Browser Monitors, HTTP/ HTTPS, and Script Monitors.
To differentiate ASM traffic from other network sources, Full Page, Real Browser Monitors, HTTP/ HTTPS, and Script Monitors each have a "Transaction Tag Header" field located towards the bottom of the Advanced monitor options. This field allows for custom values as HTTP headers to be sent to the tested service and can be used to track each test or for any other logging purposes. This property accepts name: value pairs. For example:
With the following list of predefined placeholders available by default in ASM:
Optionally, you can use the following preset headers:
Note: When tracking custom headers, custom headers with all capital letter header names will be converted to only the first letter capital, for example: WPM-TAGS will be converted to Wpm-tags
While less commonly used, the "User Agent" field can also be used to differentiate traffic. Monitor types such as HTTP/ HTTPS, Full Page, and Real Browser Monitors all have a "User Agent" field which can specific specific browsers types or identifiable user agents such as "Watch Mouse", "CA Technologies", and "Nimsoft".
For Script Monitors, the ASM UI does not allow a user to specify the user agent. However, Jmeter allows for custom http headers to be defined, including user agent, and so this can be accomplished in the script. See Jmeter's documentation on this site below: