1/10/2023 0 Comments Webmon log url![]() Mark the checkbox to follow HTTP redirects. This sets the CURLOPT_HTTPHEADER cURL option. The macros can then be referenced in the steps as macros are supported. Variables that may be used in scenario steps (URL, post variables). Note that only simple authentication is supported with HTTP proxy. If you specify the wrong protocol, the connection will fail and the item will become unsupported. You may also enter a SOCKS proxy address. The entered value is passed on "as is", no sanity checking takes place. If not specified, the proxy will not overwrite proxy-related environment variables. If specified, the proxy will overwrite proxy related environment variables like http_proxy, HTTPS_PROXY. With no protocol specified, the proxy will be treated as an HTTP proxy. The optional protocol:// prefix may be used to specify alternative proxy protocols (the protocol prefix support was added in cURL 7.21.7). You can specify an HTTP proxy to use, using the format sets the CURLOPT_PROXY cURL option. This is useful when a website returns different content for different browsers. Zabbix will pretend to be the selected browser. Note: Zabbix will not repeat a step because of a wrong response code or the mismatch of a required string. Up to 10 attempts can be specified, default value is 1. The figure set will equally affect each step of the scenario. In case of network problems (timeout, no connectivity, etc) Zabbix can repeat executing a step several times. The number of attempts for executing web scenario steps. New web scenarios will be checked within 60 seconds of their creation. 5m → 30s), the next check will be executed according to the previous value (farther in the future with the example values). ![]() Note that if a user macro is used and its value is changed (e.g. ![]() Name of the host/template that the scenario belongs to. The Scenario tab allows you to configure the general parameters of a web scenario.Īll mandatory input fields are marked with a red asterisk. Enter parameters of the scenario in the form.Click on Create scenario to the right (or on the scenario name to edit an existing scenario).Click on Web in the row of the host/template.Go to: Configuration → Hosts (or Templates).See also known issues for web monitoring using HTTPS protocol. All cookies are preserved during the execution of a single scenario. Maximum number of redirects is hard-coded to 10 (using cURL option CURLOPT_MAXREDIRS). ![]() When running a web scenario, Zabbix will optionally follow redirects (see option Follow redirects below). Zabbix web monitoring supports both HTTP and HTTPS. It can execute a simulated login and follow a path of simulated mouse clicks on the page. Zabbix can also check if a retrieved HTML page contains a pre-defined string. The data is automatically used for graphs, triggers and notifications. The following information is collected in any web scenario step:įor more details, see web monitoring items.ĭata collected from executing web scenarios is kept in the database. average download speed per second for all steps of whole scenario.The following information is collected in any web scenario: That means that web scenarios can also be created on a template level and then applied to multiple hosts in one move. Web scenarios are attached to hosts/templates in the same way as items, triggers, etc. If a host is monitored by proxy, the steps are executed by the proxy. The steps are periodically executed by Zabbix server in a pre-defined order. A web scenario consists of one or several HTTP requests or "steps". To activate web monitoring you need to define web scenarios. To perform web monitoring Zabbix server must be initially configured with cURL (libcurl) support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |