en-us	#### Item keys  The table provides details on the simple checks that can be used to monitor [VMware environments](/manual/vm_monitoring).  |Key|<|<|<|<| |-|------|--|------|------| |<|Description|Return value|Parameters|Comments| |vmware.cl.perfcounter\[<url>,<id>,<path>,<instance>\]|<|<|<|<| |<|VMware cluster performance counter metrics.|Integer|**url** - VMware service URL<br>**id** - VMware cluster ID<br>**path** - performance counter path<br>**instance** - performance counter instance|`id` can be received from vmware.cluster.discovery\[\] as {\#CLUSTER.ID}| |vmware.cluster.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware clusters.|JSON object|**url** - VMware service URL|<| |vmware.cluster.status\[<url>, <name>\]|<|<|<|<| |<|VMware cluster status.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**name** - VMware cluster name|<| |vmware.datastore.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware datastores.|JSON object|**url** - VMware service URL|<| |vmware.datastore.hv.list\[<url>,<datastore>\]|<|<|<|<| |<|List of datastore hypervisors.|JSON object|**url** - VMware service URL<br>**datastore** - datastore name|<| |vmware.datastore.read\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|Amount of time for a read operation from the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - latency (average value, default), maxlatency (maximum value)|<| |vmware.datastore.size\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore space in bytes or in percentage from total.|Integer - for bytes<br>Float - for percentage|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - possible values:<br>total (default), free, pfree (free, percentage), uncommitted|<| |vmware.datastore.write\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|Amount of time for a write operation to the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**datastore** - datastore name<br>**mode** - latency (average value, default), maxlatency (maximum value)|<| |vmware.dc.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware datacenters.|JSON object|**url** - VMware service URL|<| |vmware.eventlog\[<url>,<mode>\]|<|<|<|<| |<|VMware event log.|Log|**url** - VMware service URL<br>**mode** - *all* (default), *skip* - skip processing of older data|There must be only one vmware.eventlog\[\] item key per URL.<br><br>See also: [example of filtering](/manual/config/items/preprocessing/examples#filtering_vmware_event_log_records) VMware event log records.| |vmware.fullname\[<url>\]|<|<|<|<| |<|VMware service full name.|String|**url** - VMware service URL|<| |vmware.hv.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor cluster name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage as a percentage during the interval.|Float|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.cpu.utilization\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor usage as a percentage during the interval, depends on power management or HT.|Float|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor datacenter name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware hypervisor datastores.|JSON object|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.list\[<url>,<uuid>\]|<|<|<|<| |<|List of VMware hypervisor datastores.|JSON object|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.datastore.multipath\[<url>,<uuid>,<datastore>,<partitionid>\]|<|<|<|<| |<|Number of available datastore paths.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**partitionid** - internal ID of physical device from vmware.hv.datastore.discovery|<| |vmware.hv.datastore.read\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|Average amount of time for a read operation from the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - latency (default)|<| |vmware.hv.datastore.size\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore space in bytes or in percentage from total.|Integer - for bytes<br>Float - for percentage|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - possible values:<br>total (default), free, pfree (free, percentage), uncommitted|<| |vmware.hv.datastore.write\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|Average amount of time for a write operation to the datastore (milliseconds).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**datastore** - datastore name<br>**mode** - latency (default)|<| |vmware.hv.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware hypervisors.|JSON object|**url** - VMware service URL|<| |vmware.hv.fullname\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.freq\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor frequency (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor processor model.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of processor cores on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.cpu.threads\[<url>,<uuid>\]|<|<|<|<| |<|Number of processor threads on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.memory\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor total memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor model.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.uuid\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor BIOS UUID.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.hw.vendor\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor vendor name.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.maintenance\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor maintenance status.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|Returns '0' - not in maintenance or '1' - in maintenance| |vmware.hv.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor ballooned memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.memory.used\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor used memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.network.in\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor network input statistics (bytes per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**mode** - bps (default)|<| |vmware.hv.network.out\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor network output statistics (bytes per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**mode** - bps (default)|<| |vmware.hv.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware hypervisor performance counter value.|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**path** - performance counter path ^**[1](vmware_keys#footnotes)**^<br>**instance** - performance counter instance. Use empty instance for aggregate values (default)|<| |vmware.hv.power\[<url>,<uuid>,<max>\]|<|<|<|<| |<|VMware hypervisor power usage (W).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name<br>**max** - maximum allowed power usage|<| |vmware.hv.sensor.health.state\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor health state rollup sensor.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|The item might not work in the VMware vSphere 6.5 and newer, because VMware has deprecated the *VMware Rollup Health State* sensor. | |vmware.hv.sensors.get\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor HW vendor state sensors.|JSON|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.status\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor status.|Integer:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|Uses the host system overall status property.| |vmware.hv.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor uptime (seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.version\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor version.|String|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.hv.vm.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of virtual machines on VMware hypervisor.|Integer|**url** - VMware service URL<br>**uuid** - VMware hypervisor host name|<| |vmware.version\[<url>\]|<|<|<|<| |<|VMware service version.|String|**url** - VMware service URL|<| |vmware.vm.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.latency\[<url>,<uuid>\]|<|<|<|<| |<|Percentage of time the virtual machine is unable to run because it is contending for access to the physical CPU(s).|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|Number of processors on VMware virtual machine.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.readiness\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical CPU.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - CPU instance|<| |vmware.vm.cpu.ready\[<url>,<uuid>\]|<|<|<|<| |<|Time (in milliseconds) that the virtual machine was ready, but could not get scheduled to run on the physical CPU. CPU ready time is dependent on the number of virtual machines on the host and their CPU loads (%).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.swapwait\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Percentage of CPU time spent waiting for swap-in.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - CPU instance|<| |vmware.vm.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine processor usage (Hz).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine processor usage as a percentage during the interval.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine datacenter name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.discovery\[<url>\]|<|<|<|<| |<|Discovery of VMware virtual machines.|JSON object|**url** - VMware service URL|<| |vmware.vm.guest.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|Amount of guest physical memory that is swapped out to the swap space (KB).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.guest.osuptime\[<url>,<uuid>\]|<|<|<|<| |<|Total time elapsed since the last operating system boot-up (in seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.hv.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine hypervisor name.|String|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine total memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine ballooned memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.compressed\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine compressed memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.consumed\[<url>,<uuid>\]|<|<|<|<| |<|Amount of host physical memory consumed for backing up guest physical memory pages (KB).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.private\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine private memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.shared\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine shared memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine swapped memory size (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.usage.guest\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine guest memory usage (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.size.usage.host\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine host memory usage (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.memory.usage\[<url>,<uuid>\]|<|<|<|<| |<|Percentage of host physical memory that has been consumed.|Float|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.net.if.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine network interfaces.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.net.if.in\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine network interface input statistics (bytes/packets per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance<br>**mode** - bps (default)/pps - bytes/packets per second|<| |vmware.vm.net.if.out\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine network interface output statistics (bytes/packets per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance<br>**mode** - bps (default)/pps - bytes/packets per second|<| |vmware.vm.net.if.usage\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|VMware virtual machine network utilization (combined transmit-rates and receive-rates) during the interval (KBps).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - network interface instance|<| |vmware.vm.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware virtual machine performance counter value.|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**path** - performance counter path ^**[1](vmware_keys#footnotes)**^<br>**instance** - performance counter instance. Use empty instance for aggregate values (default)|<| |vmware.vm.powerstate\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine power state.|Integer:<br>0 - poweredOff;<br>1 - poweredOn;<br>2 - suspended|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.committed\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine committed storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.readoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Average number of outstanding read requests to the virtual disk during the collection interval.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.totalreadlatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|The average time a read from the virtual disk takes (milliseconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.totalwritelatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|The average time a write to the virtual disk takes (milliseconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.storage.uncommitted\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine uncommitted storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.unshared\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine unshared storage space (bytes).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.storage.writeoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|Average number of outstanding write requests to the virtual disk during the collection interval.|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance (mandatory)|<| |vmware.vm.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware virtual machine uptime (seconds).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.vfs.dev.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine disk devices.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|<| |vmware.vm.vfs.dev.read\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine disk device read statistics (bytes/operations per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.dev.write\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware virtual machine disk device write statistics (bytes/operations per second).|Integer ^**[2](vmware_keys#footnotes)**^|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**instance** - disk device instance<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.fs.discovery\[<url>,<uuid>\]|<|<|<|<| |<|Discovery of VMware virtual machine file systems.|JSON object|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name|VMware Tools must be installed on the guest virtual machine.| |vmware.vm.vfs.fs.size\[<url>,<uuid>,<fsname>,<mode>\]|<|<|<|<| |<|VMware virtual machine file system statistics (bytes/percentages).|Integer|**url** - VMware service URL<br>**uuid** - VMware virtual machine host name<br>**fsname** - file system name<br>**mode** - total/free/used/pfree/pused|VMware Tools must be installed on the guest virtual machine.|
zh-cn	#### 监控项键值  该表格提供了用于监控 [VMware 环境](/manual/vm_monitoring) 的简单检查的详细说明。  |键值|<|<|<|<| |---|-|-|-|-| |<|描述|返回值|参数|注释| |vmware.cl.perfcounter\[<url>,<id>,<path>,<instance>\]|<|<|<|<| |<|VMware 集群性能指标计数.|整型|**url** - VMware 服务 URL<br>**id** - VMware 集群 ID<br>**path** - 性能计数路径<br>**instance** - 性能计数实例|`id` 可以从 vmware.cluster.discovery\[\] 接收到的作为 {\#CLUSTER.ID}| |vmware.cluster.discovery\[<url>\]|<|<|<|<| |<|发现 VMware 集群.|JSON 对象|**url** - VMware 服务 URL|<| |vmware.cluster.status\[<url>, <name>\]|<|<|<|<| |<|VMware 集群状态.|整型:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware 服务 URL<br>**name** - VMware 集群名称|<| |vmware.datastore.discovery\[<url>\]|<|<|<|<| |<|发现 VMware datastore.|JSON 对象|**url** - VMware 服务 URL|<| |vmware.datastore.hv.list\[<url>,<datastore>\]|<|<|<|<| |<|Datastore hypervisors 列表.|JSON 对象|**url** - VMware 服务 URL<br>**datastore** - datastore 名称|<| |vmware.datastore.read\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|从 datastore 中读取操作的时间(单位是millisecond).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**datastore** - datastore 名称<br>**mode** - latency (默认是平均值), maxlatency (最大值)|<| |vmware.datastore.size\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore 存储空间单位是 byte 或者占总的百分比。|整型 - 单位 byte<br>浮点型 - 单位是百分比|**url** - VMware 服务 URL<br>**datastore** - datastore 名称<br>**mode** - 可能的值:<br>total (缺省值), free, pfree (空余的百分比), uncommitted|<| |vmware.datastore.write\[<url>,<datastore>,<mode>\]|<|<|<|<| |<|从 datastore 中写入操作的时间 (单位是millisecond).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**datastore** - datastore 名称<br>**mode** - latency (默认是平均值), maxlatency (最大值)|<| |vmware.dc.discovery\[<url>\]|<|<|<|<| |<|发现 VMware datacenters.|JSON 对象|**url** - VMware 服务 URL|<| |vmware.eventlog\[<url>,<mode>\]|<|<|<|<| |<|VMware 事件日志.|Log|**url** - VMware 服务 URL<br>**mode** - *all* (缺省值), *skip* - 跳过对旧数据的处理|这必须是一个 vmware.eventlog\[\] 每个 URL 监控项键值.<br><br>另请参考: [example of filtering](/manual/config/items/preprocessing/examples#filtering_vmware_event_log_records) VMware 事件日志记录.| |vmware.fullname\[<url>\]|<|<|<|<| |<|VMware 服务完整的名称.|字符串|**url** - VMware 服务 URL|<| |vmware.hv.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 集群名称.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor  CPU 使用 (Hz).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 在此间隔内的处理器使用百分比.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.cpu.utilization\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 在此间隔内的处理器使用百分比, 取决于电源管理或者 HT.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor datacenter 名称.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.datastore.discovery\[<url>,<uuid>\]|<|<|<|<| |<|发现 VMware hypervisor datastore.|JSON 对象|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.datastore.list\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor datastore 列表.|JSON 对象|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.datastore.multipath\[<url>,<uuid>,<datastore>,<partitionid>\]|<|<|<|<| |<|可用的datastore 路径数量.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**datastore** - datastore 名称<br>**partitionid** - 从  vmware.hv.datastore.discovery 发现的物理设备内部 ID|<| |vmware.hv.datastore.read\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|从 datastore 中读取操作的平均时间 (单位是 millisecond).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**datastore** - datastore 名称<br>**mode** - latency (缺省值)|<| |vmware.hv.datastore.size\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|VMware datastore 空间（单位是 byte） 或者占总体的百分比.|整型 - 单位 byte<br>浮点型 - 单位是百分比|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**datastore** - datastore名称<br>**mode** - 可能的值:<br>total (缺省值), free, pfree (空闲的百分比), uncommitted|<| |vmware.hv.datastore.write\[<url>,<uuid>,<datastore>,<mode>\]|<|<|<|<| |<|从 datastore 中写入操作的平均时间 (单位是 millisecond).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**datastore** - datastore 名称<br>**mode** - latency (缺省值)|<| |vmware.hv.discovery\[<url>\]|<|<|<|<| |<|发现 VMware hypervisors.|JSON 对象|**url** - VMware 服务 URL|<| |vmware.hv.fullname\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 名称.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.cpu.freq\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor CPU 频率 (Hz).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.cpu.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor  CPU model.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor CPU核数.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.cpu.threads\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor CPU 线程数.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.memory\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 总内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.model\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor model.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.uuid\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor BIOS UUID.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.hw.vendor\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 供应商名称.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.maintenance\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 维护状态.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|Returns '0' - 不在维护中 or '1' - 维护中| |vmware.hv.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 膨胀内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.memory.used\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 已用内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.network.in\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor 网络入方向统计数据 (byte/s).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**mode** - bps (缺省值)|<| |vmware.hv.network.out\[<url>,<uuid>,<mode>\]|<|<|<|<| |<|VMware hypervisor 网络出方向统计数据 (byte/s).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**mode** - bps (缺省值)|<| |vmware.hv.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware hypervisor 性能计数器的值.|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**path** - 性能计数路径 ^**[1](vmware_keys#footnotes)**^<br>**instance** - 性能计数实例. 默认情况下对聚合值使用空实例|<| |vmware.hv.power\[<url>,<uuid>,<max>\]|<|<|<|<| |<|VMware hypervisor 用电功率 (W).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称<br>**max** - 允许的最大用电功率|<| |vmware.hv.sensor.health.state\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 健康状态汇总传感器.|整型:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.sensors.get\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 硬件供应商状态传感器.|JSON|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.status\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 状态.|整型:<br>0 - gray;<br>1 - green;<br>2 - yellow;<br>3 - red|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|使用主机系统整体状态属性.| |vmware.hv.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 启动时间 (seconds).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.version\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor 版本.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.hv.vm.num\[<url>,<uuid>\]|<|<|<|<| |<|VMware hypervisor上的虚拟机数量.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware hypervisor 主机名称|<| |vmware.version\[<url>\]|<|<|<|<| |<|VMware 服务版本.|字符串|**url** - VMware 服务 URL|<| |vmware.vm.cluster.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机主机名.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.cpu.latency\[<url>,<uuid>\]|<|<|<|<| |<|由于争夺对物理 CPU 的访问，虚拟机无法运行的时间百分比).|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.cpu.num\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机的 CPU 数量.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.cpu.readiness\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|虚拟机已就绪，但无法调度到物理CPU上运行的时间百分比.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - CPU 实例|<| |vmware.vm.cpu.ready\[<url>,<uuid>\]|<|<|<|<| |<|虚拟机准备就绪，但无法调度到物理CPU上运行的时间(以毫秒为单位). CPU就绪时间取决于主机上的虚拟机数量及其CPU负载(%).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.cpu.swapwait\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|等待 swap-in 的CPU时间百分比.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - CPU 实例|<| |vmware.vm.cpu.usage\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 CPU 使用量 (Hz).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.cpu.usage.perf\[<url>,<uuid>\]|<|<|<|<| |<|VMware 在此间隔内虚拟机 CPU使用率的百分比.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.datacenter.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 datacenter 名称.|字符串 |**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.discovery\[<url>\]|<|<|<|<| |<|发现  VMware 虚拟机.|JSON 对象|**url** - VMware 服务 URL|<| |vmware.vm.guest.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|交换到交换空间的客户物理内存数量 (KB).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.guest.osuptime\[<url>,<uuid>\]|<|<|<|<| |<|自上次启动操作系统以来所经过的总时间 (单位second).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.hv.name\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 hypervisor 名称.|字符串|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机总内存 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.ballooned\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机膨胀内存 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.compressed\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机压缩内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.consumed\[<url>,<uuid>\]|<|<|<|<| |<|用于备份客户物理内存页面的主机物理内存使用量 (KB).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.private\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 private 内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.shared\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 shared 内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.swapped\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 swapped 内存大小 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.usage.guest\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 guest 内存使用量 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.size.usage.host\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机主机内存使用量 (bytes).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.memory.usage\[<url>,<uuid>\]|<|<|<|<| |<|主机物理内存消耗百分比.|浮点型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.net.if.discovery\[<url>,<uuid>\]|<|<|<|<| |<|发现 VMware 虚拟机网络接口.|JSON 对象|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.net.if.in\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware 虚拟机网络接口入方向统计数据 (bytes/packets per second).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 网络接口实例<br>**mode** - bps (缺省值)/pps - bytes/packets per second|<| |vmware.vm.net.if.out\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware 虚拟机网络接口出方向统计数据 (bytes/packets per second).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 网络接口实例<br>**mode** - bps (缺省值)/pps - bytes/packets per second|<| |vmware.vm.net.if.usage\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|VMware 两个间隔之间的虚拟机网络使用率 (综合发送速率和接收速率) (KBps).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 网络接口实例|<| |vmware.vm.perfcounter\[<url>,<uuid>,<path>,<instance>\]|<|<|<|<| |<|VMware 虚拟机性能计数器的值.|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**path** - 性能计数的路径 ^**[1](vmware_keys#footnotes)**^<br>**instance** - 性能计数的实例. 聚合值默认使用空实例|<| |vmware.vm.powerstate\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机电源状态.|整型:<br>0 - 电源关闭;<br>1 - 电源打开;<br>2 - 挂起中|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.storage.committed\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 committed 的存储空间(bytes).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.storage.readoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|在收集间隔内，对虚拟磁盘的平均未完成读请求数.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 磁盘设备实例(必选)|<| |vmware.vm.storage.totalreadlatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|从虚拟磁盘读取数据所需的平均时间 (millisecond).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 磁盘设备实例(必选)|<| |vmware.vm.storage.totalwritelatency\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|从虚拟磁盘写入数据所需的平均时间 (millisecond).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 磁盘设备实例(必选)|<| |vmware.vm.storage.uncommitted\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 uncommitted 存储空间 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.storage.unshared\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机 unshared 存储空间 (byte).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.storage.writeoio\[<url>,<uuid>,<instance>\]|<|<|<|<| |<|在采集间隔内，对虚拟磁盘未完成的写请求的平均次数.|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 磁盘设备实例(必选)|<| |vmware.vm.uptime\[<url>,<uuid>\]|<|<|<|<| |<|VMware 虚拟机启动时间 (second).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.vfs.dev.discovery\[<url>,<uuid>\]|<|<|<|<| |<|发现 VMware 虚拟机磁盘.|JSON 对象|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|<| |vmware.vm.vfs.dev.read\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware 虚拟机磁盘读取统计数据 (bytes/operations per second).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware virtual 虚拟机主机名<br>**instance** - 磁盘实例<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.dev.write\[<url>,<uuid>,<instance>,<mode>\]|<|<|<|<| |<|VMware 虚拟机磁盘写入统计数据 (bytes/operations per second).|整型 ^**[2](vmware_keys#footnotes)**^|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**instance** - 磁盘实例<br>**mode** - bps (default)/ops - bytes/operations per second|<| |vmware.vm.vfs.fs.discovery\[<url>,<uuid>\]|<|<|<|<| |<|发现 VMware 虚拟机文件系统.|JSON 对象|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名|客户虚拟机需要安装VMware Tools.| |vmware.vm.vfs.fs.size\[<url>,<uuid>,<fsname>,<mode>\]|<|<|<|<| |<|VMware 虚拟机文件系统统计数据 (bytes/percentages).|整型|**url** - VMware 服务 URL<br>**uuid** - VMware 虚拟机主机名<br>**fsname** - 文件系统名称<br>**mode** - total/free/used/pfree/pused|客户虚拟机需要安装VMware Tools.|

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      net.if.discovery  This item is supported since Zabbix agent 2.0.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      net.if.discovery  从Zabbix agent 2.0起支持使用此监控项。

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      system.cpu.discovery  This item is supported since Zabbix agent 2.4.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的监控项的键是      system.cpu.discovery  从Zabbix agent 2.4起支持此监控项。

