zabbix监控nginx性能状态

时间 2020-06-29

原文原文链接

ps: nginx在生产环境中的应用愈来愈普遍，因此须要对nginx的性能状态作一些监控来发现出来出现的问题。html

zabbix监控nginx，首先确认nginx的监控指标，主要有：基本活动指标，错误指标，性能指标。 nginx

nginx处理流程图具体以下:shell

注释：Accepts（接受）、Handled（已处理）、Requests（请求数）是一直在增长的计数器。Active（活跃）、Waiting（等待）、Reading（读）、Writing（写）随着请求量而增减express

名称vim	描述centos	指标类型bash
Accepts（接受）服务器	NGINX 所接受的客户端链接数app	资源: 功能curl
Handled（已处理）	成功的客户端链接数	资源: 功能
Active（活跃）	当前活跃的客户端链接数	资源: 功能
Dropped（已丢弃，计算得出）	丢弃的链接数（接受 - 已处理）	工做：错误*
Requests（请求数）	客户端请求数	工做：吞吐量

NGINX worker 进程接受 OS 的链接请求时 Accepts 计数器增长，而Handled 是当实际的请求获得链接时（经过创建一个新的链接或从新使用一个空闲的）。这两个计数器的值一般都是相同的，若是它们有差异则代表链接被Dropped，每每这是因为资源限制，好比已经达到 NGINX 的worker_connections的限制。

首先nginx须要配置nginx_status 具体步骤是：在 zabbix agentd客户端上，查看nginx是否加载了with-http_stub_status_module。由于 zabbix 监控nginx是根据nginx的Stub Status模块，抓取Status模块所提供的数据。假如之前没开启，如今想启用StubStatus 模块，在编译nginx 的时候要加上参数with-http_stub_status_module，执行./configure && make就能够了，不用make install，通常状况下都是安装的，具体的安装配置以下

(一）配置nginx

1,查看nginx_status是否开启，查看已开启。

[root@iZ237lzm354Z scripts]# /usr/local/nginx/sbin/nginx -V

nginx version: nginx/1.4.7

built by gcc 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC)

TLS SNI support enabled

configure arguments: --with-http_stub_status_module --with-http_ssl_module --with-pcre

--with-http_realip_module --with-http_image_filter_module

[root@iZ237lzm354Z scripts]#

2，nginx_status开启的步骤：

[root@iZ237lzm354Z scripts]# vim /usr/local/nginx/conf/nginx.conf

server {

listen 80 ;

server_name www.baidu.com;

rewrite ^/invitejoin/(.*)\.htm[l]?$ /register.shtml?$1 last;

index index.jsp index.html;

root /opt/home;

location = /nginx-status {

stub_status on;

access_log off;

allow 127.0.0.1;

allow 10.253.12.34;

####zabbix服务器端的IP地址通常为内网IP

}

3，测试并启动nginx

[root@iZ237lzm354Z scripts]# /usr/local/nginx/sbin/nginx -t

nginx: the configuration file /usr/local/nginx/conf/nginx.conf syntax is ok

nginx: configuration file /usr/local/nginx/conf/nginx.conf test is successful

[root@iZ237lzm354Z scripts]# /usr/local/nginx/sbin/nginx -s reload

4,用curl来进行测试：

[root@iZ237lzm354Z scripts]# curl www.baidu.com/nginx-status

Active connections: 979

server accepts handled requests

756072922 756072922 1136799890

Reading: 0 Writing: 4 Waiting: 975

备注：

Active connections –当前活跃的链接数量
server accepts handled requests — 总共处理了756072922个链接 , 成功建立 756072922次握手, 总共处理了1136799890个请求
reading — 读取客户端的链接数.
writing — 响应数据到客户端的数量
waiting — 开启 keep-alive 的状况下,这个值等于 active – (reading+writing), 意思就是 Nginx 已经处理完正在等候下一次请求指令的驻留链接.

(二)配置zabbix_agentd

1，编写脚步来获取nginx的相关信息

[root@ittestserver1 opt]# vim /usr/local/zabbix/scripts/nginx-check_performance.sh

#!/bin/bash

##################################

# Zabbix monitoring script

#

# nginx:

# - anything available via nginx stub-status module

#

##################################

# Contact:

# vincent.viallet@gmail.com

# Zabbix requested parameter

ZBX_REQ_DATA="$1"

ZBX_REQ_DATA_URL="$2"

# Nginx defaults

NGINX_STATUS_DEFAULT_URL="www.baidu.com/nginx-status" #(这里写网站的域名)

WGET_BIN="/usr/bin/wget"

#

# Error handling:

# - need to be displayable in Zabbix (avoid NOT_SUPPORTED)

# - items need to be of type "float" (allow negative + float)

#

ERROR_NO_ACCESS_FILE="-0.9900"

ERROR_NO_ACCESS="-0.9901"

ERROR_WRONG_PARAM="-0.9902"

ERROR_DATA="-0.9903" # either can not connect / bad host / bad port

# Handle host and port if non-default

if [ ! -z "$ZBX_REQ_DATA_URL" ]; then

URL="$ZBX_REQ_DATA_URL"

else

URL="$NGINX_STATUS_DEFAULT_URL"

fi

# save the nginx stats in a variable for future parsing

NGINX_STATS=$($WGET_BIN -q $URL -O - 2> /dev/null)

# error during retrieve

if [ $? -ne 0 -o -z "$NGINX_STATS" ]; then

echo $ERROR_DATA

exit 1

fi

#

# Extract data from nginx stats

#

case $ZBX_REQ_DATA in

active_connections) echo "$NGINX_STATS" | head -1 | cut -f3 -d' ';;

