I. Overview of web monitoring
In this section, we will show you how to use Zabbix for URL monitoring, specifically for URL monitoring, such as PHP applications, as long as we can curl to this ok.php, we think this service is normal, Zabbix Web monitoring also have similar features.
If you need to use this feature, you need to add libcurl support when compiling.
Before we begin, we introduce a concept of Zabbix-"Web Scenarios", a network scenario, which is the process of a series of operations performed on the network by the user in order to accomplish a goal. For example, to log in to Weibo is a "network scene" in which each step of the operation-open page, initiate login request, login success or failure, collectively referred to as "step" in Zabbix. Defining a Web scenarios, we need to define what steps to follow, and in what order, and then Zabbix periodically perform these "steps" in the order in which they are set.
In zabbix2.2, web scenarios and items, Triggers, are attached to the host or template, which means that scenes such as the Web can also be created on templates and can be applied to multiple hosts.
Collect the following information in any network scenario:
1. Average download speed for all steps
2. Number of failed steps
3. Last error message
Collect the following information in all steps:
1. Average download speed
2. Response Time
3. Response code
Zabbix can examine an HTML page that contains a predefined string to see if a string exists. It can perform a simulated login and follow the path of a simulated mouse click.
Zabbix also supports web monitoring for HTTP and HTTPS. In a Web scenarios, an error cookie is also made to truly simulate a complete visit.
Second, web monitoring to create
1, click: configuration→hosts (or Templates)
2. Click the Web in the Host/template column
3. In the upper right corner, click Create Scenario
Where you can configure the following parameters
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/72/FE/wKiom1XxUOmSvsJ5AAH3D3B1p9g414.jpg "title=" Qq20150910174235.jpg "alt=" Wkiom1xxuomsvsj5aah3d3b1p9g414.jpg "/>
Parameter explanation:
Name: The only scene rank, after zabbix2.2 can use the macro,
Application: Which application does the scene belong to,
New application: If there is no suitable application can fill in here new,
Update interval (in sec): Detection frequency,
Retries: When there is a problem, try again several times to think there is a problem,
Agent: Simulates the browser client,
HTTP proxies: You can specify an HTTP proxy to use, default to 1080 port,
Variables: Variable macros in the scene, official documentation of the specific settings,
Headers: Header information added at the time of request,
Enabled: whether to enable this monitoring,
Below we look at the step options
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/72/FF/wKiom1XxVvGQL-qbAAJC5NcoHFM767.jpg "style=" float: none; "title=" qq20150910180844.jpg "alt=" Wkiom1xxvvgql-qbaajc5ncohfm767.jpg "/>
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/72/FF/wKiom1XxVvLx-H5zAAFfYjcsPD8858.jpg "style=" float: none; "title=" qq20150910180931.jpg "alt=" Wkiom1xxvvlx-h5zaaffyjcspd8858.jpg "/>
Name:
URL:
Post:
Variables:
Headers:
Follow redirects:
Retrieve Only headers:
Timeout:
Required string:
Required Status Codes:
Reference Document: Https://www.zabbix.com/documentation/2.4/manual/web_monitoring?s[]=web
This article is from the "Little Water Drop" blog, please make sure to keep this source http://wangzan18.blog.51cto.com/8021085/1693526
Zabbix Web Network Monitoring