en-us	#### Item key  The item key to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      vfs.dev.discovery  This item is supported on Linux platforms only, since Zabbix agent 4.4.  You may create discovery rules using this discovery item and:  -   filter: **{\#DEVNAME} matches `sd[\D]$`** - to discover devices     named "sd0", "sd1", "sd2", ... -   filter: **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match     `^loop.*`** - to discover disk type devices whose name does not     start with "loop"
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      vfs.dev.discovery  从Zabbix agent 4.4起支持此监控项, 仅限Linux平台。  可以使用此监控项和下列配置来创建自动发现规则：  -   过滤器: **{\#DEVNAME} matches `sd[\D]$`** - 发现名为 "sd0", "sd1", "sd2", ... 的设备 -   过滤器: **{\#DEVTYPE} matches `disk` AND {\#DEVNAME} does not match     `^loop.*`** - 发现硬盘类型不以 "loop" 开头的设备

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      perf_instance.discovery[object]  or, to be able to provide the object name in English only, independently of OS localization:      perf_instance_en.discovery[object]  For example:      perf_instance.discovery[Processador]     perf_instance_en.discovery[Processor]  These items are supported since Zabbix Windows agent 5.0.1.
zh-cn	#### 监控项的键  在 [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的监控项是      perf_instance.discovery[object]  或者可以提供对象名称，仅支持英文名称，此名称不受操作系统本地化设置控制:      perf_instance_en.discovery[object]  例如:      perf_instance.discovery[Processador]     perf_instance_en.discovery[Processor]  从Zabbix Windows agent 5.0.1起支持这些监控项.

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      service.discovery  This item is supported since Zabbix Windows agent 3.0.
zh-cn	#### 监控项的键  此监控项在[自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用的键是      service.discovery  从Zabbix Windows agent 3.0起支持此监控项。

en-us	### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the      systemd.unit.discovery  ::: noteimportant This [item](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) key is only supported in Zabbix agent 2. :::  This item returns a JSON with information about systemd units, for example:      [{         "{#UNIT.NAME}": "mysqld.service",         "{#UNIT.DESCRIPTION}": "MySQL Server",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": ""         "{#UNIT.JOBPATH}": "/",         "{#UNIT.UNITFILESTATE}": "enabled"     }, {         "{#UNIT.NAME}": "systemd-journald.socket",         "{#UNIT.DESCRIPTION}": "Journal Socket",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": "",         "{#UNIT.JOBPATH}": "/"         "{#UNIT.UNITFILESTATE}": "enabled"     }]
zh-cn	#### 监控项的键  在[自动发现规则](/manual/discovery/low_level_discovery#discovery_rule) 中使用这个监控项      systemd.unit.discovery  ::: noteimportant 此[监控项](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2) 的键只有Zabbix agent 2版本支持. :::  此监控项返回一个包含系统单元的JSON数据，如下所示:      [{         "{#UNIT.NAME}": "mysqld.service",         "{#UNIT.DESCRIPTION}": "MySQL Server",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/mysqld_2eservice",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": ""         "{#UNIT.JOBPATH}": "/",         "{#UNIT.UNITFILESTATE}": "enabled"     }, {         "{#UNIT.NAME}": "systemd-journald.socket",         "{#UNIT.DESCRIPTION}": "Journal Socket",         "{#UNIT.LOADSTATE}": "loaded",         "{#UNIT.ACTIVESTATE}": "active",         "{#UNIT.SUBSTATE}": "running",         "{#UNIT.FOLLOWED}": "",         "{#UNIT.PATH}": "/org/freedesktop/systemd1/unit/systemd_2djournald_2esocket",         "{#UNIT.JOBID}": 0,         "{#UNIT.JOBTYPE}": "",         "{#UNIT.JOBPATH}": "/"         "{#UNIT.UNITFILESTATE}": "enabled"     }]

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is the      zabbix[host,discovery,interfaces]  internal item. This item is supported since Zabbix server 3.4.  This item returns a JSON with the description of interfaces, including:  -   IP address/DNS hostname (depending on the “Connect to” host setting) -   Port number -   Interface type (Zabbix agent, SNMP, JMX, IPMI) -   If it is the default interface or not -   If the bulk request feature is enabled - for SNMP interfaces only.  For example:      [{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}]    With multiple interfaces their records in JSON are ordered by:  -   Interface type, -   Default - the default interface is put before non-default     interfaces, -   Interface ID (in ascending order).
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule)中使用的键是      zabbix[host,discovery,interfaces]  内部监控项。 从Zabbix server 3.4起支持此监控项。  此监控项返回一个JSON数组，包含以下关于接口的描述：  -   IP 地址/DNS 主机名(取决于 “连接到” 主机设置) -   端口号 -   接口类型 (Zabbix agent, SNMP, JMX, IPMI) -   是否是默认接口 -   批量请求(bulk request)特性是否启用 - 只适用于SNMP接口。  例如：      [{"{#IF.CONN}":"192.168.3.1","{#IF.IP}":"192.168.3.1","{#IF.DNS}":"","{#IF.PORT}":"10050","{#IF.TYPE}":"AGENT","{#IF.DEFAULT}":1}]    多个接口的JSON数据按以下规则排序：  -   接口类型, -   默认 - 默认接口在非默认接口前面, -   接口 ID (升序排列)。

en-us	#### Item key  The item to use in the [discovery rule](/manual/discovery/low_level_discovery#discovery_rule) is      wmi.getall[<namespace>,<query>]  This [item](/manual/config/items/itemtypes/zabbix_agent/win_keys) transforms the query result into a JSON array. For example:      select * from Win32_DiskDrive where Name like '%PHYSICALDRIVE%'  may return something like this:  ``` {.java} [     {         "DeviceID" : "\\.\PHYSICALDRIVE0",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 0,         "InterfaceType" : "IDE"     },     {         "DeviceID" : "\\.\PHYSICALDRIVE1",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 1,         "InterfaceType" : "IDE"     } ] ```  This item is supported since Zabbix Windows agent 4.4.
zh-cn	#### 监控项的键  [自动发现规则](/manual/discovery/low_level_discovery#discovery_rule)中使用的监控项是      wmi.getall[<命名空间>,<查询>]  此[监控项](/manual/config/items/itemtypes/zabbix_agent/win_keys) 将查询结果转换成一个JSON数组. 比如:      select * from Win32_DiskDrive where Name like '%PHYSICALDRIVE%'  会转换成下面的数据:  ``` {.java} [     {         "DeviceID" : "\\.\PHYSICALDRIVE0",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 0,         "InterfaceType" : "IDE"     },     {         "DeviceID" : "\\.\PHYSICALDRIVE1",         "BytesPerSector" : 512,         "Capabilities" : [             3,             4         ],         "CapabilityDescriptions" : [             "Random Access",             "Supports Writing"         ],         "Caption" : "VBOX HARDDISK ATA Device",         "ConfigManagerErrorCode" : "0",         "ConfigManagerUserConfig" : "false",         "CreationClassName" : "Win32_DiskDrive",         "Description" : "Disk drive",         "FirmwareRevision" : "1.0",         "Index" : 1,         "InterfaceType" : "IDE"     } ] ```  从Zabbix Windows agent 4.4起支持此监控项。

en-us	#### Item key  Unlike with file system and network interface discovery, the item does not necessarily has to have an "snmp.discovery" key - item type of SNMP agent is sufficient.  Discovery of SNMP OIDs is supported since Zabbix server/proxy 2.0.  To configure the discovery rule, do the following:  -   Go to: *Configuration* → *Templates* -   Click on *Discovery* in the row of an appropriate template  ![](../../../../../assets/en/manual/discovery/low_level_discovery/templates_snmp.png)  -   Click on *Create discovery rule* in the upper right corner of the     screen -   Fill in the discovery rule form with the required details as in the     screenshot below  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_snmp.png){width="600"}  All mandatory input fields are marked with a red asterisk.  The OIDs to discover are defined in SNMP OID field in the following format: `discovery[{#MACRO1}, oid1, {#MACRO2}, oid2, …,]`  where *{\#MACRO1}*, *{\#MACRO2}* … are valid lld macro names and *oid1*, *oid2*... are OIDs capable of generating meaningful values for these macros. A built-in macro *{\#SNMPINDEX}* containing index of the discovered OID is applied to discovered entities. The discovered entities are grouped by *{\#SNMPINDEX}* macro value.  To understand what we mean, let us perform few snmpwalks on our switch:      $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifDescr     IF-MIB::ifDescr.1 = STRING: WAN     IF-MIB::ifDescr.2 = STRING: LAN1     IF-MIB::ifDescr.3 = STRING: LAN2      $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifPhysAddress     IF-MIB::ifPhysAddress.1 = STRING: 8:0:27:90:7a:75     IF-MIB::ifPhysAddress.2 = STRING: 8:0:27:90:7a:76     IF-MIB::ifPhysAddress.3 = STRING: 8:0:27:2b:af:9e  And set SNMP OID to: `discovery[{#IFDESCR}, ifDescr, {#IFPHYSADDRESS}, ifPhysAddress]`  Now this rule will discover entities with {\#IFDESCR} macros set to **WAN**, **LAN1** and **LAN2**, {\#IFPHYSADDRESS} macros set to **8:0:27:90:7a:75**, **8:0:27:90:7a:76**, and **8:0:27:2b:af:9e**, {\#SNMPINDEX} macros set to the discovered OIDs indexes **1**, **2** and **3**:  ``` {.java} [     {         "{#SNMPINDEX}": "1",         "{#IFDESCR}": "WAN",         "{#IFPHYSADDRESS}": "8:0:27:90:7a:75"     },     {         "{#SNMPINDEX}": "2",         "{#IFDESCR}": "LAN1",         "{#IFPHYSADDRESS}": "8:0:27:90:7a:76"     },     {         "{#SNMPINDEX}": "3",         "{#IFDESCR}": "LAN2",         "{#IFPHYSADDRESS}": "8:0:27:2b:af:9e"     } ] ```  If an entity does not have the specified OID, then the corresponding macro will be omitted for this entity. For example if we have the following data:      ifDescr.1 "Interface #1"     ifDescr.2 "Interface #2"     ifDescr.4 "Interface #4"      ifAlias.1 "eth0"     ifAlias.2 "eth1"     ifAlias.3 "eth2"     ifAlias.5 "eth4"  Then in this case SNMP discovery `discovery[{#IFDESCR}, ifDescr, {#IFALIAS}, ifAlias]` will return the following structure:  ``` {.java} [     {         "{#SNMPINDEX}": 1,         "{#IFDESCR}": "Interface #1",         "{#IFALIAS}": "eth0"     },     {         "{#SNMPINDEX}": 2,         "{#IFDESCR}": "Interface #2",         "{#IFALIAS}": "eth1"     },     {         "{#SNMPINDEX}": 3,         "{#IFALIAS}": "eth2"     },     {         "{#SNMPINDEX}": 4,         "{#IFDESCR}": "Interface #4"     },     {         "{#SNMPINDEX}": 5,         "{#IFALIAS}": "eth4"     } ] ```
zh-cn	#### 监控项的键  跟文件系统和网络接口自动发现不同，SNMP自动发现的监控项无需配置  "snmp.discovery" 键 - 只要监控项类型设置为SNMP agent就足够了。  从Zabbix server/proxy 2.0起支持SNMP OID自动发现。  要配置自动发现规则，需要完成下面的步骤:  -   找到: *配置* → *模板* -   在对应模板所在的那一行点击 *自动发现*   ![](../../../../../assets/en/manual/discovery/low_level_discovery/templates_snmp.png)  -   点击屏幕右上角的 *创建自动发现规则*  -   填写下面截图中的自动发现规则表格  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_snmp.png){width="600"}  所有强制输入框标记为红色星号。  待发现的OID在SNMP OID输入框中定义，格式如下: `discovery[{#MACRO1}, oid1, {#MACRO2}, oid2, …,]`  其中 *{\#MACRO1}*, *{\#MACRO2}* … 是有效的LLD宏名称，然后 *oid1*, *oid2*... 是可以为这些宏生成具体值的OID。内置的宏 *{\#SNMPINDEX}* 包含已发现OID的索引，这个宏可用于已发现的实体上。已发现的实体通过 *{\#SNMPINDEX}* 宏的返回值来进行分组。  要理解上面说的，我们来演示一下对交换机执行snmpwalk操作:      $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifDescr     IF-MIB::ifDescr.1 = STRING: WAN     IF-MIB::ifDescr.2 = STRING: LAN1     IF-MIB::ifDescr.3 = STRING: LAN2      $ snmpwalk -v 2c -c public 192.168.1.1 IF-MIB::ifPhysAddress     IF-MIB::ifPhysAddress.1 = STRING: 8:0:27:90:7a:75     IF-MIB::ifPhysAddress.2 = STRING: 8:0:27:90:7a:76     IF-MIB::ifPhysAddress.3 = STRING: 8:0:27:2b:af:9e  然后设置 SNMP OID 为: `discovery[{#IFDESCR}, ifDescr, {#IFPHYSADDRESS}, ifPhysAddress]`  现在规则会自动去发现对应实体，实体中的 {\#IFDESCR} 宏需要设置为 **WAN**, **LAN1** 和 **LAN2**, {\#IFPHYSADDRESS} 宏需要设置为 **8:0:27:90:7a:75**, **8:0:27:90:7a:76**, 和 **8:0:27:2b:af:9e**, {\#SNMPINDEX} 宏需要设置为已发现的OID的索引值 **1**, **2** 和 **3**:  ``` {.java} [     {         "{#SNMPINDEX}": "1",         "{#IFDESCR}": "WAN",         "{#IFPHYSADDRESS}": "8:0:27:90:7a:75"     },     {         "{#SNMPINDEX}": "2",         "{#IFDESCR}": "LAN1",         "{#IFPHYSADDRESS}": "8:0:27:90:7a:76"     },     {         "{#SNMPINDEX}": "3",         "{#IFDESCR}": "LAN2",         "{#IFPHYSADDRESS}": "8:0:27:2b:af:9e"     } ] ```  如果实体没有指定的OID，则对应的宏会被跳过。比如，假如存在下面的数据:      ifDescr.1 "Interface #1"     ifDescr.2 "Interface #2"     ifDescr.4 "Interface #4"      ifAlias.1 "eth0"     ifAlias.2 "eth1"     ifAlias.3 "eth2"     ifAlias.5 "eth4"  在此场景中，SNMP 自动发现 `discovery[{#IFDESCR}, ifDescr, {#IFALIAS}, ifAlias]` 会返回这种结构的数据:  ``` {.java} [     {         "{#SNMPINDEX}": 1,         "{#IFDESCR}": "Interface #1",         "{#IFALIAS}": "eth0"     },     {         "{#SNMPINDEX}": 2,         "{#IFDESCR}": "Interface #2",         "{#IFALIAS}": "eth1"     },     {         "{#SNMPINDEX}": 3,         "{#IFALIAS}": "eth2"     },     {         "{#SNMPINDEX}": 4,         "{#IFDESCR}": "Interface #4"     },     {         "{#SNMPINDEX}": 5,         "{#IFALIAS}": "eth4"     } ] ```

en-us	#### Item net.tcp.service parameters  **ftp**  Creates a TCP connection and expects the first 4 characters of the response to be "220 ", then sends "QUIT\\r\\n". Default port 21 is used if not specified.  **http**  Creates a TCP connection without expecting and sending anything. Default port 80 is used if not specified.  **https**  Uses (and only works with) libcurl, does not verify the authenticity of the certificate, does not verify the host name in the SSL certificate, only fetches the response header (HEAD request). Default port 443 is used if not specified.  **imap**  Creates a TCP connection and expects the first 4 characters of the response to be "\* OK", then sends "a1 LOGOUT\\r\\n". Default port 143 is used if not specified.  **ldap**  Opens a connection to an LDAP server and performs an LDAP search operation with filter set to (objectClass=\*). Expects successful retrieval of the first attribute of the first entry. Default port 389 is used if not specified.  **nntp**  Creates a TCP connection and expects the first 3 characters of the response to be "200" or "201", then sends "QUIT\\r\\n". Default port 119 is used if not specified.  **pop**  Creates a TCP connection and expects the first 3 characters of the response to be "+OK", then sends "QUIT\\r\\n". Default port 110 is used if not specified.  **smtp**  Creates a TCP connection and expects the first 3 characters of the response to be "220", followed by a space, the line ending or a dash. The lines containing a dash belong to a multiline response and the response will be re-read until a line without the dash is received. Then sends "QUIT\\r\\n". Default port 25 is used if not specified.  **ssh**  Creates a TCP connection. If the connection has been established, both sides exchange an identification string (SSH-major.minor-XXXX), where major and minor are protocol versions and XXXX is a string. Zabbix checks if the string matching the specification is found and then sends back the string "SSH-major.minor-zabbix\_agent\\r\\n" or "0\\n" on mismatch. Default port 22 is used if not specified.  **tcp**  Creates a TCP connection without expecting and sending anything. Unlike the other checks requires the port parameter to be specified.  **telnet**  Creates a TCP connection and expects a login prompt (':' at the end). Default port 23 is used if not specified.
zh-cn	#### 监控项 net.tcp.service 参数  **FTP**  创建 TCP 连接并期望响应的前 4 个字符为“220”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 21。  **http**  创建一个 TCP 连接而不期望和发送任何东西。 如果未指定，则使用默认端口 80。  **https**  使用（并且仅适用于）libcurl，不验证证书的真实性，不验证 SSL 证书中的主机名，仅获取响应标头（HEAD 请求）。 如果未指定，则使用默认端口 443。  **imap**  创建 TCP 连接并期望响应的前 4 个字符为“\* OK”，然后发送“a1 LOGOUT\\r\\n”。 如果未指定，则使用默认端口 143。  **ldap**  打开与 LDAP 服务器的连接并执行 LDAP 搜索操作，过滤器设置为 (objectClass=\*)。 期望成功检索第一个条目的第一个属性。 如果未指定，则使用默认端口 389。  **nntp**  创建 TCP 连接并期望响应的前 3 个字符为“200”或“201”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 119。  **pop**  创建 TCP 连接并期望响应的前 3 个字符为“+OK”，然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 110。  **smtp**  创建一个 TCP 连接并期望响应的前 3 个字符为“220”，后跟空格、行尾或破折号。包含破折号的行属于多行响应，响应将被重新读取直到收到没有破折号的行。 然后发送“QUIT\\r\\n”。 如果未指定，则使用默认端口 25。  **ssh**  创建 TCP 连接。 如果连接已经建立，双方交换一个标识字符串（SSH-major.minor-XXXX），其中major和minor是协议版本，XXXX是一个字符串。 Zabbix 检查是否找到与规范匹配的字符串，然后在不匹配时发回字符串“SSH-major.minor-zabbix\_agent\\r\\n”或“0\\n”。 如果未指定，则使用默认端口 22。  **TCP**  创建一个 TCP 连接而不期望和发送任何东西。 与其他检查不同，需要指定端口参数。  **telnet**  创建一个 TCP 连接并期望登录提示（末尾为“:”）。如果未指定，则使用默认端口 23。

en-us	#### Item net.udp.service parameters  **ntp**  Sends an SNTP packet over UDP and validates the response according to [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5). Default port 123 is used if not specified.
zh-cn	#### 监控项 net.udp.service 参数  **ntp**  在UDP上发送一个SNTP包，并根据  [RFC 4330, section 5](http://tools.ietf.org/html/rfc4330#section-5)需要验证响应。 如果未指定，则使用默认端口123。

en-us	### Item  ::: noteclassic Web items cannot be directly created, updated or deleted via the Zabbix API. :::  The item object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the item.| |**delay**<br>(required)|string|Update interval of the item. Accepts seconds or a time unit with suffix (30s,1m,2h,1d).<br>Optionally one or more [custom intervals](/manual/config/items/item/custom_intervals) can be specified either as flexible intervals or scheduling.<br>Multiple intervals are separated by a semicolon.<br>User macros may be used. A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Flexible intervals may be written as two macros separated by a forward slash (e.g. `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host or template that the item belongs to.<br><br>For update operations this field is *readonly*.| |**interfaceid**<br>(required)|string|ID of the item's host interface.<br><br>Used only for host items. Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, calculated, dependent, database monitor and script items. Optional for HTTP agent items.| |**key\_**<br>(required)|string|Item key.| |**name**<br>(required)|string|Name of the item.| |**type**<br>(required)|integer|Type of the item.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - Simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>9 - Web item;<br>10 - External check;<br>11 - Database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - Telnet agent;<br>15 - Calculated;<br>16 - JMX agent;<br>17 - SNMP trap;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script| |**url**<br>(required)|string|URL string, required only for HTTP agent item type. Supports user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(required)|integer|Type of information of the item.<br><br>Possible values:<br>0 - numeric float;<br>1 - character;<br>2 - log;<br>3 - numeric unsigned;<br>4 - text.| |allow\_traps|integer|HTTP agent item field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent items or HTTP agent items.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM<br>3 - Kerberos| |description|string|Description of the item.| |error|string|*(readonly)* Error text if there are problems updating the item.| |flags|integer|*(readonly)* Origin of the item.<br><br>Possible values:<br>0 - a plain item;<br>4 - a discovered item.| |follow\_redirects|integer|HTTP agent item field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent item field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |history|string|A time unit of how long the history data should be stored. Also accepts user macro.<br><br>Default: 90d.| |http\_proxy|string|HTTP agent item field. HTTP(S) proxy connection string.| |inventory\_link|integer|ID of the host inventory field that is populated by the item.<br><br>Refer to the [host inventory page](/manual/api/reference/host/object#host_inventory) for a list of supported host inventory fields and their IDs.<br><br>Default: 0.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI items.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lastclock|timestamp|*(readonly)* Time when the item was last updated.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |lastns|integer|*(readonly)* Nanoseconds when the item was last updated.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |lastvalue|string|*(readonly)* Last value of the item.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |logtimefmt|string|Format of the time in log entries. Used only by log items.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and maximum count of dependent items equal to 29999 are allowed.<br><br>Required by dependent items.| |output\_format|integer|HTTP agent item field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the item:<br>- executed script for SSH and Telnet items;<br>- SQL query for database monitor items;<br>- formula for calculated items;<br>- the script for script item.| |parameters|array|Additional parameters for script items. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent items.<br>When used by JMX, username should also be specified together with password or both properties should be left blank.| |post\_type|integer|HTTP agent item field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent item field. HTTP(S) request body data. Used with post\_type.| |prevvalue|string|*(readonly)* Previous value of the item.<br><br>By default, only values that fall within the last 24 hours are displayed. You can extend this time period by changing the value of *Max history display period* parameter in the *[Administration → General](/manual/web_interface/frontend_sections/administration/general#gui)* menu section.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent item field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent item field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent item field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent item field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent item field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent item field. Password for SSL Key file.| |state|integer|*(readonly)* State of the item.<br><br>Possible values:<br>0 - *(default)* normal;<br>1 - not supported.| |status|integer|Status of the item.<br><br>Possible values:<br>0 - *(default)* enabled item;<br>1 - disabled item.| |status\_codes|string|HTTP agent item field. Ranges of required HTTP status codes separated by commas. Also supports user macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template item.<br><br>*Hint*: Use the `hostid` property to specify the template that the item belongs to.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script items. Supports user macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper items or HTTP agent items.| |trends|string|A time unit of how long the trends data should be stored. Also accepts user macro.<br><br>Default: 365d.| |units|string|Value units.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent items.<br><br>Required by SSH and Telnet items.<br>When used by JMX, password should also be specified together with username or both properties should be left blank.| |uuid|string|Universal unique identifier, used for linking imported item to already existing ones. Used only for items on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |valuemapid|string|ID of the associated value map.| |verify\_host|integer|HTTP agent item field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |verify\_peer|integer|HTTP agent item field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 监控项  ::: 注意 无法直接通过 Zabbix API 创建、更新或删除 Web 监控项。 :::  监控项对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |itemid|string|*（只读）* 监控项 ID。| |**delay**<br>（必填）|string|更新监控项的时间间隔。接收秒或者带后缀的时间单位（30s、1m、2h、1d）。<br>可以通过 [自定义间隔](/manual/config/items/item/custom_intervals) 进行组合，从而更灵活的设置间隔时间。<br>多个间隔使用分号分隔。<br>可以使用用户宏。单个宏必须填充完整个字段。不支持字段中包含多个宏或文本混合宏。<br>通过编写由正斜杠分隔的两段宏能更加灵活地设置间隔时间 (e.g. `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br> Zabbix采集器，相关项监控和Zabbix agent（主动）可选 `mqtt.get` key。| |**hostid**<br>（必填）|string|监控项所属的主机或模板的 ID。<br><br>更新操作中，此字段为*只读*。| |**interfaceid**<br>（必填）|string|监控项主机接口的 ID。<br><br>仅用于主机监控项。对于Zabbix agent（主动），内部检查、采集器、可计算的监控项、相关项监控、数据库监控和脚本监控项是不需要的。| |**key\_**<br>（必填）|string|监控项关键字。| |**name**<br>（必填）|string|监控项名称。| |**type**<br>（必要项）|integer|监控项类型。<br><br>可用值：<br>0 - Zabbix agent；<br>2 - zabbix 采集器；<br>3 - 简单检查；<br>5 - 内部检查；<br>7 - Zabbix agent (主动)；<br>9 - web 监控项；<br>10 - 外部检查；<br>11 - 数据库监控；<br>12 - IPMI agent；<br>13 - SSH agent；<br>14 - Telnet agent；<br>15 - 可计算的监控；<br>16 - JMX agent；<br>17 - SNMP trap；<br>18 - 相关项监控；<br>19 - HTTP agent；<br>20 - SNMP agent；<br>21 - 脚本。| |**url**<br>（必填）|string|URL 字符串，用于 HTTP agent 监控项类型。支持用户宏 {HOST.IP}、{HOST.CONN}、{HOST.DNS}、{HOST.HOST}、{HOST.NAME}、{ITEM.ID}、{ITEM.KEY}。| |**value\_type**<br>（必填）|integer|监控项数据类型<br><br>可用值：<br>0 - 浮点型；<br>1 - 字符；<br>2 - 日志；<br>3 - 无符号数字；<br>4 - 文本。| |allow\_traps|integer|HTTP agent 监控项字段。也允许在采集器监控项中填充值。<br><br>0 - *（默认）* 不允许接受传入数据。<br>1 - 允许接受传入数据。| |authtype|integer|仅 SSH agent 监控项或 HTTP agent 监控项使用。<br><br>SSH agent 身份验证方法可用值：<br>0 - *（默认）* 密码；<br>1 - 公钥。<br><br>HTTP agent 身份验证方法可用值：<br>0 - *（默认）* 无认证；<br>1 - basic 认证；<br>2 - NTLM 认证<br>3 - Kerberos 认证；| |description|string|监控项说明。| |error|string|*（只读）* 如果更新监控项时报错，则显示错误信息。| |flags|integer|*（只读）* 监控项来源<br><br>可用值：<br>0 - 平台监控项；<br>4 - 发现监控项。| |follow\_redirects|integer|HTTP agent 监控项字段。在合并数据时遵循响应重定向。<br><br>0 - 不遵循重定向；<br>1 - *（默认）* 遵循重定向。| |headers|object|HTTP agent 监控项字段。具有 HTTP（S）请求头的对象，其中请求头名用作键，请求头值用作值。<br><br>示例：<br>{ "User-Agent": "Zabbix" }| |history|string|历史数据应保留多长时间的单位。同样接受用户宏。<br><br>默认： 90天。| |http\_proxy|string|HTTP agent 监控项字段。HTTP（S）agent 连接字符串。| |inventory\_link|integer|由监控项填充的主机资产字段的 ID。<br><br>请参阅 [主机资产清单页](/manual/api/reference/host/object#host_inventory) ，了解更多受支持的主机资产清单字段及其 ID 列表。<br><br>默认： 0。| |ipmi\_sensor|string|IPMI 传感器。仅用于 IPMI 监控项。| |jmx\_endpoint|string|JMX agent 自定义连接字符串。<br><br>默认值：<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |lastclock|timestamp|*（只读）* 上一次更新监控项的时间。<br><br>默认情况下，仅显示过去24小时内的值。您可以通过更改 *[管理 → 通用](/manual/web_interface/frontend_sections/administration/general#gui)* 菜单中的 *最大历史显示周期* 参数值来延长此时间段。| |lastns|integer|*（只读）* 上一次更新监控项时的纳秒数。<br><br>默认情况下，仅显示过去24小时内的值。您可以通过更改 *[管理 → 通用](/manual/web_interface/frontend_sections/administration/general#gui)* 菜单中的 *最大历史显示周期* 参数值来延长此时间段。| |lastvalue|string|*（只读）* 监控项最后获取的值。<br><br>默认情况下，仅显示过去24小时内的值。您可以通过更改 *[管理 → 通用](/manual/web_interface/frontend_sections/administration/general#gui)* 菜单中的 *最大历史显示周期* 参数值来延长此时间段。| |logtimefmt|string|日志条目中的时间格式。仅日志监控项使用。| |master\_itemid|integer|主监控项 ID。<br>最多允许递归 3 个相关项监控，且相关监控项的最大计数为 29999。<br><br>相关监控项的先决条件。| |output\_format|integer|HTTP agent 监控项字段。将响应转换为 JSON 格式。<br><br>0 - *（默认）* 原格式；<br>1 - 转换为 JSON 格式。| |params|string|其他参数取决于监控项的类型：<br>- SSH 和 Telnet agent 的可执行脚本；<br>- 数据库监控项的 SQL 查询；<br>- 可计算监控项的公式；<br>- 脚本监控项的脚本。| |parameters|array|脚本监控项的其他参数。具有 “名称” 和 “值” 属性的对象数组，其中名称必须唯一。| |password|string|验证密码。用于一般检查、SSH、Telnet、数据库监控、JMX 和 HTTP agent 监控项。<br>当 JMX 使用时，用户名应与密码一起指定，或者两个属性都留空。| |post\_type|integer|HTTP agent 监控项字段。Posts 属性中存储的 post 数据体的类型。<br><br>0 - *（默认）* 原始数据；<br>2 - JSON 数据；<br>3 - XML 数据。| |posts|string|HTTP agent 监控项字段。HTTP（S）请求正文数据。与 post\_type 一同使用。| |prevvalue|string|*（只读）* 监控项的上一个值。<br><br>默认情况下，仅显示过去24小时内的值。您可以通过更改 *[管理 → 通用](/manual/web_interface/frontend_sections/administration/general#gui)* 菜单中的 *最大历史显示周期* 参数值来延长此时间段。| |privatekey|string|私钥文件的名称。| |publickey|string|公钥文件的名称。| |query\_fields|array|HTTP agent 监控项字段。查询参数。具有 “键”：“值” 对的对象数组，其中值可以是空字符串。| |request\_method|integer|HTTP agent 监控项字段。请求方法类型：<br><br>0 - *（默认）* GET；<br>1 - POST；<br>2 - PUT；<br>3 - HEAD。| |retrieve\_mode|integer|HTTP agent 监控项字段。具体存储响应的部分。<br><br>0 - *（默认）* Body；<br>1 - Headers；<br>2 - Body and headers。<br><br>对于 request\_method HEAD 仅允许方法 1。| |snmp\_oid|string|SNMP OID。| |ssl\_cert\_file|string|HTTP agent 监控项字段。SSL 公钥文件路径。| |ssl\_key\_file|string|HTTP agent 监控项字段。SSL 私钥文件路径。| |ssl\_key\_password|string|HTTP agent 监控项字段。SSL 密钥文件的密码。| |state|integer|*（只读）* 监控项状态。<br><br>可用值：<br>0 - *（默认）* 标准；<br>1 - 不受支持。| |status|integer|监控项状态。<br><br>可用值：<br>0 - *（默认）* 启用监控项；<br>1 - 禁用监控项。| |status\_codes|string|HTTP agent 监控项字段。目标HTTP状态代码的范围，用逗号分隔。还支持将用户宏作为逗号分隔列表的一部分。<br><br>示例： 200,200-{$M},{$M},200-400| |templateid|string|*（只读）* 父模板监控项的 ID。<br><br>*提示*：使用  `hostid` 属性指定监控项所属的模板。| |timeout|string|监控项数据轮询请求超时。用于 HTTP agent 和脚本监控项。支持用户宏。<br><br>默认：3秒。<br>最大值：60秒。| |trapper\_hosts|string|允许的主机。采集器监控项或 HTTP agent 监控项使用。| |trends|string|趋势数据应保留多长时间的单位。可接受用户宏。<br><br>默认：365天。| |units|string|值的单位。| |username|string|用于身份验证的用户名。用于一般检查、SSH、Telnet、数据库监控项、JMX 和 HTTP agent 监控项。<br><br>SSH 和 Telnet 监控项先决条件。<br>当 JMX 使用时，用户名应与密码一起指定，或者两个属性都留空。| |uuid|string|通用唯一标识符，用于将导入的监控项链接到现有监控项。仅模板包含项目使用。如果未指定会自动生成。<br><br>对于更新操作，此字段为 *只读*。| |valuemapid|string|关联值映射 ID。| |verify\_host|integer|HTTP agent 监控项字段。验证 URL 中的主机名是否位于主机证书的公用名字段或使用者备用名字段中。<br><br>0 - *（默认）* 不验证；<br>1 - 验证。| |verify\_peer|integer|HTTP agent 监控项字段。验证主机证书的真实性。<br><br>0 - *（默认）* 不验证；<br>1 - 验证。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# > Item object  The following objects are directly related to the `item` API.
zh-cn	# > 监控项对象  以下对象直接调用 `item` API 进行操作。