accepted_connections) echo "$NGINX_STATS" | grep -Ev '[a-zA-Z]' | cut -f2 -d' ';;

handled_connections) echo "$NGINX_STATS" | grep -Ev '[a-zA-Z]' | cut -f3 -d' ';;

handled_requests) echo "$NGINX_STATS" | grep -Ev '[a-zA-Z]' | cut -f4 -d' ';;

reading) echo "$NGINX_STATS" | tail -1 | cut -f2 -d' ';;

writing) echo "$NGINX_STATS" | tail -1 | cut -f4 -d' ';;

waiting) echo "$NGINX_STATS" | tail -1 | cut -f6 -d' ';;

*) echo $ERROR_WRONG_PARAM; exit 1;;

esac

exit 0

[root@ittestserver1 opt]# chmod +x /usr/local/zabbix/scripts/nginx-check_performance.sh

-rw-r--r-x1 root root 1645 2月 4 14:26/usr/local/zabbix/scripts/nginx-check_performance.sh

2,配置zabbix_agentd.conf。启用UserParameter，并配置相关的参数。

[root@ittestserver1 opt]# vim /usr/local/zabbix/etc/zabbix_agentd.conf

####### USER-DEFINED MONITORED PARAMETERS #######

### Option: UnsafeUserParameters

# Allow all characters to be passed in arguments to user-defined parameters.

# The following characters are not allowed:

# \ ' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @

# Additionally, newline characters are not allowed.

# 0 - do not allow

# 1 - allow

#

# Mandatory: no

# Range: 0-1

# Default:

# UnsafeUserParameters=0

UnsafeUserParameters=1

### Option: UserParameter

# User-defined parameter to monitor. There can be several user-defined parameters.

# Format: UserParameter=<key>,<shell command>

# See 'zabbix_agentd' directory for examples.

#

# Mandatory: no

# Default:

# UserParameter=

UserParameter=nginx[*],/usr/local/zabbix/scripts/nginx-check_performance.sh "$1"

3，重启zabbix_agentd客户端

[root@zabbix ~]# /etc/init.d/zabbix_agentd restart

Shutting down zabbix_agentd: [ OK ]

Starting zabbix_agentd: [ OK ]

[root@zabbix ~]#

4，在zabbix服务端（server）进行测试。

[root@zabbix ~]# zabbix_get -s 10.253.17.20 -p 10050 -k "nginx[reading]"

0

[root@zabbix ~]#

（三）在网页上配置nginx模板的相关监控

1，登陆zabbix界面，依次点击：配置（configuration）---模板（template）---导入（import）

2,给主机添加模板：选择主机---nginx服务器主机---模板---选择（刚刚导入的nginx性能状态的模板）---添加---更新

3，查看nginx监控的最新数据：监控中---图形---选择相应的监控类型。

备注：

Active ：当前活跃的链接数。

Accepts: 接受的请求数

Handled: 处理的请求数（正常服务器响应，这两项应该是能够相等的）

Requests: 客户端处理的请求数。（吞吐量）

