ZabbixManual1.4/Glossary/zh

翻译人员:

FireHare

{{#ifexist: :ZabbixManual1.4/Glossary/zh/zh | | {{#ifexist: ZabbixManual1.4/Glossary/zh/zh | | {{#ifeq: {{#titleparts:ZabbixManual1.4/Glossary/zh|1|-1|}} | zh | | }} }} }} {{#ifeq: {{#titleparts:ZabbixManual1.4/Glossary/zh|1|-1|}} | zh | | }}

---

Active（主动模式）

Active（主动模式）指的是 Zabbix 代理运行的一种模式。当进入该模式时，代理可以掌握在什么时间间隔向服务器发送了什么内容。代理可以在设定的时间间隔中询问服务器以掌握向服务器发送了什么内容。

Active checker（主动探测器）

Active checker（主动探测器） 可以从 Zabbix 代理所在的系统中收集操作信息，并将其数据报告给 Zabbix 以便进一步处理。

Action（动作）

Action（动作）是当触发器被触发时所产生的回应。Action（动作）可以被配置为向在 Zabbix 中定义的特定用户组发送基于它们媒体类型设置的消息，或运行远程命令。

Agent（代理）

Agent（代理） 指的是运行在被监控主机上的程序。它作为一个服务运行并且可以同时处理主动和被动地检测。

Alerter（报警器）

Alerter（报警器）是一个为负责执行动作（如Email、Jabber、SMS和脚本等）的服务器进程。

Auto-registration（自动注册）

Auto-registration（自动注册）指的是 Zabbix 的一个功能，它允许主机可以自动把自己注册到 Zabbix 服务器上。这需要管理员通过在 Web 界面上来进行配置，定义一个特殊的主机名如“*-Linux”并为基于监测项模板的主机定义监测项。

Auto-discovery（自动发现）

Zabbix 的自动发现模块可以自动发现主机和服务并为进一步处理生成事件。

Event（事件）

事件是触发器被触发时产生的

Graphs（图表）

Graphs （图表）可以是指每监测项数据的简单图表，或也可以是指在一个图表中显示几个监测项数据的自定议图表

Host（主机）

Host（主机）是指被监视的机器。

Housekeeper（管理器）

Housekeeper（管理器）是指 Zabbix 服务器中的服务，用于消除 Zabbix 中用户定义的过时动作、事件、历史和趋势数据的数据库。动作和事件的管理在通用设置中定义，历史和趋势数据在每个监测项中定义。

IT Services（IT 服务）

IT Services（IT 服务） 是指 Zabbix 的一个功能，它允许用户定义 SLA（服务等级协议），并使 Zabbix 记录预计 SLA 和实际 SLA。IT 服务被作为触发器组来定义的，并且可以配置组的最大值和最小值。

Item（监测项）

Item（监测项） 是指在主机上被监测的单个项目，如平均负载或响应时间等。监测项可以指通过 Zabbix 代理、SNMP或其他程序所获取的项目。监测项可以配置成浮点数、64位整数、字符串或日志值。

Location（定位）

由单一节点监测的环境

Map（图）

Map（图）指的是 Zabbix 的一项功能，它允许用户通过 web 界面创建自定义图形，以便在图中创建网络图并定义主机间的链接。链接可以配置成基于触发器改变颜色和风格。

Master or Master Node（主节点）

Master Node（主节点）. Master Node（主节点） 可以有一个或多个从节点。主节点可以控制从节点的配置。

Media Type（媒体类型）

Media Types（媒体类型）在动作发生时用来提醒 Zabbix 用户注意。媒体类型可以通过邮件或自定义脚本。媒体类型先进行对所有用户生效的全局配置，然后再针对每个用户进行特定配置，以便可以通过一种媒体类型来提醒特定用户注意。

Node（节点）

ZABBIX Server in distributed setup monitoring number of hosts.

Node ID（节点 ID）

Node ID（节点 ID）是标识节点的唯一号。每个节点都必须有它自己唯一的节点号。

Node Watcher（节点观测器）

负责节点间通信的 Zabbix 服务器进程。

Queue

Queue refers to the internal queue of items the ZABBIX server is monitoring. Based on the specified intervals of items the ZABBIX server maintains a queue to keep track of the items and when it should poll them.

Passive

Passive refers to a mode that the ZABBIX Agent can run in. When running passively, the agent waits for requests for items from the server and sends them back as requested. It should be noted that typically the agent runs in both modes, and the modes are defined by the Item when it is configured.

Pinger

ZABBIX Server process which processes ICMP pings.

Poller

ZABBIX Server process which is responsible for retrieval of data from ZABBIX and SNMP agents and processing remote (simple) checks.

ROI

Return on Investment.

Screen

Screen refers to another customizable feature of ZABBIX which allows users to create custom pages within ZABBIX for displaying information. A screen can consist of graphs (custom), simple graphs, maps, or plain text such as the last 5 values of a particular item.

Sender

ZABBIX utility which sends data to ZABBIX Server for further processing. It usually used in user scripts.

Server

Server refers to the program that is run on a centralized machine that has been deemed the “monitoring station”. The server is run as a service and is in charge of keeping track of all the configured hosts, items, actions, alerts, etc.

SLA

SLA refers to Service Level Agreement. These are typically used in contracts between companies and clients in order to define a certain level of service such as 99.5% availability of a particular Host.

Slave or Slave Node

Slave Node is linked to a Master Node. Slave Nodes reports to Master Node.

Template

A Template is a Host that has a defined set of Items, Triggers, etc. which Hosts can be linked to. This allows easier configuration of hosts and changes to hosts without having to change each individual host. Host Templates are no different from other hosts except that their status is set to ‘Template’ during configuration and as such no Host is actually monitored.

Timer

ZABBIX Server process responsible for processing of date and time related functions of trigger expressions.

Trapper

ZABBIX Server process responsible for processing of ZABBIX Agent (active) checks, log files and data sent by sender.

Trigger

A trigger is used to define constraints on items and provide notifications when these constraints are exceeded. For example, you could be monitoring load average on a specific host and want to know when load average exceeds 1.0. Triggers are very flexible and can allow for multiple constraints.

User

The ZABBIX web front-end can be configured to allow access to multiple users at varying levels of access. Users can be allowed anonymous access via the guest account and be allowed to view all available data but not modify any changes, or users can be given access to only view or modify specific sections of ZABBIX.

User parameter

User Parameter (UserParameter) refers to custom scripts defined in an agent’s configuration file. User parameters are defined by a key and command. The key refers to the item defined in the web interface and can be configured to accept arguments as sent by the server.

ZABBIX

ZABBIX Software

ZABBIX SIA

Latvian company that develops and provides support for ZABBIX.