en-us	### Item preprocessing  The item preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|output^6,\ 8^|<|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JOSN|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro.\ ^8^ Prometheus output following the syntax: `<label name>`.  
zh-cn	### Item preprocessing 监控项预处理  The item preprocessing object has the following properties. 监控项预处理对象有如下属性。  |Property|Type|Description| |--------|----|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.|  

en-us	### Item preprocessing  The item preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro.\ ^8^ Prometheus output following the syntax: `<label name>` (can be a user macro) if `label` is selected as the second parameter.\ ^9^ One of the aggregation functions: `sum`, `min`, `max`, `avg`, `count` if `function` is selected as the second parameter.
zh-cn	### 监控项预处理  监控项预处理对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**type**<br>（必要)|integer（整数）|预处理选项类型。<br><br>可用值：<br>1 - Custom multiplier（自定义乘数）；<br>2 - Right trim（移除右侧空白字符）；<br>3 - Left trim（移除左侧空白字符）；<br>4 - Trim（移除空白字符）；<br>5 - Regular expression matching（正则表达式匹配）；<br>6 - Boolean to decimal（布尔值转换十进制）；<br>7 - Octal to decimal（八进制转换十进制）；<br>8 - Hexadecimal to decimal（十六进制转十进制）；<br>9 - Simple change（先前值到新值的基本变化）；<br>10 - Change per second（每秒钟变化量）；<br>11 - XML XPath（XML 解析）；<br>12 - JSONPath（JSON解析）；<br>13 - In range（生成序列）；<br>14 - Matches regular expression（匹配正则表达式）；<br>15 - Does not match regular expression（不匹配正则表达式）；<br>16 - Check for error in JSON（检查 JSON 错误）；<br>17 - Check for error in XML（检查 XML 错误）；<br>18 - Check for error using regular expression（检查正则表达式使用错误）；<br>19 - Discard unchanged（丢弃重复数据）；<br>20 - Discard unchanged with heartbeat（设置心跳检查周期，丢弃重复数据）；<br>21 - JavaScript（JS格式）；<br>22 - Prometheus pattern（Prometheus 模式）；<br>23 - Prometheus to JSON（Prometheus 转换 JSON）；<br>24 - CSV to JSON（CSV 转换 JSON）；<br>25 - Replace（替换）；<br>26 - Check unsupported（检查不支持的值）；<br>27 - XML to JSON（XML 转换 JSON）。| |**params**<br>（必要）|预处理选项使用的其他参数。多个参数由LF（\\n）字符分隔。| |**error\_handler**<br>（必要）|integer（整数）|预处理步骤失败时使用的操作类型：<br><br>可用值：<br>0 - Error message is set by Zabbix server（Zabbix 服务器自带错误消息）；<br>1 - Discard value（丢弃值）；<br>2 - Set custom value（设置自定义值）；<br>3 - Set custom error message（设置自定义错误信息）。| |**error\_handler\_params**<br>（必要)|（字符串）|错误处理器参数。与 `error_handler` 搭配使用。<br><br>如果 `error_handler` 类型为 0 或 1，此值必须为空。<br>如果 `error_handler` 类型为 2，此值可以为空。<br>如果 `error_handler` 类型为 3，此值不能为空。|  预处理类型均支持以下参数和错误处理器。  |预处理类型|名称|参数 1|参数 2|参数 3|支持的错误处理器| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier（自定义倍数）|number^1,\ 6^（数字型）|<|<|0, 1, 2, 3| |2|Right trim（移除右侧空白字符）|list of characters^2^（字符列表）|<|<|<| |3|Left trim（移除左侧空白字符）|list of characters^2^（字符列表）|<|<|<| |4|Trim（移除空白字符）|list of characters^2^（字符列表）|<|<|<| |5|Regular expression（正则表达式）|pattern^3^（模式）|output^2^（输出）|<|0, 1, 2, 3| |6|Boolean to decimal（布尔值转换十进制）|<|<|<|0, 1, 2, 3| |7|Octal to decimal（八进制转换十进制）|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal（十六进制转十进制）|<|<|<|0, 1, 2, 3| |9|Simple change（先前值到新值的基本变化）|<|<|<|0, 1, 2, 3| |10|Change per second（每秒钟变化量）|<|<|<|0, 1, 2, 3| |11|XML XPath（XML 解析）|path^4^（解析）|<|<|0, 1, 2, 3| |12|JSONPath（JSON解析）|path^4^（解析）|<|<|0, 1, 2, 3| |13|In range（生成序列）|min^1,\ 6^（最小值）|max^1,\ 6^（最大值）|<|0, 1, 2, 3| |14|Matches regular expression（匹配正则表达式）|pattern^3^（模式）|<|<|0, 1, 2, 3| |15|Does not match regular expression（不匹配正则表达式）|pattern^3^（模式）|<|<|0, 1, 2, 3| |16|Check for error in JSON（检查 JSON 错误）|path^4^（解析）|<|<|0, 1, 2, 3| |17|Check for error in XML（检查 XML 错误）|path^4^（解析）|<|<|0, 1, 2, 3| |18|Check for error using regular expression（检查正则表达式使用错误）|pattern^3^（模式）|output^2^（输出）|<|0, 1, 2, 3| |19|Discard unchanged（丢弃重复数据）|<|<|<|<| |20|Discard unchanged with heartbeat（设置心跳检查周期，丢弃重复数据）|seconds^5,\ 6^（秒）|<|<|<| |21|JavaScript（JS格式）|script^2^|<|<|<| |22|Prometheus pattern（Prometheus 模式）|pattern^6,\ 7^（模式）|`value`, `label`, `function`|output^8,\ 9^（输出）|0, 1, 2, 3| |23|Prometheus to JSON（Prometheus 转换 JSON）|pattern^6,\ 7^（模式）|<|<|0, 1, 2, 3| |24|CSV to JSON（CSV 转换 JSON）|character^2^（字符）|character^2^（字符）|0,1|0, 1, 2, 3| |25|Replace（替换）|search string^2^（查找字符串）|replacement^2^（替换）|<|<| |26|Check unsupported（检查不支持的值）|<|<|<|1, 2, 3| |27|XML to JSON（XML 转换 JSON）|<|<|<|0, 1, 2, 3|  ^1^ 整数或浮点数\ ^2^ 字符串\ ^3^ 正则表达式\ ^4^ JSONPath 或 XML XPath 解析\ ^5^ 正整数（支持时间后缀，例如：30s、1m、2h、1d）\ ^6^ 用户宏\ ^7^ Prometheus 模式遵循以下语法：`<metric name>{<label name>="<label value>", ...} == <value>`。Prometheus 每个模式组件（metric, label name, label value and metric value）都可以是用户宏。\ ^8^ 如果第二个参数选择 `label`，则 Prometheus 输出遵循以下语法：`<label name>`（可以是用户宏）\ ^9^ 如果第二个参数选择 `function`，则相对应以下聚合函数：`sum`、`min`、`max`、`avg`、`count`。\

en-us	### Item preprocessing  The item preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro.\ ^8^ Prometheus output following the syntax: `<label name>` (can be a user macro) if `label` is selected as the second parameter.\ ^9^ One of the aggregation functions: `sum`, `min`, `max`, `avg`, `count` if `function` is selected as the second parameter.
zh-cn	### 监控项预处理  监控项预处理对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|说明| |--------|---------------------------------------------------|-----------| |**type**<br>（必要)|integer（整数）|预处理选项类型。<br><br>可用值：<br>1 - Custom multiplier（自定义乘数）；<br>2 - Right trim（移除右侧空白字符）；<br>3 - Left trim（移除左侧空白字符）；<br>4 - Trim（移除空白字符）；<br>5 - Regular expression matching（正则表达式匹配）；<br>6 - Boolean to decimal（布尔值转换十进制）；<br>7 - Octal to decimal（八进制转换十进制）；<br>8 - Hexadecimal to decimal（十六进制转十进制）；<br>9 - Simple change（先前值到新值的基本变化）；<br>10 - Change per second（每秒钟变化量）；<br>11 - XML XPath（XML 解析）；<br>12 - JSONPath（JSON解析）；<br>13 - In range（生成序列）；<br>14 - Matches regular expression（匹配正则表达式）；<br>15 - Does not match regular expression（不匹配正则表达式）；<br>16 - Check for error in JSON（检查 JSON 错误）；<br>17 - Check for error in XML（检查 XML 错误）；<br>18 - Check for error using regular expression（检查正则表达式使用错误）；<br>19 - Discard unchanged（丢弃重复数据）；<br>20 - Discard unchanged with heartbeat（设置心跳检查周期，丢弃重复数据）；<br>21 - JavaScript（JS格式）；<br>22 - Prometheus pattern（Prometheus 模式）；<br>23 - Prometheus to JSON（Prometheus 转换 JSON）；<br>24 - CSV to JSON（CSV 转换 JSON）；<br>25 - Replace（替换）；<br>26 - Check unsupported（检查不支持的值）；<br>27 - XML to JSON（XML 转换 JSON）。| |**params**<br>（必要）|预处理选项使用的其他参数。多个参数由LF（\\n）字符分隔。| |**error\_handler**<br>（必要）|integer（整数）|预处理步骤失败时使用的操作类型：<br><br>可用值：<br>0 - Error message is set by Zabbix server（Zabbix 服务器自带错误消息）；<br>1 - Discard value（丢弃值）；<br>2 - Set custom value（设置自定义值）；<br>3 - Set custom error message（设置自定义错误信息）。| |**error\_handler\_params**<br>（必要)|（字符串）|错误处理器参数。与 `error_handler` 搭配使用。<br><br>如果 `error_handler` 类型为 0 或 1，此值必须为空。<br>如果 `error_handler` 类型为 2，此值可以为空。<br>如果 `error_handler` 类型为 3，此值不能为空。|  预处理类型均支持以下参数和错误处理器。  |预处理类型|名称|参数 1|参数 2|参数 3|支持的错误处理器| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier（自定义倍数）|number^1,\ 6^（数字型）|<|<|0, 1, 2, 3| |2|Right trim（移除右侧空白字符）|list of characters^2^（字符列表）|<|<|<| |3|Left trim（移除左侧空白字符）|list of characters^2^（字符列表）|<|<|<| |4|Trim（移除空白字符）|list of characters^2^（字符列表）|<|<|<| |5|Regular expression（正则表达式）|pattern^3^（模式）|output^2^（输出）|<|0, 1, 2, 3| |6|Boolean to decimal（布尔值转换十进制）|<|<|<|0, 1, 2, 3| |7|Octal to decimal（八进制转换十进制）|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal（十六进制转十进制）|<|<|<|0, 1, 2, 3| |9|Simple change（先前值到新值的基本变化）|<|<|<|0, 1, 2, 3| |10|Change per second（每秒钟变化量）|<|<|<|0, 1, 2, 3| |11|XML XPath（XML 解析）|path^4^（解析）|<|<|0, 1, 2, 3| |12|JSONPath（JSON解析）|path^4^（解析）|<|<|0, 1, 2, 3| |13|In range（生成序列）|min^1,\ 6^（最小值）|max^1,\ 6^（最大值）|<|0, 1, 2, 3| |14|Matches regular expression（匹配正则表达式）|pattern^3^（模式）|<|<|0, 1, 2, 3| |15|Does not match regular expression（不匹配正则表达式）|pattern^3^（模式）|<|<|0, 1, 2, 3| |16|Check for error in JSON（检查 JSON 错误）|path^4^（解析）|<|<|0, 1, 2, 3| |17|Check for error in XML（检查 XML 错误）|path^4^（解析）|<|<|0, 1, 2, 3| |18|Check for error using regular expression（检查正则表达式使用错误）|pattern^3^（模式）|output^2^（输出）|<|0, 1, 2, 3| |19|Discard unchanged（丢弃重复数据）|<|<|<|<| |20|Discard unchanged with heartbeat（设置心跳检查周期，丢弃重复数据）|seconds^5,\ 6^（秒）|<|<|<| |21|JavaScript（JS格式）|script^2^|<|<|<| |22|Prometheus pattern（Prometheus 模式）|pattern^6,\ 7^（模式）|`value`, `label`, `function`|output^8,\ 9^（输出）|0, 1, 2, 3| |23|Prometheus to JSON（Prometheus 转换 JSON）|pattern^6,\ 7^（模式）|<|<|0, 1, 2, 3| |24|CSV to JSON（CSV 转换 JSON）|character^2^（字符）|character^2^（字符）|0,1|0, 1, 2, 3| |25|Replace（替换）|search string^2^（查找字符串）|replacement^2^（替换）|<|<| |26|Check unsupported（检查不支持的值）|<|<|<|1, 2, 3| |27|XML to JSON（XML 转换 JSON）|<|<|<|0, 1, 2, 3|  ^1^ 整数或浮点数\ ^2^ 字符串\ ^3^ 正则表达式\ ^4^ JSONPath 或 XML XPath 解析\ ^5^ 正整数（支持时间后缀，例如：30s、1m、2h、1d）\ ^6^ 用户宏\ ^7^ Prometheus 模式遵循以下语法：`<metric name>{<label name>="<label value>", ...} == <value>`。Prometheus 每个模式组件（metric, label name, label value and metric value）都可以是用户宏。\ ^8^ 如果第二个参数选择 `label`，则 Prometheus 输出遵循以下语法：`<label name>`（可以是用户宏）\ ^9^ 如果第二个参数选择 `function`，则相对应以下聚合函数：`sum`、`min`、`max`、`avg`、`count`。\

en-us	#### itemprototype  Bug fixes:\ [ZBX-19118](https://support.zabbix.com/browse/ZBX-19118) `itemprototype.create`, `itemprototype.update`: property `interfaceid` is no longer required to create/update a HTTP agent type item prototype.\
zh-cn	#### 监控项原型  Bug修复：\ [ZBX-19118](https://support.zabbix.com/browse/ZBX-19118) `itemprototype.create`、`itemprototype.update`：不再需要属性 `interfaceid` 来创建/更新 HTTP 代理类型监控项原型。\

en-us	#### item prototype  Changes:\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `itemprototype.get`, `itemprototype.create`, `itemprototype.update`: added the third parameter to the Prometheus pattern preprocessing step. The second parameter will now determine an aggregation method: `value`, `label`, `function`. The third parameter will now contain Prometheus output for the aggregation method `label` or an aggregation function for the aggregation method `function`.\
zh-cn	 #### 监控项原型  变更：\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `itemprototype.get`，`itemprototype.create`，`itemprototype.update`：为Prometheus 模式预处理步骤添加第三个参数。第二个参数现在将会决定一个聚合方法：`value`，`label`，`function`。第三个参数现在将包含聚合方法`label`或聚合方法`function`的一个聚合函数的Prometheus输出。\

en-us	#### item prototype  Changes:\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `itemprototype.get`, `itemprototype.create`, `itemprototype.update`: added the third parameter to the Prometheus pattern preprocessing step. The second parameter will now determine an aggregation method: `value`, `label`, `function`. The third parameter will now contain Prometheus output for the aggregation method `label` or an aggregation function for the aggregation method `function`. \
zh-cn	 #### 监控项原型  变更：\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `itemprototype.get`，`itemprototype.create`，`itemprototype.update`：为Prometheus 模式预处理步骤添加第三个参数。第二个参数现在将会决定一个聚合方法：`value`，`label`，`function`。第三个参数现在将包含聚合方法`label`或聚合方法`function`的一个聚合函数的Prometheus输出。\

en-us	# itemprototype.create
zh-cn	# 创建监控项原型

en-us	# itemprototype.delete
zh-cn	# 删除监控项原型

en-us	# itemprototype.get
zh-cn	# 获取监控项原型

en-us	# > Item prototype object  The following objects are directly related to the `itemprototype` API.
zh-cn	# > 监控项原型对象  以下对象与 `监控项原型` API 直接相关。

en-us	### Item prototype preprocessing  The item prototype preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|output^6,\ 8^|<|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro, LLD macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro or LLD macro.\ ^8^ Prometheus output following the syntax: `<label name>`.  
zh-cn	### Item prototype preprocessing  The item prototype preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|output^6,\ 8^|<|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro, LLD macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro or LLD macro.\ ^8^ Prometheus output following the syntax: `<label name>`.  

