WebDriver Monitor

Use the WebDriver Monitor to record and run performance scripts for a specific browser and platform. You can record or upload your own XML scripts, which are translated to WebDriver commands and passed to a Selenium server. Selenium runs the scripts in a real browser and operating environment. The collected results sends are then sent back to the ASM Dashboard.
cacm82
Use the WebDriver Monitor to record and run performance scripts for a specific browser and platform. You can record or upload your own XML scripts, which are translated to WebDriver commands and passed to a Selenium server. Selenium runs the scripts in a real browser and operating environment. The collected results sent are then sent back to the ASM Dashboard.
To know more about OPMS, see the video on
How to Get Started with Real Browser Monitoring in DX App Synthetic Monitor
:

2
Supported Browsers and Platforms
This monitor is available for the following browsers and platforms:
Browser:
  • Chrome (version 72.0)
  • Firefox (version 65.0)
Platform:
  • Linux
For more information about Selenium supported browsers and platforms, see Platforms Supported by Selenium
Configure WebDriver Monitor
WebDriver monitors have the following configuration options:
  • General:
    • Name:
      Enter the monitor name
    • Upload a valid WebDriver script
      : Use this field to create a functional test by uploading a WebDriver script into this monitor. Select
      Browse
      and select the script file (.xml). For more information about WebDriver scripts, see Build WebDriver Scripts.
      Important:
      A script is limited to 2.00-MB file size.
    • Browser
      : Defines the browser that is used to play back the check.
    • Time-out in seconds:   If the monitor does not get a response before the time-out, an alert (error) is generated. The maximum time-out value that is allowed is 90. The time-out that is specified is the total time-out of the following parameters:
      • resolve time
      • connect time
      • read time
    • Alert Contact: Specifies the alert address for the monitor. You can add and modify addresses by clicking
      Edit
      .
      Important!
      If you select
      Edit
      , changes in this screen disappear.
      The
      Main e-mail
      address is the e-mail address that is entered in the
      Account details
      under
      Subscription.
      Your login name is also available there. Select
      none
      to record errors only in the log file (for reporting) without sending any alert message.
  • Advanced
    • Tags: 
      Tags are text labels that can be assigned to any monitor. A monitor can have any number of tags. The same tags can be used for multiple monitors. Use tags to organize your monitors regardless of the folders that the monitors are in. Use tags to define log reports or graphs. Enter any number of tags that are separated by spaces.
    • Notes:
      The Notes field does not affect the monitoring. You can use this field as a personal notepad, a reminder, or a notice for your colleagues.
    • First limit
      : Defines the first boundary in milliseconds. Performance measure:
      • Good -
        total time is below this limit, the server is performing well
      • Poor -
        total time between the first and second limit
      • Bad -
        above the second limit
        Note:
        This boundary affects the graphs and charts, not the alarms.
    • Second limit
      : Defines the second boundary in milliseconds. This boundary affects the graphs and charts, not the alarms. Performance measure total time:
      • Poor -
        above the first limit and below the second limit
      • Bad -
        above the second limit
    • User name (Optional)
      : (Optional) If the monitored host requires authentication, fill out the user name. If this field is used, also fill out the Password field.
    • Password
      : (Optional) If the monitored host requires authentication, fill out this field. If this field is used, also fill out the user name field.
    • Authentication type:
      (Optional) If the monitored host requires authentication, select authentication.
      Default:
      none
      Supported Authentication types:
      • None: No authentication
      • Basic: Uses user name and password
      • Digest: Uses Digest access authentication
    • Host
      : Enter the host name, for example: www.mysite.co.uk .
    • Use Proxy (OPMS version 8.7+)
      (Optional)
      : If the monitored host requires authentication, fill out the user name. If this field is used, also fill out the Password field.
      Available Options:
      • Don't use Proxy
      • Use system Proxy
      • Use custom Proxy
    • Alert on embedded elements errors
      : Tick to receive alerts when embedded elements, for example, JavaScript files, CSS files, and images, fail to load. Such errors occur frequently.
    • Allow browser to make requests to
      : Select to where the browser can make requests. Use this option to avoid phony hits to your website visitor statistics. By default, the browser only makes requests to the site domain. If you do not have visitor trackers on the page, you can select to allow requests everywhere. You can allow loading external page assets from a selected list of domains, while still guarding hits to analytics trackers.
    • Deny requests to selected URIs
      : Comma-separated list of domains to deny requests to, or a regular expression delimited by slashes. Any request with URI matching the regular expression is blocked.
    • Disable HTML5 media
      : Tick to reduce monitor bandwidth use and to prevent download of HTML5 media elements, for example, audio, video, and source.
    • User agent
      : Defines the user agent announced by the monitoring stations at each visit of the monitored web server. Select from the following options:
      • Native
        : Uses the agent that is defined in the browser.
      • Custom
        : Lets you specify a custom user agent.
        Note:
        The user agent does not impact the browser version that the monitor uses.
    • Transaction Tag header
      : Sends custom values as HTTP headers to the tested service. This option can be used to track each test for any other logging purposes.
    Locations
    Monitor order algorithm:
    ASM selects a monitoring station for the second opinion automatically from the order algorithm you select for a given rule. Select from the following options:
    • Master
      - Next Monitor Station is the nearest monitor station.
    • Random
      - Next Monitor Station is a random monitor station.
    • Sequential
      - Next Monitor Station is the next one in the sequence.
    • Sticky
      -  If the previous probe returned an error, the algorithm uses the same monitor station. Otherwise, it picks a random one.
    Check Periods
    • Delay between checks:
      Specifies the delay between the subsequent checks of the monitor. The package that you are subscribed to determines the minimum delay.
    • Check period
      : Specifies the time period of monitor checks. To activate, a start time, and duration. Optionally you can set the repetition period and the date field is updated automatically every period.
    • Maintenance:
      Used to plan maintenance for the monitor. Monitors continue to perform checks during maintenance. The errors that occur during maintenance do not count as errors in reports and do not trigger message alerts.
    • Check on these days only
      : Check a monitor only on specific days of the week. Useful for a monitor that is used to check an item in a Service Level Agreement.
    Alerting
    • Warn me
      : Specify when CA App Synthetic Monitor sends alerts to you.
    • N
      otify me when up again: Tick the box to receive a notification when the monitor is not in alert state.
    • Remind me again after an alert in
      :  Select the interval between the subsequent reminders. To deactivate, select 'Never'.
Workflow
The following diagram shows the WebDriver Monitor workflow.
WebDriver Workflow
WebDriver Workflow