Reading: 当接收到请求时，链接离开 Waiting 状态，而且该请求自己使 Reading 状态计数增长。在这种状态下 NGINX 会读取客户端请求首部。请求首部是比较小的，所以这一般是一个快速的操做。

Writing: 请求被读取以后，其使 Writing 状态计数增长，并保持在该状态，直到响应返回给客户端。这意味着，该请求在 Writing 状态时，一方面 NGINX 等待来自上游系统的结果（系统放在 NGINX “后面”），另一方面，NGINX 也在同时响应。请求每每会在 Writing 状态花费大量的时间。

Waiting: 活跃的链接也能够处于 Waiting 子状态，若是有在此刻没有活跃请求的话。新链接能够绕过这个状态并直接变为到 Reading 状态，最多见的是在使用“accept filter（接受过滤器）” 和 “deferred accept（延迟接受）”时，在这种状况下，NGINX 不会接收 worker 进程的通知，直到它具备足够的数据才开始响应。若是链接设置为 keep-alive ，那么它在发送响应后将处于等待状态

附nginx.xml

<?xml version="1.0" encoding="UTF-8"?>

<zabbix_export>

<group>

<name>Templates</name>

</group>

</groups>

<template>Template_Nginx</template>

<name>Template_Nginx</name>

<group>

<name>Templates</name>

</group>

</groups>

<name>Nginx</name>

</application>

</applications>

<items>

<item>

<name>Nginx $1</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[waiting,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[writing,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[active_connections,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[reading,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1/sec</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[handled_requests,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1/sec</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[accepted_connections,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Nginx $1/sec</name>

<snmp_community/>

<snmp_oid/>

<key>nginx[handled_connections,{$NGINX_STATUS_URL}]</key>

<value_type>0</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

<name>Nginx</name>

</application>

</applications>

</item>

<item>

<name>Number of $1 process</name>

<snmp_community>public</snmp_community>

<snmp_oid>interfaces.ifTable.ifEntry.ifInOctets.1</snmp_oid>

<key>proc.num[nginx]</key>

<value_type>3</value_type>

<allowed_hosts/>

<snmpv3_securityname/>

<snmpv3_securitylevel>0</snmpv3_securitylevel>

<snmpv3_authpassphrase/>

<snmpv3_privpassphrase/>

<delay_flex/>

<ipmi_sensor/>

<data_type>0</data_type>

<port/>

<inventory_link>0</inventory_link>

</item>

</items>

<discovery_rules/>

<macro>

<macro>{$NGINX_STATUS_URL}</macro>

<value>http://127.0.0.1:10061/nginx_status</value>

</macro>

</macros>

</template>

</templates>

<expression>{Template_Nginx:proc.num[nginx].last(0)}=0</expression>

<name>Nginx is not running on {HOSTNAME}</name>

<url/>

<description>Nginx is not running.

It has been stopped / shutdown or has crashed. 

Check on the server for more details:

- w / last

- dmesg logs

- /var/log/messages

- nginx error logs</description>

</trigger>

</triggers>

<graph>

<name>Nginx - Connections and Requests status</name>

<show_work_period>0</show_work_period>

<show_triggers>0</show_triggers>

<show_legend>1</show_legend>

<show_3d>0</show_3d>

<percent_left>0.0000</percent_left>

<percent_right>0.0000</percent_right>

<ymin_type_1>1</ymin_type_1>

<ymax_type_1>0</ymax_type_1>

<ymin_item_1>0</ymin_item_1>

<ymax_item_1>0</ymax_item_1>

<graph_items>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[accepted_connections,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[handled_connections,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[handled_requests,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

</graph_items>

</graph>

<graph>

<name>Nginx - Threads status</name>

<show_work_period>0</show_work_period>

<show_triggers>0</show_triggers>

<show_legend>1</show_legend>

<show_3d>0</show_3d>

<percent_left>0.0000</percent_left>

<percent_right>0.0000</percent_right>

<ymin_type_1>1</ymin_type_1>

<ymax_type_1>0</ymax_type_1>

<ymin_item_1>0</ymin_item_1>

<ymax_item_1>0</ymax_item_1>

<graph_items>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[writing,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[reading,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

<graph_item>

<calc_fnc>4</calc_fnc>

<item>

<host>Template_Nginx</host>

<key>nginx[waiting,{$NGINX_STATUS_URL}]</key>

</item>

</graph_item>

</graph_items>

</graph>

</graphs>

</zabbix_export>