en-us	### Item prototype preprocessing  The item prototype preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro, LLD macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro or LLD macro.\ ^8^ Prometheus output following the syntax: `<label name>` (can be a user macro or an LLD macro) if `label` is selected as the second parameter.\ ^9^ One of the aggregation functions: `sum`, `min`, `max`, `avg`, `count` if `function` is selected as the second parameter.
zh-cn	 ### 监控项原型预处理  监控项原型预处理对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**type**<br>（必需）|integer|预处理选项类型。<br><br>可能的值：<br>1 - 自定义乘数；<br>2 - 右修剪；<br>3 -左修剪;<br>4 - 修剪;<br>5 - 正则表达式匹配;<br>6 - 布尔转十进制;<br>7 - 八进制转十进制;<br>8 - 十六进制转十进制;<br>9 - 简单更改;<br>10 - 每秒更改;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - 在范围内;<br>14 - 匹配正则表达式;<br>15 -不匹配正则表达式；<br>16 - 检查 JSON 中的错误；<br>17 - 检查 XML 中的错误；<br>18 - 使用正则表达式检查错误；<br>19 - 丢弃未更改的内容；<br >20 - 丢弃未更改的心跳；<br>21 - JavaScript；<br>22 - Prometheus 模式；<br>23 - Prometheus 到 JSON；<br>24 - CSV 到 JSON；<br>25 - 替换；<br >26 - 检查不支持；<br>27 - XML 到 JSON。| |**params**<br>（必需）|string|预处理选项使用的附加参数。多个参数由 LF (\\n) 字符分隔。| |**error\_handler**<br>（必需）|integer|在预处理步骤失败的情况下使用的操作类型。<br><br>可能的值：<br>0 - 错误消息由 Zabbix server设置；<br>1 - 丢弃值；<br>2 - 设置自定义值；<br>3 - 设置自定义错误消息。| |**error\_handler\_params**<br>（必需）|string|错误处理程序参数。与 `error_handler` 一起使用。<br><br>如果 `error_handler` 为 0 或 1，则必须为空。<br>如果 `error_handler` 为 2，则可以为空。<br>如果`error_handler`为3，则不能为空。|  每个都支持以下参数和错误处理程序 预处理类型。  |预处理类型|名称|参数 1|参数 2|参数 3|支持的错误处理程序| |-------|----|-----------|-----------|-----------|------------| |1|自定义乘数|number^1,\ 6^|<|<|0, 1, 2, 3| |2|右修剪|list of characters^2^|<|<|<| |3|左修剪|list of characters^2^|<|<|<| |4|修剪|list of characters^2^|<|<|<| |5|正则表达式|pattern^3^|output^2^|<|0,1,2,3| |6|布尔转十进制|<|<|<|0,1,2,3| |7|八进制转十进制|<|<|<|0, 1, 2, 3| |8|十六进制转十进制|<|<|<|0,1,2,3| |9|简单更改|<|<|<|0,1,2,3| |10|每秒变化|<|<|<|0,1,2,3| |11|XML XPath|path^4^|<|<|0,1,2,3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|在范围内|min^1,\6^|max^1,\6^|<|0,1,2,3| |14|匹配正则表达式|pattern^3^|<|<|0,1,2,3| |15|不匹配正则表达式|pattern^3^|<|<|0,1,2,3| |16|检查 JSON 中的错误|path^4^|<|<|0, 1, 2, 3| |17|检查 XML 中的错误|path^4^|<|<|0, 1, 2, 3| |18|使用正则表达式检查错误|pattern^3^|output^2^|<|0,1,2,3| |19|原封不动地丢弃|<|<|<|<| |20|用心跳不改变丢弃|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|普罗米修斯模式|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus 转 JSON|pattern^6,\ 7^|<|<|0,1,2,3| |24|CSV 转 JSON|character^2^|character^2^|0,1|0,1,2,3| |25|替换|search string^2^|replacement^2^|<|<| |26|检查不支持|<|<|<|1,2,3| |27|XML 转 JSON|<|<|<|0, 1, 2, 3|  ^1^ 整数或浮点数\ ^2^ 字符串\ ^3^ 正则表达式\ ^4^ JSONPath 或 XML XPath\ ^5^ 正整数（支持时间后缀，例如 30s、1m、2h、1d)\ ^6^ 用户宏，LLD 宏\ ^7^ Prometheus 模式遵循以下语法：`<metric name>{<label name>="<label value>", ...} == <value>`。每个Prometheus 模式组件（指标、标签名称、标签值和指标value) 可以是用户宏或 LLD 宏。\ ^8^ Prometheus 输出如下语法：`<label name>`（可以是用户宏或 LLD 宏）如果选择 `label` 作为第二个参数。\ ^9^ 聚合函数之一：`sum`、`min`、`max`、`avg`、`count` 如果`function`被选为第二个范围。

en-us	### Item prototype preprocessing  The item prototype preprocessing object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**type**<br>(required)|integer|The preprocessing option type.<br><br>Possible values:<br>1 - Custom multiplier;<br>2 - Right trim;<br>3 - Left trim;<br>4 - Trim;<br>5 - Regular expression matching;<br>6 - Boolean to decimal;<br>7 - Octal to decimal;<br>8 - Hexadecimal to decimal;<br>9 - Simple change;<br>10 - Change per second;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - In range;<br>14 - Matches regular expression;<br>15 - Does not match regular expression;<br>16 - Check for error in JSON;<br>17 - Check for error in XML;<br>18 - Check for error using regular expression;<br>19 - Discard unchanged;<br>20 - Discard unchanged with heartbeat;<br>21 - JavaScript;<br>22 - Prometheus pattern;<br>23 - Prometheus to JSON;<br>24 - CSV to JSON;<br>25 - Replace;<br>26 - Check unsupported;<br>27 - XML to JSON.| |**params**<br>(required)|string|Additional parameters used by preprocessing option. Multiple parameters are separated by LF (\\n) character.| |**error\_handler**<br>(required)|integer|Action type used in case of preprocessing step failure.<br><br>Possible values:<br>0 - Error message is set by Zabbix server;<br>1 - Discard value;<br>2 - Set custom value;<br>3 - Set custom error message.| |**error\_handler\_params**<br>(required)|string|Error handler parameters. Used with `error_handler`.<br><br>Must be empty, if `error_handler` is 0 or 1.<br>Can be empty if, `error_handler` is 2.<br>Cannot be empty, if `error_handler` is 3.|  The following parameters and error handlers are supported for each preprocessing type.  |Preprocessing type|Name|Parameter 1|Parameter 2|Parameter 3|Supported error handlers| |------------------|----|-----------|-----------|-----------|------------------------| |1|Custom multiplier|number^1,\ 6^|<|<|0, 1, 2, 3| |2|Right trim|list of characters^2^|<|<|<| |3|Left trim|list of characters^2^|<|<|<| |4|Trim|list of characters^2^|<|<|<| |5|Regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |6|Boolean to decimal|<|<|<|0, 1, 2, 3| |7|Octal to decimal|<|<|<|0, 1, 2, 3| |8|Hexadecimal to decimal|<|<|<|0, 1, 2, 3| |9|Simple change|<|<|<|0, 1, 2, 3| |10|Change per second|<|<|<|0, 1, 2, 3| |11|XML XPath|path^4^|<|<|0, 1, 2, 3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|In range|min^1,\ 6^|max^1,\ 6^|<|0, 1, 2, 3| |14|Matches regular expression|pattern^3^|<|<|0, 1, 2, 3| |15|Does not match regular expression|pattern^3^|<|<|0, 1, 2, 3| |16|Check for error in JSON|path^4^|<|<|0, 1, 2, 3| |17|Check for error in XML|path^4^|<|<|0, 1, 2, 3| |18|Check for error using regular expression|pattern^3^|output^2^|<|0, 1, 2, 3| |19|Discard unchanged|<|<|<|<| |20|Discard unchanged with heartbeat|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|Prometheus pattern|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus to JSON|pattern^6,\ 7^|<|<|0, 1, 2, 3| |24|CSV to JSON|character^2^|character^2^|0,1|0, 1, 2, 3| |25|Replace|search string^2^|replacement^2^|<|<| |26|Check unsupported|<|<|<|1, 2, 3| |27|XML to JSON|<|<|<|0, 1, 2, 3|  ^1^ integer or floating-point number\ ^2^ string\ ^3^ regular expression\ ^4^ JSONPath or XML XPath\ ^5^ positive integer (with support of time suffixes, e.g. 30s, 1m, 2h, 1d)\ ^6^ user macro, LLD macro\ ^7^ Prometheus pattern following the syntax: `<metric name>{<label name>="<label value>", ...} == <value>`. Each Prometheus pattern component (metric, label name, label value and metric value) can be user macro or LLD macro.\ ^8^ Prometheus output following the syntax: `<label name>` (can be a user macro or an LLD macro) if `label` is selected as the second parameter.\ ^9^ One of the aggregation functions: `sum`, `min`, `max`, `avg`, `count` if `function` is selected as the second parameter.
zh-cn	 ### 监控项原型预处理  监控项原型预处理对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|----------------------------------------------------|------------| |**type**<br>（必需）|integer|预处理选项类型。<br><br>可能的值：<br>1 - 自定义乘数；<br>2 - 右修剪；<br>3 -左修剪;<br>4 - 修剪;<br>5 - 正则表达式匹配;<br>6 - 布尔转十进制;<br>7 - 八进制转十进制;<br>8 - 十六进制转十进制;<br>9 - 简单更改;<br>10 - 每秒更改;<br>11 - XML XPath;<br>12 - JSONPath;<br>13 - 在范围内;<br>14 - 匹配正则表达式;<br>15 -不匹配正则表达式；<br>16 - 检查 JSON 中的错误；<br>17 - 检查 XML 中的错误；<br>18 - 使用正则表达式检查错误；<br>19 - 丢弃未更改的内容；<br >20 - 丢弃未更改的心跳；<br>21 - JavaScript；<br>22 - Prometheus 模式；<br>23 - Prometheus 到 JSON；<br>24 - CSV 到 JSON；<br>25 - 替换；<br >26 - 检查不支持；<br>27 - XML 到 JSON。| |**params**<br>（必需）|string|预处理选项使用的附加参数。多个参数由 LF (\\n) 字符分隔。| |**error\_handler**<br>（必需）|integer|在预处理步骤失败的情况下使用的操作类型。<br><br>可能的值：<br>0 - 错误消息由 Zabbix server设置；<br>1 - 丢弃值；<br>2 - 设置自定义值；<br>3 - 设置自定义错误消息。| |**error\_handler\_params**<br>（必需）|string|错误处理程序参数。与 `error_handler` 一起使用。<br><br>如果 `error_handler` 为 0 或 1，则必须为空。<br>如果 `error_handler` 为 2，则可以为空。<br>如果`error_handler`为3，则不能为空。|  每个都支持以下参数和错误处理程序 预处理类型。  |预处理类型|名称|参数 1|参数 2|参数 3|支持的错误处理程序| |-------|----|-----------|-----------|-----------|------------| |1|自定义乘数|number^1,\ 6^|<|<|0, 1, 2, 3| |2|右修剪|list of characters^2^|<|<|<| |3|左修剪|list of characters^2^|<|<|<| |4|修剪|list of characters^2^|<|<|<| |5|正则表达式|pattern^3^|output^2^|<|0,1,2,3| |6|布尔转十进制|<|<|<|0,1,2,3| |7|八进制转十进制|<|<|<|0, 1, 2, 3| |8|十六进制转十进制|<|<|<|0,1,2,3| |9|简单更改|<|<|<|0,1,2,3| |10|每秒变化|<|<|<|0,1,2,3| |11|XML XPath|path^4^|<|<|0,1,2,3| |12|JSONPath|path^4^|<|<|0, 1, 2, 3| |13|在范围内|min^1,\6^|max^1,\6^|<|0,1,2,3| |14|匹配正则表达式|pattern^3^|<|<|0,1,2,3| |15|不匹配正则表达式|pattern^3^|<|<|0,1,2,3| |16|检查 JSON 中的错误|path^4^|<|<|0, 1, 2, 3| |17|检查 XML 中的错误|path^4^|<|<|0, 1, 2, 3| |18|使用正则表达式检查错误|pattern^3^|output^2^|<|0,1,2,3| |19|原封不动地丢弃|<|<|<|<| |20|用心跳不改变丢弃|seconds^5,\ 6^|<|<|<| |21|JavaScript|script^2^|<|<|<| |22|普罗米修斯模式|pattern^6,\ 7^|`value`, `label`, `function`|output^8,\ 9^|0, 1, 2, 3| |23|Prometheus 转 JSON|pattern^6,\ 7^|<|<|0,1,2,3| |24|CSV 转 JSON|character^2^|character^2^|0,1|0,1,2,3| |25|替换|search string^2^|replacement^2^|<|<| |26|检查不支持|<|<|<|1,2,3| |27|XML 转 JSON|<|<|<|0, 1, 2, 3|  ^1^ 整数或浮点数\ ^2^ 字符串\ ^3^ 正则表达式\ ^4^ JSONPath 或 XML XPath\ ^5^ 正整数（支持时间后缀，例如 30s、1m、2h、1d)\ ^6^ 用户宏，LLD 宏\ ^7^ Prometheus 模式遵循以下语法：`<metric name>{<label name>="<label value>", ...} == <value>`。每个Prometheus 模式组件（指标、标签名称、标签值和指标value) 可以是用户宏或 LLD 宏。\ ^8^ Prometheus 输出如下语法：`<label name>`（可以是用户宏或 LLD 宏）如果选择 `label` 作为第二个参数。\ ^9^ 聚合函数之一：`sum`、`min`、`max`、`avg`、`count` 如果`function`被选为第二个范围。

en-us	#### Item prototypes  The following screenshot illustrates how we can use these macros in item prototypes:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_snmp.png)  Again, creating as many item prototypes as needed:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototypes_snmp.png)
zh-cn	#### 监控项原型  下面的截图演示了如何在监控项原型中使用宏:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_snmp.png)  创建所需的监控项原型，数量不限:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototypes_snmp.png)

en-us	### Item prototype tag  The item prototype tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Item prototype tag name.| |value|string|Item prototype tag value.|
zh-cn	### 监控项原型标签  监控项原型标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必需)|string|监控项原型标签名字。| |value|string|监控项原型标签值。|

en-us	### Item prototype tag  The item prototype tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Item prototype tag name.| |value|string|Item prototype tag value.|
zh-cn	### 监控项原型标签  监控项原型标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>(必需)|string|监控项原型标签名字。| |value|string|监控项原型标签值。|

