en	# 2 Definitions
zh-cn	# 2. 定义

en	#### Overview In this section you can learn the meaning of some terms commonly used in Zabbix.
zh-cn	#### 概述 在本章节中，您可以了解 Zabbix 中一些常用术语的含义。

en	#### Definitions ***[host](/manual/config/hosts)*** \- *any physical or virtual device, application, service, or any other logically-related collection of monitored parameters.* ***[host group](/manual/config/hosts)*** \- *a logical grouping of hosts. Host groups are used when assigning access rights to hosts for different user groups.* ***[item](/manual/config/items)*** \- *a particular piece of data that you want to receive from a host, a metric of data.* ***[value preprocessing](/manual/config/items/item#item_value_preprocessing)*** \- *a transformation of received metric value* before saving it to the database. ***[trigger](/manual/config/triggers)*** \- *a logical expression that defines a problem threshold and is used to "evaluate" data received in items.* When received data are above the threshold, triggers go from 'Ok' into a 'Problem' state. When received data are below the threshold, triggers stay in/return to an 'Ok' state. ***[template](/manual/config/templates)*** \- *a set of entities (items, triggers, graphs, low-level discovery rules, web scenarios) ready to be applied to one or several hosts.* The job of templates is to speed up the deployment of monitoring tasks on a host; also to make it easier to apply mass changes to monitoring tasks. Templates are linked directly to individual hosts. ***[template group](/manual/config/templates)*** \- *a logical grouping of templates. Template groups are used when assigning access rights to templates for different user groups.* ***[event](/manual/config/events)*** \- *a single occurrence of something that deserves attention such as a trigger changing state or a discovery/agent autoregistration taking place.* ***[event tag](/manual/config/tagging)*** \- *a pre-defined marker for the event.* It may be used in event correlation, permission granulation, etc. ***[event correlation](/manual/config/event_correlation)*** \- *a method of correlating problems to their resolution flexibly and precisely.* For example, you may define that a problem reported by one trigger may be resolved by another trigger, which may even use a different data collection method. ***[problem](/manual/web_interface/frontend_sections/monitoring/problems)*** \- *a trigger that is in "Problem" state.* ***[problem update](/manual/acknowledgment#updating_problems)*** \- *problem management options provided by Zabbix, such as adding comment, acknowledging, changing severity or closing manually.* ***[action](/manual/config/notifications/action)*** \- *a predefined means of reacting to an event.* An action consists of operations (e.g. sending a notification) and conditions (*when* the operation is carried out) ***[escalation](/manual/config/notifications/action/escalations)*** \- *a custom scenario for executing operations within an action; a sequence of sending notifications/executing remote commands.* ***[media](/manual/config/notifications/media)*** \- *a means of delivering notifications; delivery channel.* ***[notification](/manual/config/notifications/action/operation/message)*** \- *a message about some event sent to a user via the chosen media channel.* ***[remote command](/manual/config/notifications/action/operation/remote_command)*** \- *a pre-defined command that is automatically executed on a monitored host upon some condition.* ***[web scenario](/manual/web_monitoring)*** \- *one or several HTTP requests to check the availability of a web site.* ***[frontend](/manual/introduction/overview#architecture)*** \- *the web interface provided with Zabbix.* ***[dashboard](/manual/web_interface/frontend_sections/dashboards)*** \- *customizable section of the web interface displaying summaries and visualizations* of important information in visual units called widgets. ***[widget](/manual/web_interface/frontend_sections/dashboards/widgets)*** \- *visual unit displaying information of a certain kind and source* (a summary, a map, a graph, the clock, etc.), used in the dashboard. ***[Zabbix API](/manual/api)*** \- *Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any other custom tasks.* ***[Zabbix server](/manual/concepts/server)*** \- *a central process of Zabbix software that performs monitoring, interacts with Zabbix proxies and agents, calculates triggers, sends notifications; a central repository of data.* ***[Zabbix proxy](/manual/concepts/proxy)*** \- *a process that may collect data on behalf of Zabbix server, taking some processing load from the server.* ***[Zabbix agent](/manual/concepts/agent)*** \- *a process deployed on monitoring targets to actively monitor local resources and applications.* ***[Zabbix agent 2](/manual/concepts/agent2)*** \- *a new generation of Zabbix agent to actively monitor local resources and applications, allowing to use custom plugins for monitoring.* ::: noteimportant Because Zabbix agent 2 shares much functionality with Zabbix agent, the term "Zabbix agent" in documentation stands for both - Zabbix agent and Zabbix agent 2, if the functional behavior is the same. Zabbix agent 2 is only specifically named where its functionality differs. ::: ***[encryption](/manual/encryption)*** \- *support of encrypted communications between Zabbix components (server, proxy, agent, zabbix\_sender and zabbix\_get utilities)* using Transport Layer Security (TLS) protocol. ***[agent autoregistration](/manual/discovery/auto_registration)*** \- *automated process whereby a Zabbix agent itself is registered* as a host and started to monitor. ***[network discovery](/manual/discovery/network_discovery)*** \- *automated discovery of network devices*. ***[low-level discovery](/manual/discovery/low_level_discovery)*** \- *automated discovery of low-level entities on a particular device* (e.g. file systems, network interfaces, etc). ***[low-level discovery rule](/manual/discovery/low_level_discovery#discovery_rule)*** \- *set of definitions for automated discovery of low-level entities* on a device. ***[item prototype](/manual/discovery/low_level_discovery#item_prototypes)*** \- *a metric with certain parameters as variables, ready for low-level discovery*. After low-level discovery the variables are automatically substituted with the real discovered parameters and the metric automatically starts gathering data. ***[trigger prototype](/manual/discovery/low_level_discovery#trigger_prototypes)*** \- *a trigger with certain parameters as variables, ready for low-level discovery*. After low-level discovery the variables are automatically substituted with the real discovered parameters and the trigger automatically starts evaluating data. *Prototypes* of some other Zabbix entities are also in use in low-level discovery - graph prototypes, host prototypes, host group prototypes.
zh-cn	#### 定义 ***[host（主机）](/manual/config/hosts)*** \- *任何物理或虚拟设备、应用程序、服务或任何其他逻辑相关的监控对象的集合。* ***[host group（主机组）](/manual/config/hosts)*** \- *主机的逻辑分组。在为不同用户组分配主机访问权限时使用主机组。 * ***[item（监控项）](/manual/config/items)*** \- *你想要接收的主机的特定数据，一个度量/指标数据。* ***[value preprocessing（值预处理）](/manual/config/items/item#监控项值预处理)*** \- 在数据存入数据库之前 *对接收到的监控项进行预处理转换。* ***[trigger（触发器）](/manual/config/triggers)*** \- *一个被用于定义问题阈值和 "评估" 监控项接收到的数据的逻辑表达式。* 当接收到的数据高于阈值时，触发器从 'Ok' 变成 'Problem' 状态。当接收到的数据低于阈值时，触发器保留/返回 'Ok' 的状态。 ***[template（模板）](/manual/config/templates)*** \- *可以应用于一个或多个主机的一组实体集 （包含监控项、触发器、图表、低级别自动发现规则、web场景等）。* 模版的应用使得主机上的监控任务部署快捷方便；也可以使监控任务的批量修改更加简单。模版是直接关联到每台单独的主机上。 ***[template group（模板组）](/manual/config/templates)*** \- *模板的逻辑分组。在为不同用户组分配模板的访问权限时使用。* ***[event（事件）](/manual/config/events)*** \- *一次发生的需要注意的事情，例如 触发器状态改变、自动发现/agent 自动注册。* ***[event tag（事件标签）](/manual/config/event_correlation/trigger/event_tags)*** \- *预设的事件标记* 可以被用于事件关联，权限细化设置等。 ***[event correlation（事件关联）](/manual/config/event_correlation)*** \- *一种灵活而精确地将问题与其解决方法联系起来的方法* 比如说，你可以定义触发器A告警的异常可以由触发器B解决，触发器B可能采用完全不同的数据采集方式。 ***[problem（问题）](/manual/web_interface/frontend_sections/monitoring/problems)*** \- *一个处在 "问题" 状态的触发器。* ***[problem update（问题更新）](/manual/acknowledges#更新问题)*** \- *Zabbix 提供的问题管理选项，例如添加评论、确认、更改严重性或手动关闭。* ***[action（动作）](/manual/config/notifications/action)*** \- *对事件作出反应的预先定义的方法。* 一个动作由多个操作（例如发送通知)）和条件（*什么情况下* 执行操作）组成。 ***[escalation（升级）](/manual/config/notifications/action/escalations)*** \- *用于在动作中执行操作的自定义场景；发送通知/执行远程命令的序列。* ***[media（媒体）](/manual/config/notifications/media)*** \- *发送告警通知的渠道；传输媒介。* ***[notification（通知）](/manual/config/notifications/action/operation/message)*** \- *通过选定的媒体通道发送给用户的关于某个事件的消息。* ***[remote command（远程命令）](/manual/config/notifications/action/operation/remote_command)*** \- *在某些条件下自动在被监控主机上执行的预定义命令。* ***[web scenario（web 场景）](/manual/web_monitoring)*** \- *检查一个网站的可用性的一个或多个HTTP请求。* ***[frontend（前端）](/manual/introduction/overview#结构体系)*** \- *Zabbix的web界面。* ***[dashboard（仪表盘）](/manual/web_interface/frontend_sections/monitoring/dashboard)*** \- *web界面的可定制部分，以可视化的单元（又叫小部件）显示重要信息的摘要和可视化。* ***[widget（小部件）](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets)*** \- *在仪表板中使用的显示某种类型和来源的信息*（摘要、地图、图表、时钟等）的可视化单元。 ***[Zabbix API](/manual/api)*** \- *Zabbix API 允许您使用 JSON RPC 协议来创建、更新和获取 Zabbix 对象（如主机、监控项、图表等）或执行任何其他自定义任务。* ***[Zabbix server](/manual/concepts/server)*** \- Zabbix 软件的中央进程，执行监控、与 Zabbix proxy 和 agent 交互、计算触发器、发送通知；数据的中央存储库。 ***[Zabbix proxy](/manual/concepts/proxy)*** \- *一个可以代表 Zabbix server 收集数据的进程，减轻 server 的一些处理负载。* ***[Zabbix agent](/manual/concepts/agent)*** \- *部署在被监控目标上以主动监控本地资源和应用程序的进程。* ***[Zabbix agent 2](/manual/concepts/agent2)*** \- *新一代 Zabbix agent，主动监控本地资源和应用程序，允许使用自定义插件进行监控。* ::: noteimportant 因为 Zabbix agent 2 与 Zabbix agent 共享许多功能，所以如果功能行为相同，文档中的术语 "Zabbix agent" 同时代表 Zabbix agent 和 Zabbix agent 2。Zabbix agent 2 仅在其功能不同的地方特别命名。 ::: ***[encryption（加密）](/manual/encryption)*** \- 使用传输层安全 (TLS) 协议 *支持Zabbix组件（server，proxy，agent，zabbix\_sender 和 zabbix\_get 实用程序）之间的加密通信 。* ***[agent autoregistration（agent 自动注册）](/manual/discovery/auto_registration)*** \- *Zabbix agent 自动注册为主机* 并开始监控的自动化过程。 ***[network discovery（网络发现）](/manual/discovery/network_discovery)*** \- *网络设备的自动发现。* ***[low-level discovery（低级别自动发现）](/manual/discovery/low_level_discovery)*** \- *自动发现特定设备上的底层实体*（例如：文件系统、网络接口等) ***[low-level discovery rule（低级别自动发现规则）](/manual/discovery/low_level_discovery#自动发现规则)*** \- *用于在设备上自动发现低级别实体的一组定义。* ***[item prototype（监控项原型）](/manual/discovery/low_level_discovery#监控项原型)*** \- *带有某些参数作为变量的度量，为低级别自动发现做好了准备。* 在低级别自动发现之后，变量被自动替换为实际发现的参数，度量标准自动开始收集数据。 ***[trigger prototype（触发器原型）](/manual/discovery/low_level_discovery#触发器原型)*** \- *以某些参数作为变量的触发器，为低级别自动发现做好准备。* 在低级别自动发现之后，变量被自动替换为实际发现的参数，触发器自动开始计算数据。 其他一些 Zabbix 实体的 *原型* 也在低级别自动发现中使用 - 图形原型、主机原型、主机组原型。