Zabbix Documentation 4.0

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 [2019/04/17 06:04]
martins-v updating screenshot
manual:web_monitoring [2019/04/17 08:24] (current)
martins-v setting 'protocol' for http proxy string is optional
Line 58: Line 58:
 |//​Attempts// ​ |The number of attempts for executing web scenario steps. In case of network problems (timeout, no connectivity,​ etc) Zabbix can repeat executing a step several times. The figure set will equally affect each step of the scenario. Up to 10 attempts can be specified, default value is 1.\\ //Note//: Zabbix will not repeat a step because of a wrong response code or the mismatch of a required string.\\ This parameter is supported starting with //Zabbix 2.2//​. ​ | |//​Attempts// ​ |The number of attempts for executing web scenario steps. In case of network problems (timeout, no connectivity,​ etc) Zabbix can repeat executing a step several times. The figure set will equally affect each step of the scenario. Up to 10 attempts can be specified, default value is 1.\\ //Note//: Zabbix will not repeat a step because of a wrong response code or the mismatch of a required string.\\ This parameter is supported starting with //Zabbix 2.2//​. ​ |
 |//​Agent// ​ |Select a client agent.\\ Zabbix will pretend to be the selected browser. This is useful when a website returns different content for different browsers.\\ User macros can be used in this field, //starting with Zabbix 2.2//​. ​ | |//​Agent// ​ |Select a client agent.\\ Zabbix will pretend to be the selected browser. This is useful when a website returns different content for different browsers.\\ User macros can be used in this field, //starting with Zabbix 2.2//​. ​ |
-|//HTTP proxy// ​ |You can specify an HTTP proxy to use, using the format: //%%http://​[username[:​password]@]proxy.mycompany.com[:​port]%%//\\ The proxy string can be specified with a ''​%%protocol://​%%''​ prefix - optional and only supported from cURL 7.21.7 (see [[https://​curl.haxx.se/​docs/manpage.html#-x|cURL manpage]]).\\ By default, 1080 port will be used. With no protocol specified, the proxy will be treated as an HTTP proxy.\\ If specified, the proxy will overwrite proxy related environment variables like http_proxy, HTTPS_PROXY. If not specified, the proxy will not overwrite proxy related environment variables.\\ The entered value is passed on "as is", no sanity checking takes place. You may also enter a SOCKS proxy address. If you specify the wrong protocol, the connection will fail and the item will become unsupported.\\ //Note//: Only simple authentication is supported with HTTP proxy.\\ User macros can be used in this field.\\ This parameter is supported starting with //Zabbix 2.2//​. ​ |+|//HTTP proxy// ​ |You can specify an HTTP proxy to use, using the format ​''​%%[protocol://][username[:​password]@]proxy.mycompany.com[:​port]%%''​.\\ This sets the [[https://​curl.haxx.se/​libcurl/c/​CURLOPT_PROXY.html|CURLOPT_PROXY]] cURL option.\\ The optional ''​%%protocol://​%%''​ prefix may be used to specify alternative proxy protocols (the protocol prefix support was added in cURL 7.21.7). With no protocol specified, the proxy will be treated as an HTTP proxy.\\ By default, 1080 port will be used.\\ If specified, the proxy will overwrite proxy related environment variables like http_proxy, HTTPS_PROXY. If not specified, the proxy will not overwrite proxy-related environment variables. The entered value is passed on %%"%%as is%%"%%, no sanity checking takes place.\\ You may also enter a SOCKS proxy address. If you specify the wrong protocol, the connection will fail and the item will become unsupported.\\ //​Note// ​that only simple authentication is supported with HTTP proxy.\\ User macros can be used in this field.\\ This parameter is supported starting with //Zabbix 2.2//​. ​ |
 |//​Variables// ​ |Variables that may be used in scenario steps (URL, post variables).\\ They have the following format:\\ **{macro1}**=value1\\ **{macro2}**=value2\\ **{macro3}**=regex:<​regular expression>​\\ For example:\\ {username}=Alexei\\ {password}=kj3h5kJ34bd\\ {hostid}=regex:​hostid is ([0-9]+)\\ The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values. Note that variables with ''​regex:''​ need one step to get the value of the regular expression so the extracted value can only be applied to the step after.\\ If the value part starts with ''​regex:''​ then the part after it is treated as a regular expression that searches the web page and, if found, stores the match in the variable. At least one subgroup must be present so that the matched value can be extracted.\\ Regular expression match in variables is supported //since Zabbix 2.2//.\\ User macros and {HOST.*} [[:​manual/​appendix/​macros/​supported_by_location|macros]] are supported, since Zabbix 2.2.\\ Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.  | |//​Variables// ​ |Variables that may be used in scenario steps (URL, post variables).\\ They have the following format:\\ **{macro1}**=value1\\ **{macro2}**=value2\\ **{macro3}**=regex:<​regular expression>​\\ For example:\\ {username}=Alexei\\ {password}=kj3h5kJ34bd\\ {hostid}=regex:​hostid is ([0-9]+)\\ The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values. Note that variables with ''​regex:''​ need one step to get the value of the regular expression so the extracted value can only be applied to the step after.\\ If the value part starts with ''​regex:''​ then the part after it is treated as a regular expression that searches the web page and, if found, stores the match in the variable. At least one subgroup must be present so that the matched value can be extracted.\\ Regular expression match in variables is supported //since Zabbix 2.2//.\\ User macros and {HOST.*} [[:​manual/​appendix/​macros/​supported_by_location|macros]] are supported, since Zabbix 2.2.\\ Variables are automatically URL-encoded when used in query fields or form data for post variables, but must be URL-encoded manually when used in raw post or directly in URL.  |
 |//​Headers// ​ |Custom HTTP headers that will be sent when performing a request.\\ Headers should be listed using the same syntax as they would appear in the HTTP protocol, optionally using some additional features supported by the [[http://​curl.haxx.se/​libcurl/​c/​CURLOPT_HTTPHEADER.html|CURLOPT_HTTPHEADER]] cURL option.\\ For example:\\ Accept-Charset=utf-8\\ Accept-Language=en-US\\ Content-Type=application/​xml;​ charset=utf-8\\ User macros and {HOST.*} [[:​manual/​appendix/​macros/​supported_by_location|macros]] are supported.\\ Specifying custom headers is supported //starting with Zabbix 2.4//​. ​ | |//​Headers// ​ |Custom HTTP headers that will be sent when performing a request.\\ Headers should be listed using the same syntax as they would appear in the HTTP protocol, optionally using some additional features supported by the [[http://​curl.haxx.se/​libcurl/​c/​CURLOPT_HTTPHEADER.html|CURLOPT_HTTPHEADER]] cURL option.\\ For example:\\ Accept-Charset=utf-8\\ Accept-Language=en-US\\ Content-Type=application/​xml;​ charset=utf-8\\ User macros and {HOST.*} [[:​manual/​appendix/​macros/​supported_by_location|macros]] are supported.\\ Specifying custom headers is supported //starting with Zabbix 2.4//​. ​ |