In order to use Experience monitoring to monitor an application, you need to create a web app group. When you create it you are asked to specify the source monitoring points, web app URLs, and workflows you wish to use. A web path is then created for all combinations of these components. For example, four monitoring points, two web app URLs, and one workflow results in eight web paths being created in the web app group. Typically though, all web paths within a web app group use the same target web app.

Depending on the workflow type you specify when creating the web app group, the web paths you create will either emulate users accessing a web app via a browser or they will send HTTP requests to the web app’s API.

Create a web app group

To create the web app group:

Initiate web app group creation

  1. Navigate to Experience > Web App Groups.
  2. Click + Web App Group.
  3. In the Name field, specify a name for the web app group.
  4. In the Description field, describe the web app group (optional).
  5. Click Next.
    • You return to the Web App Groups page.

Specify source monitoring points

  1. In the Monitor from… pane, click .
    • The Monitoring Points for Web App Group:<group-name> page opens.
  2. Select the monitoring points you want to use.
    • If a monitoring point has more than one interface available they will appear in the Local Network Interface column.
  3. Select the interface(s) to use.
  4. If the monitoring point is in a location serviced by a proxy, click the appropriate link in the Proxy Settings column.
    • The Edit Proxy Settings dialog appears.
      1. In the Proxy Type field, select the type of proxy being used.
      2. If the Proxy Type is HTTP or SOCKS5, in the Proxy Address field, specify the IP address of the proxy server.
      3. If the Proxy Type is PAC file, in the PAC File URL field, specify the location of the Proxy Auto-Config (PAC) file to use for proxy configuration.
      4. In the Username field, specify a username recognized by the proxy server.
      5. In the Password field, specify the password associated with the Username.
      6. Click Submit.
  5. Click OK.
    • You return to the Web App Groups page.