en-us	### Item prototype  The item prototype object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |itemid|string|*(readonly)* ID of the item prototype.| |**delay**<br>(required)|string|Update interval of the item prototype. Accepts seconds or a time unit with suffix (30s,1m,2h,1d).<br>Optionally one or more [custom intervals](/manual/config/items/item/custom_intervals) can be specified either as flexible intervals or scheduling.<br>Multiple intervals are separated by a semicolon.<br>User macros and LLD macros may be used. A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.<br>Flexible intervals may be written as two macros separated by a forward slash (e.g. `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br>Optional for Zabbix trapper, dependent items and for Zabbix agent (active) with `mqtt.get` key.| |**hostid**<br>(required)|string|ID of the host that the item prototype belongs to.<br><br>For update operations this field is *readonly*.| |**ruleid**<br>(required)|string|ID of the LLD rule that the item belongs to.<br><br>For update operations this field is *readonly*.| |**interfaceid**<br>(required)|string|ID of the item prototype's host interface. Used only for host item prototypes.<br><br>Not required for Zabbix agent (active), Zabbix internal, Zabbix trapper, calculated, dependent, database monitor and script item prototypes. Optional for HTTP agent item prototypes.| |**key\_**<br>(required)|string|Item prototype key.| |**name**<br>(required)|string|Name of the item prototype.| |**type**<br>(required)|integer|Type of the item prototype.<br><br>Possible values:<br>0 - Zabbix agent;<br>2 - Zabbix trapper;<br>3 - simple check;<br>5 - Zabbix internal;<br>7 - Zabbix agent (active);<br>10 - external check;<br>11 - database monitor;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - TELNET agent;<br>15 - calculated;<br>16 - JMX agent;<br>17 - SNMP trap;<br>18 - Dependent item;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - Script.| |**url**<br>(required)|string|URL string required only for HTTP agent item prototypes. Supports LLD macros, user macros, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(required)|integer|Type of information of the item prototype.<br><br>Possible values:<br>0 - numeric float;<br>1 - character;<br>2 - log;<br>3 - numeric unsigned;<br>4 - text.| |allow\_traps|integer|HTTP agent item prototype field. Allow to populate value as in trapper item type also.<br><br>0 - *(default)* Do not allow to accept incoming data.<br>1 - Allow to accept incoming data.| |authtype|integer|Used only by SSH agent item prototypes or HTTP agent item prototypes.<br><br>SSH agent authentication method possible values:<br>0 - *(default)* password;<br>1 - public key.<br><br>HTTP agent authentication method possible values:<br>0 - *(default)* none<br>1 - basic<br>2 - NTLM<br>3 - Kerberos| |description|string|Description of the item prototype.| |follow\_redirects|integer|HTTP agent item prototype field. Follow response redirects while pooling data.<br><br>0 - Do not follow redirects.<br>1 - *(default)* Follow redirects.| |headers|object|HTTP agent item prototype field. Object with HTTP(S) request headers, where header name is used as key and header value as value.<br><br>Example:<br>{ "User-Agent": "Zabbix" }| |history|string|A time unit of how long the history data should be stored. Also accepts user macro and LLD macro.<br><br>Default: 90d.| |http\_proxy|string|HTTP agent item prototype field. HTTP(S) proxy connection string.| |ipmi\_sensor|string|IPMI sensor. Used only by IPMI item prototypes.| |jmx\_endpoint|string|JMX agent custom connection string.<br><br>Default value:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |logtimefmt|string|Format of the time in log entries. Used only by log item prototypes.| |master\_itemid|integer|Master item ID.<br>Recursion up to 3 dependent items and item prototypes and maximum count of dependent items and item prototypes equal to 29999 are allowed.<br><br>Required by Dependent items.| |output\_format|integer|HTTP agent item prototype field. Should response be converted to JSON.<br><br>0 - *(default)* Store raw.<br>1 - Convert to JSON.| |params|string|Additional parameters depending on the type of the item prototype:<br>- executed script for SSH and Telnet item prototypes;<br>- SQL query for database monitor item prototypes;<br>- formula for calculated item prototypes.| |parameters|array|Additional parameters for script item prototypes. Array of objects with 'name' and 'value' properties, where name must be unique.| |password|string|Password for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent item prototypes.| |post\_type|integer|HTTP agent item prototype field. Type of post data body stored in posts property.<br><br>0 - *(default)* Raw data.<br>2 - JSON data.<br>3 - XML data.| |posts|string|HTTP agent item prototype field. HTTP(S) request body data. Used with post\_type.| |privatekey|string|Name of the private key file.| |publickey|string|Name of the public key file.| |query\_fields|array|HTTP agent item prototype field. Query parameters. Array of objects with 'key':'value' pairs, where value can be empty string.| |request\_method|integer|HTTP agent item prototype field. Type of request method.<br><br>0 - *(default)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP agent item prototype field. What part of response should be stored.<br><br>0 - *(default)* Body.<br>1 - Headers.<br>2 - Both body and headers will be stored.<br><br>For request\_method HEAD only 1 is allowed value.| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP agent item prototype field. Public SSL Key file path.| |ssl\_key\_file|string|HTTP agent item prototype field. Private SSL Key file path.| |ssl\_key\_password|string|HTTP agent item prototype field. Password for SSL Key file.| |status|integer|Status of the item prototype.<br><br>Possible values:<br>0 - *(default)* enabled item prototype;<br>1 - disabled item prototype;<br>3 - unsupported item prototype.| |status\_codes|string|HTTP agent item prototype field. Ranges of required HTTP status codes separated by commas. Also supports user macros or LLD macros as part of comma separated list.<br><br>Example: 200,200-{$M},{$M},200-400| |templateid|string|(readonly) ID of the parent template item prototype.| |timeout|string|Item data polling request timeout. Used for HTTP agent and script item prototypes. Supports user macros and LLD macros.<br><br>default: 3s<br>maximum value: 60s| |trapper\_hosts|string|Allowed hosts. Used by trapper item prototypes or HTTP item prototypes.| |trends|string|A time unit of how long the trends data should be stored. Also accepts user macro and LLD macro.<br><br>Default: 365d.| |units|string|Value units.| |username|string|Username for authentication. Used by simple check, SSH, Telnet, database monitor, JMX and HTTP agent item prototypes.<br><br>Required by SSH and Telnet item prototypes.| |uuid|string|Universal unique identifier, used for linking imported item prototypes to already existing ones. Used only for item prototypes on templates. Auto-generated, if not given.<br><br>For update operations this field is *readonly*.| |valuemapid|string|ID of the associated value map.| |verify\_host|integer|HTTP agent item prototype field. Validate host name in URL is in Common Name field or a Subject Alternate Name field of host certificate.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.<br>| |verify\_peer|integer|HTTP agent item prototype field. Validate is host certificate authentic.<br><br>0 - *(default)* Do not validate.<br>1 - Validate.| |discover|integer|Item prototype discovery status.<br><br>Possible values:<br>0 - *(default)* new items will be discovered;<br>1 - new items will not be discovered and existing items will be marked as lost.|  Note that for some methods (update, delete) the required/optional parameter combination is different.
zh-cn	### 监控项原型  监控项原型对象具有以下属性。   |属性|[类型](/manual/api/reference_commentary#数据类型)|描述| |--------|---------------------------------------------------|-----------| |itemid|string|*(只读)* 监控项原型的ID| |**delay**<br>(必需)|string|监控项原型的更新间隔。接受秒或带有后缀的时间单位(30s,1m,2h,1d)。<br>可灵活的指定一个或多个时间间隔[自定义间隔](/manual/config/items/item/custom_intervals)或计划， <br>多个间隔用分号分割。<br>可以使用用户宏和LLD宏. 一个宏必须填充整个字段. 不支持字段中的多个宏或与文本混合的宏.<br>灵活的间隔可以写成两个用正斜杠分隔的宏 (例如 `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`).<br><br>Zabbix 采集器, 相关项监控和Zabbix agent (主动)可选 `mqtt.get` key。| |**hostid**<br>(必需)|string|监控项原型的主机ID.<br><br>对于更新操作，此字段为*只读*。| |**ruleid**<br>(必需)|string|监控项所属的LLD规则的ID.<br><br>对于更新操作，此字段为*只读*。| |**interfaceid**<br>(必需)|string|监控项原型的主机接口的ID。 仅用于监控项原型。<br><br>对于Zabbix agent (主动), Zabbix 内部检查, Zabbix 采集器,相关项监控, 数据库监控项和可计算监控项原型是可选的。| |**key**<br>(必需)|string|监控项原型key.| |**name**<br>(必需)|string|监控项原型名字。| |**type**<br>(必需)|integer|监控项原型类型.<br><br>可选值:<br>0 - Zabbix agent;<br>2 - Zabbix 采集器;<br>3 - 简单检查;<br>5 - Zabbix 内部检查;<br>7 - Zabbix agent (主动);<br>10 - 外部检查;<br>11 - 数据库监控;<br>12 - IPMI agent;<br>13 - SSH agent;<br>14 - TELNET agent;<br>15 - 可计算的监控;<br>16 - JMX agent;<br>17 - SNMP trap;<br>18 - 相关项监控;<br>19 - HTTP agent;<br>20 - SNMP agent;<br>21 - 脚本.| |**url**<br>(必需)|string|URL仅用于HTTP agent监控项原型. 支持 LLD宏,用户宏, {HOST.IP}, {HOST.CONN}, {HOST.DNS}, {HOST.HOST}, {HOST.NAME}, {ITEM.ID}, {ITEM.KEY}.| |**value\_type**<br>(必需)|integer|监控项原型的值的类型<br><br>可选项:<br>0 - 浮点值;<br>1 - 字符串;<br>2 - 日志;<br>3 - 无符号整数;<br>4 - 文本。| |allow\_traps|integer|HTTP客户端监控项原型字段. 允许采集器监控项类型填充值。<br><br>0 - *(默认值)* 不允许接受传入数据、<br>1 - 允许接受传入数据。| |authtype|integer|仅允许SSH客户端监控项原型或者HTTP客户端监控项原型。<br><br>SSH客户端验证方法可选值:<br>0 - *(默认值)* 密码;<br>1 - 秘钥.<br><br>HTTP客户端验证方法可选值:<br>0 - *(默认值)* none<br>1 - basic<br>2 - NTLM<br>3 - Kerberos| |description|string|监控项原型的描述.| |follow\_redirects|integer|HTTP客户端监控现原型字段。数据重定向.<br><br>0 - 不要重定向。<br>1 - *(默认值)* 重定向。| |headers|object|HTTP客户端监控现原型字段。 HTTP（S）请求头的对象，其中，头部名称用作键，头部值用作值.<br><br>示例:<br>{ "User-Agent": "Zabbix" }| |history|string|历史数据的保存时间。可接受用户宏和LLD宏。<br><br>默认值: 90d.| |http\_proxy|string|HTTP客户端监控现原型字段。 HTTP(S) 代理地址字符串.| |ipmi\_sensor|string|IPMI传感器. 仅用于IPMI监控现原型.| |jmx\_endpoint|string|JMX客户端连接地址。<br><br>默认值:<br>service:jmx:rmi:///jndi/rmi://{HOST.CONN}:{HOST.PORT}/jmxrmi| |logtimefmt|string|日志条目中的时间格式。仅由日志监控项原型使用。| |master\_itemid|integer|主监控项ID.<br>最多可递归3个相关监控项目和监控项目原型，且相关监控项和监控项原型的最大计数等于29999。| |output\_format|integer|HTTP客户端监控项原型字段。可将响应内容转换为JSON<br><br>0 - *(默认值)* 原始数据.<br>1 - 转JSON.| |params|string|其他参数取决于监控项原型的类型:<br>- SSH和Telnet监控项原型的执行脚本;<br>- 数据库监控项原型的sql查询;<br>- 可计算监控项目原型的公式。| |parameters|array|脚本监控项原型的其他参数。具有“名称”和“值”属性的对象数组，其中名称必须唯一。| |password|string|验证密码。用于简单检查、SSH、Telnet、数据库监控项、JMX和HTTP客户端监控项原型。| |post\_type|integer|HTTP客户端监控现原型字段。 posts属性中存储的post数据体的类型。<br><br>0 - *(默认值)* Raw数据。<br>2 - JSON数据。<br>3 - XML数据。| |posts|string|HTTP客户端监控项原型字段。HTTP(S)请求内容. 使用post类型.| |privatekey|string|私钥文件的名称。| |publickey|string|公钥文件的名称。| |query\_fields|array|HTTP客户端监控项原型字段。 查询参数。具有“键”：“值”对的对象数组，其中值可以是空字符串。| |request\_method|integer|HTTP客户端监控项原型字段。请求方法的类型。<br><br>0 - *(默认值)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP客户端监控项原型字段。 响应返数据的哪一部分。<br><br>0 - *(默认值)* Body.<br>1 - Headers.<br>2 - body和headers.<br><br>值为1时，返回request的HEAD。| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP代理监控项原型字段。公共SSL密钥文件路径。| |ssl\_key\_file|string|HTTP代理监控项原型字段。私有SSL密钥文件路径。| |ssl\_key\_password|string|HTTP代理监控项原型字段。 SSL密钥文件的密码。| |status|integer|监控项原型状态。<br><br>可选值:<br>0 - *(默认值)* 激活监控项原型;<br>1 - 禁用监控项原型;<br>3 - 不支持监控项原型.| |status\_codes|string|HTTP代理监控项原型字段。 指定HTTP状态码范围以，分隔。还支持用户宏或LLD宏作为逗号分隔列表的一部分。<br><br>例如: 200,200-{$M},{$M},200-400| |templateid|string|监控项原型的模板（只读）id.| |timeout|string|监控项数据轮询请求超时。用于HTTP代理和脚本监控项原型. 支持用户宏或LLD宏。<br><br>默认值: 3s<br>最小值: 60s| |trapper\_hosts|string|允许的主机。 用于采集器监控项原型或者HTTP监控现原型.| |trends|string|趋势数据存储多长时间。还接受用户宏和LLD宏。<br><br>默认值: 365d.| |units|string|值的单位。| |username|string|验证的用户名. 用于简单检查、SSH、Telnet、数据库监控项、JMX和HTTP代理监控项原型。<br><br>SSH和Telnet监控项目原型需要。| |uuid|string|通用唯一标识符，用于将导入的监控项目原型链接到现有的监控项目原型。仅用于模板上的监控项原型。如果没有给出则自动生成。<br><br>对于更新操作，此字段为*只读*.| |valuemapid|string|关联值映射值的ID.| |verify\_host|integer|HTTP代理监控项原型字段。 验证URL中的主机名位于主机证书的公用名字段或使用者备用名字段中.<br><br>0 - *(默认值)* 不验证.<br>1 - 验证.<br>| |verify\_peer|integer|HTTP代理监控项原型字段。 验证主机证书是否真实.<br><br>0 - *(默认值)* 不验证.<br>1 - 验证.| |discover|integer|监控项原型自动发现状态.<br><br>可选值:<br>0 - *(默认值)* 新监控项目将被发现;<br>1 - 新项目将不会被发现，现有项目将被标记为丢失。| 注意，对于某些方法（更新、删除），必需/可选参数组合是不同的。

en-us	# Item prototype  This class is designed to work with item prototypes.  Object references:\  -   [Item     prototype](/manual/api/reference/itemprototype/object#item_prototype)  Available methods:\  -   [itemprototype.create](/manual/api/reference/itemprototype/create) -     creating new item prototypes -   [itemprototype.delete](/manual/api/reference/itemprototype/delete) -     deleting item prototypes -   [itemprototype.get](/manual/api/reference/itemprototype/get) -     retrieving item prototypes -   [itemprototype.update](/manual/api/reference/itemprototype/update) -     updating item prototypes
zh-cn	#  监控项原型  此类用于管理监控项原型。  对象引用:\  -   [监控项原型](/manual/api/reference/itemprototype/object#监控项原型)  可用的方法:\  -   [itemprototype.create](/manual/api/reference/itemprototype/create) 创建监控项原型 -   [itemprototype.delete](/manual/api/reference/itemprototype/delete) 删除监控项原型 -   [itemprototype.get](/manual/api/reference/itemprototype/get) 搜索监控项原型 -   [itemprototype.update](/manual/api/reference/itemprototype/update) 更新监控项原型

en-us	# itemprototype.update
zh-cn	# 更新监控项原型

en-us	##### Item prototype  You may want to create an item prototype like this:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom.png)  with preprocessing options:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom_b.png)
zh-cn	##### 监控项原型  可以创建这样的监控项原型:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom.png)  并配置预处理选项:  ![](../../../../../assets/en/manual/discovery/low_level_discovery/lld_item_prototype_prom_b.png)

en-us	#### Items  Define items to monitor.  [Item API](/manual/api/reference/item)
zh-cn	#### 监控项  定义要监控的监控项。  [Item API](/manual/api/reference/item)

en-us	#### Items  To configure querying of internal stats on another Zabbix instance, you may use two items:  -   `zabbix[stats,<ip>,<port>]` internal item - for direct remote     queries of Zabbix server/proxy. <ip> and <port> are used     to identify the target instance. -   `zabbix.stats[<ip>,<port>]` agent item - for agent-based remote     queries of Zabbix server/proxy. <ip> and <port> are used     to identify the target instance.  See also: [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)  The following diagram illustrates the use of either item depending on the context.  ![](../../../../assets/en/manual/appendix/items/ext_stats.png)  -   ![](../../../../assets/en/manual/appendix/items/green.png) - Server     → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/pink.png) - Server →     proxy → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/blue.png) - Server →     agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/red.png) - Server →     proxy → agent → external Zabbix instance     (`zabbix.stats[<ip>,<port>]`)  To make sure that the target instance allows querying it by the external instance, list the address of the external instance in the 'StatsAllowedIP' parameter on the target instance.
zh-cn	 #### 监控项  要在另一个Zabbix实例上配置内部统计信息的查询，可以使用两项：  -   `zabbix[stats,<ip>,<port>]`  内部监控项 - 用于直接远程查询Zabbix server/proxy。<ip>和<port>用于标识目标实例。 -   `zabbix.stats[<ip>,<port>]`  Agent监控项 - 用于基于代理的Zabbix server/proxy的远程查询。<ip>和<port>用于标识目标实例。  另请参见:   [Internal items](/manual/config/items/itemtypes/internal), [Zabbix agent items](/manual/config/items/itemtypes/zabbix_agent)  下图根据上下文说明了这两个项的用法。  ![](../../../../assets/en/manual/appendix/items/ext_stats.png)  -   ![](../../../../assets/en/manual/appendix/items/green.png) - Server     → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/pink.png) - Server →     proxy → external Zabbix instance (`zabbix[stats,<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/blue.png) - Server →     agent → external Zabbix instance (`zabbix.stats[<ip>,<port>]`) -   ![](../../../../assets/en/manual/appendix/items/red.png) - Server →     proxy → agent → external Zabbix instance     (`zabbix.stats[<ip>,<port>]`)  要确保目标实例允许外部实例查询它，请在目标实例的“StatsAllowedIP”参数中列出外部实例的地址。

en-us	### Item tag  The item tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |**tag**<br>(required)|string|Item tag name.| |value|string|Item tag value.|
zh-cn	### 监控项标签  监控项标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>（必需）|string|监控项标签名称。| |value|string|监控项标签值。|

en-us	### Item tag  The item tag object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--------|---------------------------------------------------|-----------| |**tag**<br>(required)|string|Item tag name.| |value|string|Item tag value.|
zh-cn	### 监控项标签  监控项标签对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |**tag**<br>（必需）|string|监控项标签名称。| |value|string|监控项标签值。|

en-us	# Item  This class is designed to work with items.  Object references:\  -   [Item](/manual/api/reference/item/object#item)  Available methods:\  -   [item.create](/manual/api/reference/item/create) - creating new     items -   [item.delete](/manual/api/reference/item/delete) - deleting items -   [item.get](/manual/api/reference/item/get) - retrieving items -   [item.update](/manual/api/reference/item/update) - updating items
zh-cn	# 监控项  此部分旨在介绍如何对监控项进行操作。  引用对象：  -   [监控项](/manual/api/reference/item/object#item)  可用方法：  -   [创建](/manual/api/reference/item/create) - 创建新监控项 -   [删除](/manual/api/reference/item/delete) - 删除监控项 -   [检索](/manual/api/reference/item/get) - 检索监控项 -   [更新](/manual/api/reference/item/update) - 更新监控项

en-us	##### Item  To begin with, you may want to set up an item that monitors a log file, for example:      log[/var/log/syslog]  ![](../../../../assets/en/manual/config/event_correlation/correlation_item.png)  With the item set up, wait a minute for the configuration changes to be picked up and then go to [Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data) to make sure that the item has started collecting data.
zh-cn	##### 监控项  首先，你可能想设置一个监控日志文件的监控项，例如：      log[/var/log/syslog]  ![](../../../../assets/en/manual/config/event_correlation/correlation_item.png)  设置监控项后，等待一分钟，等待配置更改，然后去[最新数据](/manual/web_interface/frontend_sections/monitoring/latest_data)  确认该监控项已经开始收集数据。

en-us	# item.update
zh-cn	# 更新

en-us	##### Item value  An *Item value* widget has been added to dashboard widgets.   This type of widget is useful for displaying values of  single items prominently. Different visual styles of display  are possible:  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets_new.png)  For more information, see [Item value widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value).
zh-cn	##### 监控项值  *监控项值（Item value）*小部件被添加到仪表盘小部件中。  这种类型的小部件对于突出显示单个监控项的值很有用。不同的视觉风格的显示成为可能：  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets_new.png)  有关详细信息，请参阅 [Item value 小部件](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value)。

en-us	##### Item value preprocessing  The **Preprocessing** tab allows to define [transformation rules](/manual/config/items/preprocessing) for the received values.
zh-cn	##### 监控项值预处理   **预处理** 选项卡允许为接收到的值定义[转换规则](/zh/manual/config/items/preprocessing) 。

en-us	#### Item value preprocessing  To visualize the data preprocessing process, we can use the following simplified diagram:  ![](../../../../../assets/en/manual/appendix/items/preprocessing_simplified.png)  The diagram above shows only processes, objects and main actions related to item value preprocessing in a **simplified** form. The diagram does not show conditional direction changes, error handling or loops. Only one preprocessing worker is shown on this diagram (multiple preprocessing workers can be used in real-life scenarios), only one item value is being processed and we assume that this item requires to execute at least one preprocessing step. The aim of this diagram is to show the idea behind item value preprocessing pipeline.  -   Item data and item value is passed to preprocessing manager using     socket-based IPC mechanism. -   Item is placed in the preprocessing queue.  ::: noteclassic Item can be placed at the end or at the beginning of the preprocessing queue. Zabbix internal items are always placed at the beginning of preprocessing queue, while other item types are enqueued at the end. :::  -   At this point data flow stops until there is at least one unoccupied     (that is not executing any tasks) preprocessing worker. -   When preprocessing worker is available, preprocessing task is being     sent to it. -   After preprocessing is done (both failed and successful execution of     preprocessing steps), preprocessed value is being passed back to     preprocessing manager. -   Preprocessing manager converts result to desired format (defined by     item value type) and places result in preprocessing queue. If there     are dependent items for current item, then dependent items are added     to preprocessing queue as well. Dependent items are enqueued in     preprocessing queue right after the master item, but only for master     items with value set and not in NOT SUPPORTED state.
zh-cn	#### 监控项值预处理  为了可视化数据预处理过程，我们使用下面的简化图来展示：  ![](../../../../../assets/en/manual/appendix/items/preprocessing_simplified.png)  上图仅以**简化**形式显示了与监控项值预处理相关的流程、对象和主要操作。 该图没有显示有条件的方向变化、错误处理或循环。 这张图只显示了一个预处理进程（在现实生活中可以使用多个预处理进程），只处理一个监控项值，我们假设该监控项需要执行至少一个预处理步骤。 此图的目的是展示监控项值预处理管道背后的理念。  -    使用基于套接字的 IPC 机制将监控项数据和监控项值传递给预处理管理器。 -    监控项被放置在预处理队列中。  ::: noteclassic 监控项可以放在预处理队列的末尾或开头。 Zabbix 内部监控项总是放在预处理队列的开头，而其他监控项类型在最后排队。 :::  -    此时数据流停止，直到至少有一个未占用（即不执行任何任务）预处理进程。 -    当预处理进程可用时，将向它发送预处理任务。 -    预处理完成后（预处理步骤执行失败或成功），预处理值被传递回预处理管理器。 -    预处理管理器将结果转换为所需格式（由监控项值类型定义）并将结果放入预处理队列。 如果当前监控项有依赖项，则依赖项也将添加到预处理队列中。 依赖项在主要监控项之后的预处理队列中排队，但仅适用于有值设置且不处于不支持状态的主要监控项。

