的zabbix psql的主动监测，不支持

Question

我在主动模式和psql监测的zabbix代理未working.It不支持，我不知道这意味着什么......

的zabbix服务器消息：

代理日志文件：

36170:20170103:023837.264 Starting Zabbix Agent [xxxxx]. Zabbix 2.2.7 (revision 50148). 
36170:20170103:023837.264 using configuration file: /etc/zabbix/zabbix_agentd.conf 
36170:20170103:023837.270 Starting agent module libzbxpgsql 1.0.0 
36170:20170103:023837.271 loaded modules: libzbxpgsql.so 
36171:20170103:023837.271 agent #0 started [collector] 
36172:20170103:023837.272 agent #1 started [listener #1] 
36173:20170103:023837.272 agent #2 started [listener #2] 
36174:20170103:023837.273 agent #3 started [listener #3] 
36175:20170103:023837.273 agent #4 started [active checks #1] 

36175:20170103:024841.219 active check "psql.active_connections[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.219 active check "psql.buffers_alloc[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.219 active check "psql.buffers_backend[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.219 active check "psql.buffers_backend_fsync[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.219 active check "psql.buffers_checkpoint[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.buffers_clean[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.checkpoints_req[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.checkpoints_timed[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.tx_commited[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.server_connections[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.idle_connections[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.idle_tx_connections[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.220 active check "psql.locks_waiting[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.221 active check "psql.server_maxcon[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.221 active check "psql.maxwritten_clean[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.221 active check "psql.running[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.221 active check "psql.tx_rolledback[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
36175:20170103:024841.221 active check "psql.slow_dml_queries[127.0.0.1,5432,postgres,raban_wiw,10]" is not supported 
36175:20170103:024841.221 active check "psql.slow_queries[127.0.0.1,5432,postgres,raban_wiw,10]" is not supported 
36175:20170103:024841.221 active check "psql.slow_select_queries[127.0.0.1,5432,postgres,raban_wiw,10]" is not supported 

配置文件：

# This is a config file for the Zabbix agent daemon (Unix) 
# To get more information about Zabbix, visit http://www.zabbix.com 

############ GENERAL PARAMETERS ################# 

### Option: PidFile 
# Name of PID file. 
# 
# Mandatory: no 
# Default: 
# PidFile=/tmp/zabbix_agentd.pid 

PidFile=/var/run/zabbix/zabbix_agentd.pid 

### Option: LogFile 
# Name of log file. 
# If not set, syslog is used. 
# 
# Mandatory: no 
# Default: 
# LogFile= 

LogFile=/var/log/zabbix-agent/zabbix_agentd.log 

### Option: LogFileSize 
# Maximum size of log file in MB. 
# 0 - disable automatic log rotation. 
# 
# Mandatory: no 
# Range: 0-1024 
# Default: 
# LogFileSize=1 

LogFileSize=0 

### Option: DebugLevel 
# Specifies debug level 
# 0 - no debug 
# 1 - critical information 
# 2 - error information 
# 3 - warnings 
# 4 - for debugging (produces lots of information) 
# 
# Mandatory: no 
# Range: 0-4 
# Default: 
# DebugLevel=3 

### Option: SourceIP 
# Source IP address for outgoing connections. 
# 
# Mandatory: no 
# Default: 
# SourceIP= 

### Option: EnableRemoteCommands 
# Whether remote commands from Zabbix server are allowed. 
# 0 - not allowed 
# 1 - allowed 
# 
# Mandatory: no 
# Default: 
# EnableRemoteCommands=0 

### Option: LogRemoteCommands 
# Enable logging of executed shell commands as warnings. 
# 0 - disabled 
# 1 - enabled 
# 
# Mandatory: no 
# Default: 
# LogRemoteCommands=0 

##### Passive checks related 

### Option: Server 
# List of comma delimited IP addresses (or hostnames) of Zabbix servers. 
# Incoming connections will be accepted only from the hosts listed here. 
# If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally. 
# 
# Mandatory: no 
# Default: 
# Server= 

Server=127.0.0.1,88.198.52.25 

### Option: ListenPort 
# Agent will listen on this port for connections from the server. 
# 
# Mandatory: no 
# Range: 1024-32767 
# Default: 
# ListenPort=10050 

### Option: ListenIP 
# List of comma delimited IP addresses that the agent should listen on. 
# First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks. 
# 
# Mandatory: no 
# Default: 
# ListenIP=0.0.0.0 

### Option: StartAgents 
# Number of pre-forked instances of zabbix_agentd that process passive checks. 
# If set to 0, disables passive checks and the agent will not listen on any TCP port. 
# 
# Mandatory: no 
# Range: 0-100 
# Default: 
# StartAgents=3 

##### Active checks related 

### Option: ServerActive 
# List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks. 
# If port is not specified, default port is used. 
# IPv6 addresses must be enclosed in square brackets if port for that host is specified. 
# If port is not specified, square brackets for IPv6 addresses are optional. 
# If this parameter is not specified, active checks are disabled. 
# Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1] 
# 
# Mandatory: no 
# Default: 
# ServerActive= 

ServerActive=88.198.52.25 

### Option: Hostname 
# Unique, case sensitive hostname. 
# Required for active checks and must match hostname as configured on the server. 
# Value is acquired from HostnameItem if undefined. 
# 
# Mandatory: no 
# Default: 
# Hostname= 

Hostname=system.wroc.wiw.gov.pl 

### Option: HostnameItem 
# Item used for generating Hostname if it is undefined. Ignored if Hostname is defined. 
# Does not support UserParameters or aliases. 
# 
# Mandatory: no 
# Default: 
# HostnameItem=system.hostname 

### Option: HostMetadata 
# Optional parameter that defines host metadata. 
# Host metadata is used at host auto-registration process. 
# An agent will issue an error and not start if the value is over limit of 255 characters. 
# If not defined, value will be acquired from HostMetadataItem. 
# 
# Mandatory: no 
# Range: 0-255 characters 
# Default: 
# HostMetadata= 

### Option: HostMetadataItem 
# Optional parameter that defines an item used for getting host metadata. 
# Host metadata is used at host auto-registration process. 
# During an auto-registration request an agent will log a warning message if 
# the value returned by specified item is over limit of 255 characters. 
# This option is only used when HostMetadata is not defined. 
# 
# Mandatory: no 
# Default: 
# HostMetadataItem= 

### Option: RefreshActiveChecks 
# How often list of active checks is refreshed, in seconds. 
# 
# Mandatory: no 
# Range: 60-3600 
# Default: 
# RefreshActiveChecks=120 

### Option: BufferSend 
# Do not keep data longer than N seconds in buffer. 
# 
# Mandatory: no 
# Range: 1-3600 
# Default: 
# BufferSend=5 

### Option: BufferSize 
# Maximum number of values in a memory buffer. The agent will send 
# all collected data to Zabbix Server or Proxy if the buffer is full. 
# 
# Mandatory: no 
# Range: 2-65535 
# Default: 
# BufferSize=100 

### Option: MaxLinesPerSecond 
# Maximum number of new lines the agent will send per second to Zabbix Server 
# or Proxy processing 'log' and 'logrt' active checks. 
# The provided value will be overridden by the parameter 'maxlines', 
# provided in 'log' or 'logrt' item keys. 
# 
# Mandatory: no 
# Range: 1-1000 
# Default: 
# MaxLinesPerSecond=100 

############ ADVANCED PARAMETERS ################# 

### Option: Alias 
# Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one. 
# Multiple Alias parameters may be present. Multiple parameters with the same Alias key are not allowed. 
# Different Alias keys may reference the same item key. 
# For example, to retrieve the ID of user 'zabbix': 
# Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,^zabbix:.:([0-9]+),,,,\1] 
# Now shorthand key zabbix.userid may be used to retrieve data. 
# Aliases can be used in HostMetadataItem but not in HostnameItem parameters. 
# 
# Mandatory: no 
# Range: 
# Default: 

### Option: Timeout 
# Spend no more than Timeout seconds on processing 
# 
# Mandatory: no 
# Range: 1-30 
# Default: 
# Timeout=3 

### Option: AllowRoot 
# Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent 
# will try to switch to user 'zabbix' instead. Has no effect if started under a regular user. 
# 0 - do not allow 
# 1 - allow 
# 
# Mandatory: no 
# Default: 
# AllowRoot=0 

### Option: Include 
# You may include individual files or all files in a directory in the configuration file. 
# Installing Zabbix will create include directory in /etc/zabbix, unless modified during the compile time. 
# 
# Mandatory: no 
# Default: 
# Include= 

# Include=/etc/zabbix/zabbix_agentd.userparams.conf 
# Include=/etc/zabbix/zabbix_agentd.conf.d/ 
Include=/etc/zabbix/zabbix_agentd.conf.d/ 

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

### Option: UnsafeUserParameters 
# Allow all characters to be passed in arguments to user-defined parameters. 
# 0 - do not allow 
# 1 - allow 
# 
# Mandatory: no 
# Range: 0-1 
# Default: 
# UnsafeUserParameters=0 

### 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= 

####### LOADABLE MODULES ####### 

### Option: LoadModulePath 
# Full path to location of agent modules. 
# Default depends on compilation options. 
# 
# Mandatory: no 
# Default: 
# LoadModulePath=${libdir}/modules 

### Option: LoadModule 
# Module to load at agent startup. Modules are used to extend functionality of the agent. 
# Format: LoadModule=<module.so> 
# The modules must be located in directory specified by LoadModulePath. 
# It is allowed to include multiple LoadModule parameters. 
# 
# Mandatory: no 
# Default: 
LoadModule=libzbxpgsql.so 

详细日志：

129967: 45220:20170103:125411.785 active check "psql.checkpoints_req[127.0.0.1,5432,postgres,raban_wiw]" is not supported 
129968: 45220:20170103:125411.785 for key [psql.checkpoints_timed[127.0.0.1,5432,postgres,raban_wiw]] received value [ZBX_NOTSUPPORTED] 
129969: 45220:20170103:125411.785 In process_value() key:'system.wroc.wiw.gov.pl:psql.checkpoints_timed[{$PGHOST},{$PGPORT},{$PGROLE},{$PGDATABASE}]' value:'ZBX_NOTSUPPORTED' 

Answer 1

看起来像你的代理人未配置有任何所需要的那些项目项工作，除非你有他们在某些包含文件的psql.* userparameters的。

您应该从获得此模板的相同位置获取用户参数配置。看起来你已经从相关主机中取消了链接模板 - 这可能不是一个好主意，更好地保持模板链接。

并考虑在官方手册中阅读关于Zabbix userparameters的信息，它应该更清楚地说明这应该如何工作。

有人建议libzbxpgsqlloadable module应该提供这些项目密钥。如果是这样，将代理DebugLevel参数设置为4并检查更有用的错误消息可能会有所帮助，但这可能是您已经提供的“详细日志”。如果是这样，请仔细检查Zabbix用户（或代理运行的那个用户）是否可以使用“postgres”角色连接到127.0.0.1:5432上的PostgreSQL。

注意，template，应该与可加载模块一起使用，具有完全不同的项键 - 你有psql.开始，而那些模板与pg.开始。最简单的方法可能是放弃以前的所有配置并重新安装最新版本的模块和模板。

Answer 2

尝试增加代理日志级别，然后重新检查代理日志。可能是PSQL权限问题。另外我建议升级你的代理。然后，您可能会在Zabbix UI中看到错误消息，而不是ZBX_UNSUPPORTED。