Specify web app URLs

  1. In the Monitor to… pane, click .
    • The Add Monitor Target page opens.
  2. In the Target URL field, specify the URL of the web app you are monitoring.
    • For the most meaningful results, don’t specify a top level domain. Instead, use a specific webserver (for example, use https://www.google.com, not https://google.com).
    • If the target blocks ICMP traffic, you will be prompted to specify a supplementary target for the associated, auto-generated, network path. Specifying a valid supplementary target will enable Delivery monitoring to collect data such as capacity and network response time.
  3. In the HTTP Authentication field, specify a valid Username and Password if required by the target web application.
    • These credentials are only used with one of the supported authentication methods if prompted for by the target.
    • Note that this is optional. The best practice is to specify authentication parameters at the workflow level.
  4. To specify variables that apply to all workflows in the web app group (optional), click the Need Any Variables? link and specify the variables.
    • This is typically left until your workflow has been specified.
  5. Click OK.
    • You return to the Web App Groups page.

Specify workflows

Select Browser workflow to create web paths that will emulate users accessing a web app via a browser. Select HTTP workflow to create web paths that will send HTTP requests to the web app’s API.

Browser workflow
  1. In the Workflows… pane, click .
    • The Add Workflow page opens.
  2. In the first field, specify a name for the workflow.
  3. Click Add Description, to add a description for the workflow (optional).
  4. In the Type field, select Browser.
  5. For a basic web app group with a minimal script, click either Selenium (recommended) or AppNeta Synthetic, but do not change the defaults.
  6. Click Save.
    • You return to the Web App Groups page.

Note: Some legacy monitoring points do not support Selenium scripting. See Monitoring Point Feature Comparison - Legacy for details.

HTTP workflow
  1. In the Workflows… pane, click .
    • The Add Workflow page opens.
  2. In the first field, specify a name for the workflow.
  3. Click Add Description, to add a description for the workflow (optional).
  4. In the Type field, select HTTP.
  5. In the HTTP Authentication field, specify the type of authentication used by the web app (if any) then specify the Username and Password if required.
  6. If variables are required, click Need Any Variables? and specify them.
  7. In the Request section, specify the request Method (e.g., “GET”) and the API Endpoint to access at the target.
    • For example, if the full endpoint is “https://api.example.com/v7/widget”, the Target URL should be set to “https://api.example.com” and the Endpoint field should be set to “/v7/widget”.
  8. Select Follow Redirects to allow the request to be redirected.
  9. Select Specify HTTP Version if you need to use a specific HTTP protocol version.
  10. In the Headers section, specify any headers if required.
    • Select Form to specify them as pairs of “Name” and “Value” (e.g., Name=”Accept” and Value=”application/json”).
    • Select Text to specify them as a list of “Name:Value” pairs (e.g., “Accept:application/json”).
  11. In the Expected Response section, specify if/how you want to validate the response.
    • In the Expected Status field:
      • Select Any to accept any HTTP status.
      • Select Status Code and specify the expected status code. This can be a single value (e.g., 200), a range of values (e.g., 200-204), or a comma separated list of values (e.g., 200, 201, 202, 300-304).
    • In the Expected Body field:
      • Select Any to accept any response body.
      • Select Contains Text to accept responses with text in the response body matching a specified case sensitive string.
      • Select Contains Regex to accept responses with text in the response body matching a specified Regular Expression. Use this when the basic text match is insufficient.
  12. In the Response Limit field, specify the amount of the response that will be stored with the test results. The entire response is analyzed when received but only the amount specified (to a maximum of 1024 Kbytes) is stored.
  13. In the Preview field, specify Monitoring Point, Target, and Timeout then click Preview to generate a test request and view the response.
  14. In the Alert Profiles section, use the default web path alert profile or, if you need to change from the default, see Experience Alerts.
    • This alert profile applies to all web paths that use the workflow. This can be overridden on an individual web path if necessary.
  15. Click Save.
    • You return to the Web App Groups page.

Note: Some legacy monitoring points do not support HTTP monitoring. See Monitoring Point Feature Comparison - Legacy for details. It is also not supported on Global Monitoring Points.

Configure additional parameters

Once the source monitoring point, the target web app, and the workflow are specified, you can update the license type, the workflow execution interval, the workflow timeout, and the alert profiles used for each web path in the web app group.

  1. In the App License Type field, select the license type.
    • Selecting Unlicensed frees up the application license.
  2. In the Interval field, select the workflow execution interval.
    • The minimum interval you can choose depends on the license type.
  3. In the Timeout (sec) field, specify how long the workflow should wait for a response before continuing.
  4. If you want to override the alert profiles applied to the workflow, you can apply web path alert profiles to the web path.
  5. Click Save.
    • The web app group is created.

View web app groups list

To view the list of web app groups:

  1. Navigate to Experience > Web App Groups.
    • The list of web app groups is displayed.

Note: You can also share a link to the page.

Edit a web app group

You can edit a web app group configuration after it has been created. You can edit a web app group from either the Web App Groups page or from the Web Paths page.

To edit a web app group from the Web App Groups page:

  1. Navigate to Experience > Web App Groups.
  2. For the web app group you want to edit, click Configure.
    • The web app group details are presented in “Edit Mode”.
  3. Update the configuration as required.
  4. Click Save.
    • The configuration changes are saved.

To edit a web app group from the Web Paths page:

  1. Navigate to Experience > Web Paths.
  2. For a web path in the web app group you want to edit, click > Edit Web App.
  3. Click Configure.
    • The web app group details are presented in “Edit Mode”.
  4. Update the configuration as required.
  5. Click Save.
    • The configuration changes are saved.

Rename a web app group

To rename a web app group:

  1. Navigate to Experience > Web App Groups.
  2. For the web app group you want to edit, in the Action dropdown, select Rename.
  3. In the Name field, update the web app group name.
  4. Click Save.
    • The web app group name is changed.

Copy a web app group

To make a copy of a web app group:

  1. Navigate to Experience > Web App Groups.
  2. For the web app group you want to copy, in the Action dropdown, select Copy.
  3. In the Name field, update the web app group name.
  4. Click Save.
    • A copy of the web app group is created.

Delete a web app group

To delete a web app group:

  1. Navigate to Experience > Web App Groups.
  2. For the web app group you want to delete, in the Action dropdown, select Delete.
  3. Click OK.
    • The web app group is deleted.

Edit proxy settings

Proxy settings must be configured when a monitoring point needs to access a web app via a proxy. Typically this is done when you create a web app group (either browser-based or HTTP request-based) but it can be done after the web app group is created.

To edit proxy settings:

  1. Navigate to Experience > Web App Groups.
  2. For the web app group you want to edit, click Configure.
    • The web app group details are presented in “Edit Mode”.
  3. In the Monitor from… pane, click either the Add Proxy Settings or Edit link next to the monitoring point and interface to be configured.
    • The Edit Proxy Settings dialog appears.
      1. In the Proxy Type field, select the type of proxy being used.
      2. In the Proxy Address field, specify the IP address of the proxy server.
      3. In the Username field, specify a username recognized by the proxy server.
      4. In the Password field, specify the password associated with the Username.
      5. Click Submit.
  4. Click OK.
    • You return to the Web App Groups page.
  5. Click Save.
    • The proxy settings are updated.