en-us	#### Item value processing  To visualize the data flow from data source to the Zabbix database, we can use the following simplified diagram:  ![](../../../../../assets/en/manual/appendix/items/overall_pic.png)  The diagram above shows only processes, objects and actions related to item value processing in a **simplified** form. The diagram does not show conditional direction changes, error handling or loops. Local data cache of preprocessing manager is not shown either because it doesn't affect data flow directly. The aim of this diagram is to show processes involved in item value processing and the way they interact.  -   Data gathering starts with raw data from a data source. At this     point, data contains only ID, timestamp and value (can be multiple     values as well) -   No matter what type of data gatherer is used, the idea is the same     for active or passive checks, for trapper items and etc, as it only     changes the data format and the communication starter (either data     gatherer is waiting for a connection and data, or data gatherer     initiates the communication and requests the data). Raw data is     validated, item configuration is retrieved from configuration cache     (data is enriched with the configuration data). -   Socket-based IPC mechanism is used to pass data from data gatherers     to preprocessing manager. At this point data gatherer continue to     gather data without waiting for the response from preprocessing     manager. -   Data preprocessing is performed. This includes execution of     preprocessing steps and dependent item processing.  ::: noteclassic Item can change its state to NOT SUPPORTED while preprocessing is performed if any of preprocessing steps fail. :::  -   History data from local data cache of preprocessing manager is being     flushed into history cache. -   At this point data flow stops until the next synchronization of     history cache (when history syncer process performs data     synchronization). -   Synchronization process starts with data normalization storing data     in Zabbix database. Data normalization performs conversions to     desired item type (type defined in item configuration), including     truncation of textual data based on predefined sizes allowed for     those types (HISTORY\_STR\_VALUE\_LEN for string,     HISTORY\_TEXT\_VALUE\_LEN for text and HISTORY\_LOG\_VALUE\_LEN for     log values). Data is being sent to Zabbix database after     normalization is done.  ::: noteclassic Item can change its state to NOT SUPPORTED if data normalization fails (for example, when textual value cannot be converted to number). :::  -   Gathered data is being processed - triggers are checked, item     configuration is updated if item becomes NOT SUPPORTED, etc. -   This is considered the end of data flow from the point of view of     item value processing.
zh-cn	#### 监控项值预处理  为了可视化从数据源到 Zabbix 数据库的数据流，我们可以使用下面的简化图：  ![](../../../../../assets/en/manual/appendix/items/overall_pic.png)  上图仅以**简化**形式显示了与监控项值处理相关的流程、对象和操作。 该图没有显示有条件的方向变化、错误处理或循环。 预处理管理器的本地数据缓存也没有显示，因为它不直接影响数据流。 此图的目的是显示监控项价值处理中涉及的流程及其交互方式。  - 数据收集从数据源的原始数据开始。 此时数据只包含ID、时间戳和值（也可以是多个值） - 无论使用哪种类型的数据收集器，对于主动或被动检查、陷阱监控项等的想法都是相同的，因为它只更改数据格式和通信启动器（任何一个数据收集器都在等待连接和数据 ，或数据收集器发起通信并请求数据）。 验证原始数据，从配置缓存中检索监控项配置（使用配置数据丰富数据）。 - 基于套接字的 IPC 机制用于将数据从数据收集器传递到预处理管理器。 此时数据收集器继续收集数据，无需等待预处理管理器的响应。 - 执行数据预处理。 这包括执行预处理步骤和依赖项处理。  ::: noteclassic 如果任何预处理步骤失败，则在执行预处理时，监控项可以将其状态更改为不支持。 :::  - 来自预处理管理器的本地数据缓存的历史数据正在刷新到历史缓存中。 - 此时数据流停止，直到历史缓存的下一次同步（当历史同步器进程执行数据同步时）。 - 同步过程从数据规范化开始，将数据存储在 Zabbix 数据库中。 数据规范化执行到所需监控项类型（监控项配置中定义的类型）的转换，包括基于这些类型允许的预定义大小截断文本数据（HISTORY\_STR\_VALUE\_LEN 用于字符串，HISTORY\_TEXT\_VALUE\_LEN 用于文本和 HISTORY\_LOG\_VALUE\_LEN 用于日志值）。 规范化完成后，数据正在发送到 Zabbix 数据库。  ::: noteclassic 如果数据规范化失败（例如，当文本值无法转换为数字时），监控项可以将其状态更改为不支持。 :::  - 正在处理收集的数据 - 检查触发器，如果监控项不支持，则更新监控项配置等。 - 从监控项值处理的角度来看，这被认为是数据流的结束。

en-us	#### Item values  The following information is exported for a collected item value:  |Field|<|Type|Description| |-|---------|---------|---------------------------| |*host*|<|object|Host name of the item host.| | |host|string|Host name.| |^|name|string|Visible host name.| |*groups*|<|array|List of host groups of the item host; there should be at least one element in array.| | |\-|string|Host group name.| |*itemid*|<|number|Item ID.| |*name*|<|string|Visible item name.| |*clock*|<|number|Number of seconds since Epoch to the moment when value was collected (integer part).| |*ns*|<|number|Number of nanoseconds to be added to `clock` to get a precise value collection time.| |*timestamp*<br>(*Log* only)|<|number|0 if not available.| |*source*<br>(*Log* only)|<|string|Empty string if not available.| |*severity*<br>(*Log* only)|<|number|0 if not available.| |*eventid*<br>(*Log* only)|<|number|0 if not available.| |*value*|<|number (for numeric items) or<br>string (for text items)|Collected item value.| |*type*|<|number|Collected value type:<br>0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text|
zh-cn	#### 监控项值  为收集的监控项值导出以下信息:  |字段|<|类型|描述| |-----|-|----|-----------| |*host*|<|object|监控项主机的主机名.| | |host|string|主机名.| | |name|string|可见的主机名.| |*groups*|<|array|监控项主机的主机组列表;数组中应至少有一个元素| | |\-|string|主机组名.| |*itemid*|<|number|监控项 ID.| |*name*|<|string|可见监控项名称.| |*clock*|<|number|收集值那一刻的时间秒数（整数部分）.| |*ns*|<|number|要添加到`clock`以获得精确收集值时间的纳秒数。| |*timestamp*<br>(*Log* only)|<|number|如果不可用，则为 0| |*source*<br>(*Log* only)|<|string|如果不可用，则为空字符串| |*severity*<br>(*Log* only)|<|number|如果不可用，则为 0| |*eventid*<br>(*Log* only)|<|number|如果不可用，则为 0| |*value*|<|number (用于数字型监控项) or<br>string (用于文本型监控项)|收集的监控项值。| |*type*|<|number|收集的值类型：<br>0 - 浮点数, 1 - 字符, 2 - 日志, 3 - 无符号数字, 4 -文本|

en-us	### Item value widget  An *Item value* widget has been added to dashboard widgets.   This type of widget is useful for displaying values of  single items prominently. Different visual styles of display  are possible:  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets_new.png)  For more information, see [Item value widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets/item_value).  
zh-cn	Macros for internal actions contain the reason why an item, an LLD-rule, or a trigger became unsupported:   - {ITEM.STATE.ERROR} - for item-based internal notifications;  - {LLDRULE.STATE.ERROR} -  for LLD-rule based internal notifications;  - {TRIGGER.STATE.ERROR} - for trigger-based internal notifications.  For more details, see [Supported macros](/manual/appendix/macros/supported_by_location).  

en-us	It is possible to zoom in and out the map by using the plus and minus buttons in the widget's upper left corner or by using the mouse scroll wheel or touchpad. To set the current view as default, right-click anywhere on the map and select *Set this view as default*. This setting will override *Initial view* widget parameter for the current user. To undo this action, right-click anywhere on the map again and select *Reset the initial view*.  When *Initial view* or *Default view* is set, you can return to this view at any time by pressing on the home icon on the left.  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget3.png)
zh-cn	通过组件左上角的加号和减号按钮或使用鼠标滚轮或触摸板来放大和缩小地图。如果需要把当前视图作为默认状态，可以在地图内任意位置点击右键，选择*Set this view as default*把当前视图设置为默认状态。此设置会覆盖当前用户的默认视图设定。通过在在地图内任意位置点击右键，选择*Reset the initial view*。功能恢复默认视图。   当设置了*初始视图*或*默认视图*时，您可通过点击左边的主页图标返回到这个视图。  ![](../../../../../../../assets/en/manual/web_interface/frontend_sections/monitoring/geomap_widget3.png)

en-us	##### Java gateway  If you obtained Zabbix from the source repository or an archive, then the necessary dependencies are already included in the source tree.  If you obtained Zabbix from your distribution's package, then the necessary dependencies are already provided by the packaging system.  In both cases above, the software is ready to be used and no additional downloads are necessary.  If, however, you wish to provide your versions of these dependencies (for instance, if you are preparing a package for some Linux distribution), below is the list of library versions that Java gateway is known to work with. Zabbix may work with other versions of these libraries, too.  The following table lists JAR files that are currently bundled with Java gateway in the original code:  |Library|License|Website|Comments| |-------|-------|-------|--------| |*logback-core-1.2.3.jar*|EPL 1.0, LGPL 2.1|<http://logback.qos.ch/>|Tested with 0.9.27, 1.0.13, 1.1.1 and 1.2.3.| |*logback-classic-1.2.3.jar*|EPL 1.0, LGPL 2.1|<http://logback.qos.ch/>|Tested with 0.9.27, 1.0.13, 1.1.1 and 1.2.3.| |*slf4j-api-1.7.30.jar*|MIT License|<http://www.slf4j.org/>|Tested with 1.6.1, 1.6.6, 1.7.6 and 1.7.30.| |*android-json-4.3\_r3.1.jar*|Apache License 2.0|<https://android.googlesource.com/platform/libcore/+/master/json>|Tested with 2.3.3\_r1.1 and 4.3\_r3.1. See src/zabbix\_java/lib/README for instructions on creating a JAR file.|  Java gateway can be built using either Oracle Java or open-source OpenJDK (version 1.6 or newer). Packages provided by Zabbix are compiled using OpenJDK. The table below provides information about OpenJDK versions used for building Zabbix packages by distribution:  |Distribution|OpenJDK version| |------------|---------------| |RHEL/CentOS 8|1.8.0| |RHEL/CentOS 7|1.8.0| |SLES 15|11.0.4| |SLES 12|1.8.0| |Debian 10|11.0.8| |Ubuntu 20.04|11.0.8| |Ubuntu 18.04|11.0.8|
zh-cn	##### Java 网关  如果您从源代码仓库或存档中获得了 Zabbix，则必要的依赖项已包含在源代码树中。  如果您从发行版的软件包中获得了Zabbix，那么打包系统已经提供了必要的依赖项。  在上述两种情况下，即可准备部署软件了，而不需要下载额外的依赖包。  但是，如果您希望提供这些依赖关系的版本（例如，如果您正在为某些 Linux 发行版准备软件包），则下面是 Java 网关已知可以使用的库的版本列表。 Zabbix 也许可以与这些库的其他版本一起使用。  下表列出了原始代码中当前与 Java 网关捆绑在一起的 JAR 文件：  |库名|许可|网站|备注| |-------|-------|-------|--------| |*logback-core-1.2.3.jar*|EPL 1.0, LGPL 2.1|<http://logback.qos.ch/>|0.9.27, 1.0.13, 1.1.1 和 1.2.3 测试通过。| |*logback-classic-1.2.3.jar*|EPL 1.0, LGPL 2.1|<http://logback.qos.ch/>|0.9.27, 1.0.13, 1.1.1 和 1.2.3 测试通过。| |*slf4j-api-1.7.30.jar*|MIT License|<http://www.slf4j.org/>|1.6.1, 1.6.6, 1.7.6 和 1.7.30 测试通过。| |*android-json-4.3\_r3.1.jar*|Apache License 2.0|<https://android.googlesource.com/platform/libcore/+/master/json>|2.3.3\_r1.1 和 4.3\_r3.1 测试通过。关于创建 JAR 文件，详见 src/zabbix\_java/lib/README 说明。|  Java网关可以使用Oracle Java或开源OpenJDK（版本1.6或更高版本）构建。Zabbix提供的软件包是使用OpenJDK编译的。下表提供了有关用于按发行版构建Zabbix软件包的OpenJDK版本的信息：  |发行版|OpenJDK 版本| |------------|---------------| |RHEL/CentOS 8|1.8.0| |RHEL/CentOS 7|1.8.0| |SLES 15|11.0.4| |SLES 12|1.8.0| |Debian 10|11.0.8| |Ubuntu 20.04|11.0.8| |Ubuntu 18.04|11.0.8|

en-us	### Java gateway installation  It is required to install [Java gateway](/manual/concepts/java) only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database.  Once the required repository is added, you can install Zabbix Java gateway by running:      # dnf install zabbix-java-gateway  Proceed to [setup](/manual/concepts/java/from_rhel_centos) for more details on configuring and running Java gateway.
zh-cn	### 安装Java gateway   仅当你想监控 JMX 应用程序时，才需要安装 [Java gateway](/manual/concepts/java)。 Java gateway 是轻量级的不需要数据库。  一旦添加了所需软件源，就可通过执行如下命令安装 Zabbix Java gateway：      # dnf install zabbix-java-gateway  了解更多关于配置和运行Java gateway的详细信息可跳转至[ java 设置](/manual/concepts/java/from_rhel_centos)。

en-us	### JavaScript methods  HTTP methods PATCH, HEAD, OPTIONS, TRACE, CONNECT have been added to the JavaScript engine. Also, the engine now allows sending custom HTTP method requests with the new JS method HttpRequest.customRequest.  See also: [Additional JavaScript objects](/manual/config/items/preprocessing/javascript/javascript_objects).
zh-cn	### JavaScript 方法  HTTP 方法 PATCH、HEAD、OPTIONS、TRACE、CONNECT 已添加到 JavaScript 引擎中。此外，引擎现在允许使用新的 JS 方法 HttpRequest.customRequest 发送自定义 HTTP 方法请求。  另请参阅：[其他 JavaScript 对象](/manual/config/items/preprocessing/javascript/javascript_objects)。

en-us	#### Jira webhook (custom)  ![](../../../../../../assets/en/manual/config/notifications/media/media_webhook_jira.png)  This script will create a JIRA issue and return some info on the created issue.  ``` {.java} try {     Zabbix.log(4, '[ Jira webhook ] Started with params: ' + value);      var result = {             'tags': {                 'endpoint': 'jira'             }         },         params = JSON.parse(value),         req = new HttpRequest(),         fields = {},         resp;      if (params.HTTPProxy) {         req.setProxy(params.HTTPProxy);     }      req.addHeader('Content-Type: application/json');     req.addHeader('Authorization: Basic ' + params.authentication);      fields.summary = params.summary;     fields.description = params.description;     fields.project = {key: params.project_key};     fields.issuetype = {id: params.issue_id};      resp = req.post('https://tsupport.zabbix.lan/rest/api/2/issue/',         JSON.stringify({"fields": fields})     );      if (req.getStatus() != 201) {         throw 'Response code: ' + req.getStatus();     }      resp = JSON.parse(resp);     result.tags.issue_id = resp.id;     result.tags.issue_key = resp.key;      return JSON.stringify(result); } catch (error) {     Zabbix.log(4, '[ Jira webhook ] Issue creation failed json : ' + JSON.stringify({"fields": fields}));     Zabbix.log(3, '[ Jira webhook ] issue creation failed : ' + error);      throw 'Failed with error: ' + error; } ```
zh-cn	 #### Jira webhook (自定义)  ![](../../../../../../assets/en/manual/config/notifications/media/media_webhook_jira.png)  此脚本将创建一个JIRA问题，并返回关于所创建问题的一些信息。  ``` {.java} try {     Zabbix.log(4, '[ Jira webhook ] Started with params: ' + value);      var result = {             'tags': {                 'endpoint': 'jira'             }         },         params = JSON.parse(value),         req = new HttpRequest(),         fields = {},         resp;      if (params.HTTPProxy) {         req.setProxy(params.HTTPProxy);     }      req.addHeader('Content-Type: application/json');     req.addHeader('Authorization: Basic ' + params.authentication);      fields.summary = params.summary;     fields.description = params.description;     fields.project = {key: params.project_key};     fields.issuetype = {id: params.issue_id};      resp = req.post('https://tsupport.zabbix.lan/rest/api/2/issue/',         JSON.stringify({"fields": fields})     );      if (req.getStatus() != 201) {         throw 'Response code: ' + req.getStatus();     }      resp = JSON.parse(resp);     result.tags.issue_id = resp.id;     result.tags.issue_key = resp.key;      return JSON.stringify(result); } catch (error) {     Zabbix.log(4, '[ Jira webhook ] Issue creation failed json : ' + JSON.stringify({"fields": fields}));     Zabbix.log(3, '[ Jira webhook ] issue creation failed : ' + error);      throw 'Failed with error: ' + error; } ```

en-us	#### JMX item keys in more detail
zh-cn	#### JMX监控项详细信息

en-us	#### JMX monitoring  See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details.  
zh-cn	#### JMX 监控  详见  [JMX 监控](/manual/config/items/itemtypes/jmx_monitoring)  页面以获取更多信息。

