When you run a LoadView test, Load Injectors send requests to the target resource. You can identify LoadView traffic in traffic reports, analytics tools, or server logs by the User-Agent header.

LoadView requests include a product identifier in the User-Agent string. The value indicates the type of the test and that the request was generated by the LoadView platform:

  • Protocol-based tests: DMBrowser/2.1 (SV; LV)
  • Browser-based tests: DMBrowser/2.1 (UV; LV)

Use this value to detect and filter load testing traffic in your systems.

Example User-Agent Header

A complete User-Agent header can look like this:

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36 DMBrowser/2.1 (UV; LV)

Use the DMBrowser/2.1 (UV; LV) value to identify LoadView requests and exclude them from traffic reports or analytics when required.

If you need to identify LoadView traffic by IP address instead, you can configure the LoadView test to use the Public Proxy option. This provides a set of static IP addresses that you can use for traffic filtering.

For information about configuring the Public Proxy option, see Testing Behind a Firewall with LoadView Static Proxy Server. For the current list of static proxy IP addresses, see List of Static Proxy IPs.