Zabbix Documentation 2.2

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:web_monitoring

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:web_monitoring [2018/02/08 06:17]
martins-v if a host is monitored by proxy, the steps are executed by the proxy.
manual:web_monitoring [2019/04/05 12:39] (current)
martins-v more precise wording
Line 80: Line 80:
 |//​Variables// ​ |List of step-level variables (macros) that may be used for GET and POST functions.\\ Step-level variables override scenario-level variables or variables from the previous step. However, the value of a step-level variable only affects the step after (and not the current step).\\ They have the following format:\\ **{macro}**=value\\ **{macro}**=regex:<​regular expression>​\\ For more information see variable description on the [[web_monitoring#​configuring_a_web_scenario|scenario]] level.\\ Having step-level variables is supported //starting with Zabbix 2.2//.\\ //Note//: Variables are not URL-encoded. ​ | |//​Variables// ​ |List of step-level variables (macros) that may be used for GET and POST functions.\\ Step-level variables override scenario-level variables or variables from the previous step. However, the value of a step-level variable only affects the step after (and not the current step).\\ They have the following format:\\ **{macro}**=value\\ **{macro}**=regex:<​regular expression>​\\ For more information see variable description on the [[web_monitoring#​configuring_a_web_scenario|scenario]] level.\\ Having step-level variables is supported //starting with Zabbix 2.2//.\\ //Note//: Variables are not URL-encoded. ​ |
 |//​Timeout// ​ |Zabbix will not spend more than the set amount of seconds on processing the URL. 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  | |//​Timeout// ​ |Zabbix will not spend more than the set amount of seconds on processing the URL. 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 string// ​ |Required regular ​expressions ​pattern.\\ Unless retrieved content (HTML) matches required pattern the step will fail. If empty, no check is performed.\\ For example:\\ Homepage of Zabbix\\ Welcome.*admin\\ //Note//: Referencing [[regular_expressions|regular expressions]] created in the Zabbix frontend is not supported in this field.\\ //Starting with Zabbix 2.2//, this field may contain supported [[manual:​appendix:​macros:​supported_by_location|macros]]. ​ | +|//Required string// ​ |Required regular ​expression ​pattern.\\ Unless retrieved content (HTML) matches ​the required pattern the step will fail. If empty, no check on required string ​is performed.\\ For example:\\ Homepage of Zabbix\\ Welcome.*admin\\ //Note//: Referencing [[regular_expressions|regular expressions]] created in the Zabbix frontend is not supported in this field.\\ //Starting with Zabbix 2.2//, this field may contain supported [[manual:​appendix:​macros:​supported_by_location|macros]]. ​ | 
-|//Required status codes// ​ |List of expected HTTP status codes. If Zabbix gets a code which is not in the list, the step will fail.\\ If empty, no check is performed.\\ For example: 200,​201,​210-299\\ //Starting with Zabbix 2.2//, user macros can be used in this field. ​ |+|//Required status codes// ​ |List of expected HTTP status codes. If Zabbix gets a code which is not in the list, the step will fail.\\ If empty, no check on required status codes is performed.\\ For example: 200,​201,​210-299\\ //Starting with Zabbix 2.2//, user macros can be used in this field. ​ |
  
 <​note>​Any changes in web scenario steps will only be saved when the whole scenario is saved.</​note>​ <​note>​Any changes in web scenario steps will only be saved when the whole scenario is saved.</​note>​