Zabbix Documentation 1.8


Table of Contents

4 WEB Step

Step is basically a HTTP request. Steps are executed in a pre-defined order.

Parameter Description
Name Name of the step.
For example: Login
For example:
Post HTTP POST variables, if any.
For example:
If {user} is defined as a macro of the WEB scenario, it will be replaced by its value when the step is executed.
The information will be sent as is, variables are not URL-encoded..
Timeout Do not spend more than Timeout seconds for execution of the step. Actually this parameter defines maximum time for making connection to the URL and maximum time for performing an HTTP request. Therefore, Zabbix will not spend more than 2 x Timeout seconds on the step.
For example: 15
Required The string (given as POSIX extended regular expression) must exist in retrieved content.
Otherwise this step fails. If empty, any content will be accepted.
For example: Homepage of Zabbix
Status codes List of HTTP status codes to be considered as success. If retrieved status code is not in the list, this step fails.
If empty, any status code is accepted.
For example: 200,210

As soon as a step is created, Zabbix automatically adds the following items for monitoring and links them to the selected application. Actual scenario and step names will be used instead of "Scenario" and "Step" respectively.

Item Description
Download speed for step 'Step' of scenario 'Scenario' This item will collect information about download speed (bytes per second) of the step.
Item key:[Scenario,Step,bps]
Type: float
Response time for step 'Step' of scenario 'Scenario' This item will collect information about response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred.
Item key: web.test.time[Scenario,Step,resp]
Type: float
Response code for step 'Step' of scenario 'Scenario' This item will collect response codes of the step.
Item key: web.test.rspcode[Scenario,Step]
Type: integer

Web monitoring items are added with 30 day history retention and 90 day trend retention periods.

These items can be used to create triggers and define notification conditions.

Example 1

Trigger "Zabbix GUI login is too slow"

The trigger expression can be defined as:

{zabbix: web.test.time[ZABBIX GUI,Login,resp].last(0)}>3