en-us	#### JMX monitoring  See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details.  
zh-cn	#### JMX 监控  详见  [JMX 监控](/manual/config/items/itemtypes/jmx_monitoring)  页面以获取更多信息。

en-us	#### JMX monitoring  See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details.  
zh-cn	#### JMX 监控  详见  [JMX 监控](/manual/config/items/itemtypes/jmx_monitoring)  页面以获取更多信息。

en-us	 ### JMX monitoring  The template *Generic Java JMX* now contains discovery rules for low-level discovery of memory pools and garbage collectors. 
zh-cn	 ### JMX 监控  模板 *Generic Java JMX* 现在包含内存池和垃圾回收器的低级别自动发现规则。

en-us	# JMX template operation  Steps to ensure correct operation of templates that collect metrics by [JMX](/manual/config/items/itemtypes/jmx_monitoring):  1\. Make sure Zabbix [Java gateway](/manual/concepts/java#getting_java_gateway) is installed and set up properly.\ 2. [Link](/manual/config/templates/linking#linking_a_template) the template to the target host. The host should have JMX interface set up.\ If the template is not available in your Zabbix installation, you may need to import the template's .xml file first - see [Templates out-of-the-box](/manual/config/templates_out_of_the_box) section for instructions.\ 3. Adjust the values of mandatory macros as needed.\ 4. Configure the instance being monitored to allow sharing data with Zabbix - see instructions in the *Additional steps/comments* column.  ::: notetip  This page contains only a minimum set of macros and setup steps that are required for proper template operation. A detailed description of a template, including the full list of macros, items, and triggers, is available in the template's Readme.md file (accessible by clicking on a template name).  :::  |Template|Mandatory macros|Additional steps/comments| |--------|----------------|-------------------------| |[Apache ActiveMQ by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/activemq_jmx/README.md)|**{$ACTIVEMQ.PORT}** - port for JMX (default: 1099).<br>**{$ACTIVEMQ.USERNAME}**, **{$ACTIVEMQ.PASSWORD}** - login credentials for JMX<br>(default username: admin, password: activemq).|JMX access to Apache ActiveMQ should be enabled and configured per instructions in [the official documentation](https://activemq.apache.org/jmx.html).| |[Apache Cassandra by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cassandra_jmx/README.md)|**{$CASSANDRA.USER}**, **{$CASSANDRA.PASSWORD}** - Apache Cassandra login credentials<br>(default username: zabbix, password: zabbix)|JMX access to Apache Cassandra should be enabled and configured per instructions in [the official documentation](https://cassandra.apache.org/doc/latest/operating/security.html#jmx-access).| |[Apache Kafka by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kafka_jmx/README.md)|**{$KAFKA.USER}**, **{$KAFKA.PASSWORD}** - Apache Kafka login credentials<br>(default username: zabbix, password: zabbix)|JMX access to Apache Kafka should be enabled and configured per instructions in [the official documentation](https://kafka.apache.org/documentation/#remote_jmx).| |[Apache Tomcat by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/tomcat_jmx/README.md)|**{$TOMCAT.USER}**, **{$TOMCAT.PASSWORD}** - Apache Tomcat login credentials; leave blank if Tomcat installation does not require authentication<br>(default: not set).|JMX access to Apache Tomcat should be enabled and configured per instructions in [the official documentation](https://tomcat.apache.org/tomcat-10.0-doc/monitoring.html#Enabling_JMX_Remote) (choose the correct version).| |[GridGain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/gridgain_jmx/README.md)|**{$GRIDGAIN.USER}**, **{$GRIDGAIN.PASSWORD}** - GridGain login credentials (default username: zabbix, password: <secret>).|JMX access to GridGain In-Memory Computing Platform should be enabled and configured per instructions in [the documentation](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html).| |[Ignite by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/ignite_jmx/README.md)|**{$IGNITE.USER}**, **{$IGNITE.PASSWORD}** - Apache Ignite login credentials (default username: zabbix, password: <secret>).|Enable and configure JMX access to Apache Ignite.<br><br>JMX tree hierarchy contains ClassLoader by default. Adding the following Java Virtual Machine option `-DIGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false` will exclude one level with ClassLoader name.<br><br>Cache and Data Region metrics can be configured as needed - see [Ignite documentation](https://ignite.apache.org/docs/latest/monitoring-metrics/configuring-metrics) for details.<br><br>See also: [Monitoring and Management Using JMX Technology](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)| |[WildFly Domain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_domain_jmx/README.md)|**{$WILDFLY.JMX.PROTOCOL}** - JMX scheme (default: remote+http)<br>**{$WILDFLY.USER}**, **{$WILDFLY.PASSWORD}** - WildFly login credentials (default username: zabbix, password: zabbix).|1\. Enable and configure JMX access to WildFly according to instructions in [the official documentation](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copy *jboss-client.jar* from `/(wildfly,EAP,Jboss,AS)/bin/client` into directory `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Restart Zabbix Java gateway.| |[WildFly Server by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_server_jmx/README.md)|**{$WILDFLY.JMX.PROTOCOL}** - JMX scheme (default: remote+http)<br>**{$WILDFLY.USER}**, **{$WILDFLY.PASSWORD}** - WildFly login credentials (default username: zabbix, password: zabbix).|1\. Enable and configure JMX access to WildFly according to instructions in [the official documentation](https://docs.wildfly.org/23/Admin_Guide.html#JMX).<br><br>2. Copy *jboss-client.jar* from `/(wildfly,EAP,Jboss,AS)/bin/client` into directory `/usr/share/zabbix-java-gateway/lib`.<br><br>3. Restart Zabbix Java gateway.|
zh-cn	 # JMX 模板操作  确保通过[JMX](/manual/config/items/itemtypes/jmx_monitoring)收集模板指标的正确步骤:  1\. 确保已正确安装和设置 Zabbix [Java网关](/manual/concepts/java#getting_java_gateway) 。\ 2. [链接](/manual/config/templates/linking#linking_a_template) 模板到目标主机。主机应设置JMX接口。\ 如果模板在您的Zabbix中不可用， 您可能需要先导入摸板文件 .xml - 查看[开箱即用的模板](/manual/config/templates_out_of_the_box) 说明部分。 3. 根据需要调整必配宏的值。\ 4. 配置要监控的实例允许与Zabbix共享数据- 请参阅 _附加步骤/注释_ 字段。  ::: notetip 该页面仅包含最小的一组宏和正确的模板操作所需的设置步骤。 在模板的Readme.md文件中提供了模板的详细说明，包括宏，项和触发器的完整列表（可通过单击模板名称访问）。 :::  |模板|必配宏|附加步骤/注释| |--------|----------------|-------------------------| |[Apache ActiveMQ by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/activemq_jmx/README.md)|**{\$ACTIVEMQ.PORT}** - JMX端口 (默认: 1099).<br>**{\$ACTIVEMQ.USERNAME}**, **{\$ACTIVEMQ.PASSWORD}** - JMX登录凭证<br>(默认 用户名: admin, 密码: activemq).|根据 [官方文档](https://activemq.apache.org/jmx.html) 启用和配置JMX访问Apache ActiveMQ.| |[Apache Cassandra by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/cassandra_jmx/README.md)|**{\$CASSANDRA.USER}**, **{\$CASSANDRA.PASSWORD}** - Apache Cassandra 登录凭据<br>(默认 用户名: zabbix, 密码: zabbix)|根据 [官方文档](https://cassandra.apache.org/doc/latest/operating/security.html#jmx-access) 启用和配置JMX访问Apache Cassandra.| |[Apache Kafka by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/kafka_jmx/README.md)|**{\$KAFKA.USER}**, **{\$KAFKA.PASSWORD}** - Apache Kafka 登录凭据<br>(默认 用户名: zabbix, 密码: zabbix)|根据 [官方文档](https://kafka.apache.org/documentation/#remote_jmx) 启用和配置JMX访问 Apache Kafka .| |[Apache Tomcat by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/tomcat_jmx/README.md)|**{\$TOMCAT.USER}**, **{\$TOMCAT.PASSWORD}** - Apache Tomcat 登录凭据; leave blank if Tomcat installation does not require authentication<br>(默认: 不设置).|根据 [官方文档](https://tomcat.apache.org/tomcat-10.0-doc/monitoring.html#Enabling_JMX_Remote) (请选择正确的版本) 启用和配置JMX访问Apache Tomcat.| |[GridGain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/gridgain_jmx/README.md)|**{\$GRIDGAIN.USER}**, **{\$GRIDGAIN.PASSWORD}** - GridGain 登录凭据 (默认 用户名: zabbix, 密码: <secret>).|根据 [文档](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html) 启用和配置JMX访问GridGain In-Memory Computing Platform.| |[Ignite by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/ignite_jmx/README.md)|**{\$IGNITE.USER}**, **{\$IGNITE.PASSWORD}** - Apache Ignite 登录凭据 (默认 用户名: zabbix, 密码: <secret>).|启动和配置JMX访问Apache Ignite.<br><br>默认情况下，JMX树层次结构包含类加载器. 添加下列Java虚拟机参数`-DIGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false`将排除一个具有类加载器名称的级别.<br><br>Cache 和 Data Region 指标需配置  - 详情参见 [Ignite文档](https://ignite.apache.org/docs/latest/monitoring-metrics/configuring-metrics).<br><br>See also: [Monitoring and Management Using JMX Technology](https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html)| |[WildFly Domain by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_domain_jmx/README.md)|**{\$WILDFLY.JMX.PROTOCOL}** - JMX 协议(默认: remote+http)<br>**{\$WILDFLY.USER}**, **{\$WILDFLY.PASSWORD}** - WildFly 登录凭据 (默认 用户名: zabbix, 密码: zabbix).|1\. 根据 [官方文档](https://docs.wildfly.org/23/Admin_Guide.html#JMX) 启用和配置JMX访问WildFly.<br><br>2. 从`/(wildfly,EAP,Jboss,AS)/bin/client` 中复制 *jboss-client.jar* 到 `/usr/share/zabbix-java-gateway/lib`目录中.<br><br>3. 重启 Zabbix Java网关.| |[WildFly Server by JMX](https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/wildfly_server_jmx/README.md)|**{\$WILDFLY.JMX.PROTOCOL}** - JMX 协议 (默认: remote+http)<br>**{\$WILDFLY.USER}**, **{\$WILDFLY.PASSWORD}** - WildFly 登录凭据 (默认 用户名: zabbix, 密码: zabbix).|1\. 根据 [官方文档](https://docs.wildfly.org/23/Admin_Guide.html#JMX)启用和配置JMX访问WildFly.<br><br>2. Copy  从`/(wildfly,EAP,Jboss,AS)/bin/client` 复制*jboss-client.jar*到 `/usr/share/zabbix-java-gateway/lib`目录中.<br><br>3.  重启 Zabbix Java网关.|

en-us	 ### JSONPath parsing errors  JSONPath parsing errors occur in this version in case of leading whitespace and empty array/object. Fixed in Zabbix 6.0.12.
zh-cn	### JSONPath解析错误  在前导空格和空数组/对象的情况下，此版本中会出现 JSONPath 解析错误。 在 Zabbix 6.0.12 中修复。

en-us	#### Keeping history  You can set for how many days history will be kept:  -   in the item properties [form](/manual/config/items/item) -   when mass-updating items -   when [setting     up](/manual/web_interface/frontend_sections/administration/general#housekeeper)     housekeeper tasks  Any older data will be removed by the housekeeper.  The general strong advice is to keep history for the smallest possible number of days and that way not to overload the database with lots of historical values.  Instead of keeping a long history, you can keep longer data of trends. For example, you could keep history for 14 days and trends for 5 years.  You can get a good idea of how much space is required by history versus trends data by referring to the [database sizing page](/manual/installation/requirements#database_size).  While keeping shorter history, you will still be able to review older data in graphs, as graphs will use trend values for displaying older data.  ::: noteimportant If history is set to '0', the item will update only dependent items and inventory. No trigger functions will be evaluated because trigger evaluation is based on history data only. :::   ::: notetip As an alternative way to preserve history consider to use [history export](/manual/config/items/loadablemodules#providing_history_export_callbacks) functionality of loadable modules. :::
zh-cn	#### 历史数据的留存  通过设置历史数据保留时长，可以指定历史数据留存的时长。在以下位置，你可以找到相关的输入框：  -   监控项属性 [表单](/manual/config/items/item) -   批量更新监控项 -   [管家配置页](/manual/web_interface/frontend_sections/administration/general#管家)       任何过旧的历史数据会被管家从数据库中删除。  一般来讲，强烈建议将历史数据保留时长设置得尽可能的小。这么做可以让数据库不会因存储了大量的历史数据，导致超负荷运行。  可以选择长时间的保留趋势数据，来替代长期需要的历史数据。例如：设置成保留14天历史数据和5年的趋势数据。  参考[数据库空间大小](/manual/installation/requirements#database_size)页，来了解历史数据和趋势数据各自需要的数据库空间。  当设置了较短的历史数据保留时间，图形会使用趋势数据值显示旧数据，因此依旧可以通过图形查看旧数据。  ::: noteimportant 如果历史数据保留时长被设置为“0”，只有相关项目和资产记录会被更新。不会计算触发器函数，因为触发器计算是基于历史数据的。 :::   ::: notetip 作为保存历史数据的替代方法，考虑使用可加载模块 [导出历史数据](/manual/config/items/loadablemodules#providing_history_export_callbacks) 功能。 :::

en-us	#### Keeping trends  Trends is a built-in historical data reduction mechanism which stores minimum, maximum, average and the total number of values per every hour for numeric data types.  You can set for how many days trends will be kept:  -   in the item properties [form](/manual/config/items/item) -   when mass-updating items -   when setting up Housekeeper tasks  Trends usually can be kept for much longer than history. Any older data will be removed by the housekeeper.  Zabbix server accumulates trend data in runtime in the trend cache, as the data flows in. Server flushes **previous hour** trends of every item into the database (where frontend can find them) in these situations:  -   server receives the first current hour value of the item -   5 or less minutes of the current hour left and still no current hour     values of the item -   server stops  To see trends on a graph you need to wait at least to the beginning of the next hour (if item is updated frequently) and at most to the end of the next hour (if item is updated rarely), which is 2 hours maximum.  When server flushes trend cache and there are already trends in the database for this hour (for example, server has been restarted mid-hour), server needs to use update statements instead of simple inserts. Therefore on a bigger installation if restart is needed it is desirable to stop server in the end of one hour and start in the beginning of the next hour to avoid trend data overlap.  History tables do not participate in trend generation in any way.  ::: noteimportant If trends are set to '0', Zabbix server does not calculate or store trends at all. :::  ::: noteclassic The trends are calculated and stored with the same data type as the original values. As a result the average value calculations of unsigned data type values are rounded and the less the value interval is the less precise the result will be. For example if item has values 0 and 1, the average value will be 0, not 0.5.  Also restarting server might result in the precision loss of unsigned data type average value calculations for the current hour. :::
zh-cn	#### 趋势数据的留存  趋势数据是一种内建的历史数据压缩机制，可以用来存储数字类型监控项的每小时的最小值、最大值、平均值和记录数量。  通过设置趋势存储时间，可以指定趋势数据留存的时长。 在以下位置，你可以找到相关的输入框：  -   监控项属性 [表单](/manual/config/items/item) -   批量更新监控项 -   [管家配置页](/manual/web_interface/frontend_sections/administration/general#管家)  通常趋势数据设置的的留存时间应当比历史数据留存时间设置的长。任何过旧的趋势数据会被管家从数据库删除。  Zabbix server在运行时会在趋势缓存中积累趋势数据，因为有数据流入。 在这些情况下，Zabbix Server会将每个监控项的**前一个小时**趋势数据写入数据库(在前端可以看到):    - 服务器接收到监控项首个当前一小时的值   - 在还差5分钟或更少时间达到一小时，仍然没有该监控项当前一小时的值   - 服务器停止    要查看图表上的趋势，你需要至少等待到下一个小时的开始(如果监控项经常更新)，最多等待到下一个小时的结束(如果监控项很少更新)，最多2个小时。    当服务器刷新趋势缓存时，如果数据库中已经有这一小时的趋势(例如，服务器在这一小时中已经重新启动)，服务器需要使用更新语句，而不是简单的插入。 因此，在大型环境的安装中，如果需要重新启动，最好在一个小时结束时停止服务器，在下一个小时开始时开始，以避免趋势数据重叠。  趋势数据生成和历史表没有关系。  ::: noteimportant 如果趋势存储时间被设置为“0”，Zabbix server将不再计算或存储该监控项的趋势数据 :::  ::: noteclassic 趋势数据的计算和存储将会使用与原值相同的数据类型。无符号数字（unsigned Numeric）数据类型的值，平均值计算的结果小数点后会被舍去，所以记录值之间的间隔越小，计算结果结果将会精确度越低。例如：如果监控项的得到了得到了两个值，分别是“0”和“1”，那么平均值的计算结果将会是“0”，而不是“0.5”。  此外，重启服务器可能会导致当前小时无符号数字类型的数据，平均值计算的精度损失。 :::

en-us	 ##### Kernel data  |Item key|<|<|<| |--|--|------|------| |Description|Return value|Parameters|Comments| |**kernel.maxfiles**|<|<|<| |Maximum number of opened files supported by OS.|Integer| | | |**kernel.maxproc**|<|<|<| |Maximum number of processes supported by OS.|Integer| | | |**kernel.openfiles**|<|<|<| |Return the number of currently open file descriptors.|Integer| |This item is supported since Zabbix 6.0.|
zh-cn	##### 内核数据  |监控项键值|<|<|<| |--|--|------|------| |描述|返回值|参数|注释| |**kernel.maxfiles**|<|<|<| |OS支持的最大打开文件数。|整型| | | |**kernel.maxproc**|<|<|<| |OS支持的最大进程数|整型| | | |**kernel.openfiles**|<|<|<| |返回当前打开文件句柄数|整型|| 自 Zabbix 6.0开始支持该参数|

en-us	 ### Keyboard navigation  Keyboard control has been implemented for info icons in the frontend. Thus it is now  possible to focus on info icons, and open the hints, using the keyboard.
zh-cn	 ### 键盘导航  已对前端的信息图标实施键盘控制。现在是这样可以专注于信息图标，并使用键盘打开提示。