[comment]: # ({0decccc5-0decccc5})
# 5 Web scenarios

[comment]: # ({/0decccc5-0decccc5})

[comment]: # ({87f8bcb8-f081f01c})
#### Overview

The [web scenario](/manual/web_monitoring) list for a host can be accessed from *Data collection → Hosts*
by clicking *Web* for the respective host.

A list of existing web scenarios is displayed.

![](../../../../../../assets/en/manual/web_interface/web_scenarios.png){width="600"}

Displayed data:

|Column|Description|
|--|--------|
|*Name*|Name of the web scenario. Clicking the web scenario name opens the web scenario [configuration form](/manual/web_monitoring#configuring-a-web-scenario).<br>If the host web scenario belongs to a template, the template name is displayed before the web scenario name as a gray link. Clicking the template link will open the web scenario list on the template level.|
|*Number of steps*|The number of steps the scenario contains.|
|*Update interval*|How often the scenario is performed.|
|*Attempts*|How many attempts for executing web scenario steps are performed.|
|*Authentication*|Authentication method is displayed - Basic, NTLM, Kerberos, Digest, or None.|
|*HTTP proxy*|Displays HTTP proxy or 'No' if not used.|
|*Status*|Web scenario status is displayed - *Enabled* or *Disabled*.<br>By clicking the status you can change it.|
|*Tags*|Web scenario tags are displayed.<br>Up to three tags (name:value pairs) can be displayed. If there are more tags, a "..." link is displayed that allows to see all tags on mouseover.|
|*Info*|If everything is working correctly, no icon is displayed in this column. In case of errors, a square icon with the letter "i" is displayed. Hover over the icon to see a tooltip with the error description.|

To configure a new web scenario, click the *Create web scenario* button at the upper-right corner.

[comment]: # ({/87f8bcb8-f081f01c})

[comment]: # ({7ff4a29b-1f28be9a})
##### Mass editing options

Buttons below the list offer some mass-editing options:

-   *Enable* - change the scenario status to *Enabled*
-   *Disable* - change the scenario status to *Disabled*
-   *Clear history and trends* - clear history and trend data for the scenarios
-   *Delete* - delete the web scenarios

To use these options, mark the checkboxes before the respective web
scenarios, then click the required button.

[comment]: # ({/7ff4a29b-1f28be9a})

[comment]: # ({d1fc0dba-a55df61a})
##### Using filter

You can use the filter to display only the scenarios you are interested
in. For better search performance, data is searched with macros
unresolved.

The *Filter* link is available above the list of web scenarios.
Clicking it will open a filter where you can specify the desired filtering criteria.

![](../../../../../../assets/en/manual/web_interface/web_scenario_filter.png){width="600"}

|Parameter|Description|
|--|--------|
|*Host groups*|Filter by one or more host groups.<br>Specifying a parent host group implicitly selects all nested host groups.|
|*Hosts*|Filter by one or more hosts.<br>If host groups are already selected above, host selection is limited to those groups.|
|*Status*|Filter by web scenario status.|
|*Tags*|Filter by web scenario tag name and value.<br>It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.<br><br>There are several operators available for each condition:<br>**Exists** - include the specified tag names;<br>**Equals** - include the specified tag names and values (case-sensitive);<br>**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive);<br>**Does not exist** - exclude the specified tag names;<br>**Does not equal** - exclude the specified tag names and values (case-sensitive);<br>**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive).<br><br>There are two calculation types for conditions:<br>**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition;<br>**Or** - enough if one condition is met.|

[comment]: # ({/d1fc0dba-a55df61a})