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|<| |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.|
ja	#### アイテムキー  この表は [VMware環境](/manual/vm_monitoring) を監視するためのシンプルチェックの詳細を示します。  |Key|<|<|<|<| |-|------|--|------|------| |<|説明|戻り値|パラメータ|コメント| |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|<| |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.|

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.
ja	#### アイテムキー  [検出ルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムキーは次のとおりです。      net.if.discovery  このアイテムはZabbixエージェント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.
ja	#### アイテムキー  [検出ルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムキーは次のとおりです。      system.cpu.discovery  このアイテムは、Zabbixエージェント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"
ja	#### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムキーは次のとおりです      vfs.dev.discovery  Zabbixエージェント4.4以降、このアイテムはLinuxプラットフォームでのみサポートされます。  このディスカバリアイテムを使用してディスカバリルールを作成し、次のようなことを行うことができます。  -   filter: **{\#DEVNAME} matches `sd[\D]$`** - 名前の付いたデバイスを検出する "sd0", "sd1", "sd2", ... -   filter: **{\#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.
ja	#### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムは      perf_instance.discovery[object]  また、OSのローカリゼーションとは関係なく、英語でのみオブジェクト名を提供できるようにするには、次のようにします。      perf_instance_en.discovery[object]  例:      perf_instance.discovery[Processador]     perf_instance_en.discovery[Processor]  これらのアイテムはZabbixWindowsエージェント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.
ja	#### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムは      service.discovery  このアイテムは、ZabbixWindowsエージェント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"     }]
ja	### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムは      systemd.unit.discovery  ::: noteimportant この[アイテム](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2)キーは、Zabbixエージェント2でのみサポートされています。 :::  このアイテムはsystemdユニットに関する情報を含む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).
ja	#### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムは以下です。      zabbix[host,discovery,interfaces]  内部アイテムです。 このアイテムはZabbixサーバー3.4以降でサポートされています。  このアイテムは、次のようなインターフェースの説明を含むJSONを返します。  -   IPアドレス/DNSホスト名（"接続先"ホスト設定によって異なります） -   ポート番号 -   インターフェースタイプ (Zabbixエージェント, SNMP, JMX, IPMI) -   デフォルトのインターフェースかどうか -   バルクリクエスト機能が有効か - 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.
ja	#### アイテムキー  [ディスカバリルール](/manual/discovery/low_level_discovery#discovery_rule)で使用するアイテムは      wmi.getall[<namespace>,<query>]  この[アイテム](/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"     } ] ```  このアイテムはZabbixWindowsエージェント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"     } ] ```
ja	#### アイテムキー  ファイルシステムやネットワークインターフェイスの検出とは異なり、アイテムは必ずしも"snmp.discovery"キーを持っている必要はありません。SNMPエージェントのアイテムタイプで十分です。  SNMP OIDの検出は、Zabbixサーバー/プロキシ2.0以降でサポートされています。  ディスカバリルールを設定するには、次のようにします。  -   *設定* → *テンプレート*を開きます -   適当なテンプレート行の*ディスカバリ*をクリックします  ![](../../../../../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です。 検出されたOIDのインデックスを含む組み込みマクロ*{\#SNMPINDEX} *が、検出されたエンティティに適用されます。 検出されたエンティティは*{\#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}マクロ：**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.
ja	#### 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サーバーへの接続を開き、フィルターを(objectClass=\*)に設定してLDAP検索操作を実行して、最初のエントリの最初の属性が正常に取得できることを検証します。ポートが指定されていない場合はデフォルトのポート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）が交換されます。ここでのメジャーとマイナーはプロトコルバージョンであり、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.
ja	#### net.udp.serviceアイテムのパラメータ  **ntp**  UDPを介してSNTPパケットを送信し、[RFC 4330、セクション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.|
ja	### item  ::: noteclassic Zabbix API を使用して Web アイテムを直接作成、更新、または削除することはできません。 :::  item オブジェクトには次のプロパティがあります。  |プロパティ|[タイプ](/manual/api/reference_commentary#data_types)|説明| |--|--|------| |itemid|string|*(読取専用)* アイテムID| |**delay**<br>(必須)|string|アイテムの更新間隔。 秒またはサフィックス付きの時間単位 (30s、1m、2h、1d) を受け入れます。<br>オプションで、1 つまたは複数の [カスタム間隔](/manual/config/items/item/custom_intervals) を柔軟な間隔またはスケジューリングとして指定できます。<br>複数の間隔はセミコロンで区切ります。<br>ユーザーマクロを使用できます。 1 つのマクロでフィールド全体を埋める必要があります。 フィールド内の複数のマクロまたはテキストと混合されたマクロはサポートされていません。<br>柔軟な間隔は、スラッシュで区切られた 2 つのマクロとして記述できます (例: `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`)。<br><br>Zabbix トラッパー、依存アイテム、および `mqtt.get` キーを使用した Zabbix エージェント (アクティブ) のオプション。| |**hostid**<br>(required)|string|アイテムが属するホストまたはテンプレートの ID<br><br>更新操作の場合、このフィールドは *読取専用* です。| |**interfaceid**<br>(必須)|string|アイテムのホストインターフェースの ID<br><br>ホスト アイテムにのみ使用されます。 Zabbix エージェント (アクティブ)、Zabbix インターナル、Zabbix トラッパー、計算、依存、データベース モニター、およびスクリプト アイテムには必要ありません。 HTTP エージェント アイテムのオプションです。| |**key\_**<br>(required)|string|アイテムキー| |**name**<br>(required)|string|アイテム名| |**type**<br>(required)|integer|アイテムのタイプ<br><br>使用可能な値:<br>0 - Zabbix エージェント<br>2 - Zabbix トラッパー<br>3 - シンプル チェック<br>5 - Zabbix インターナル<br>7 - Zabbix エージェント (アクティブ)<br>9 - Web アイテム<br>10 - 外部チェック<br>11 - データベース監視<br>12 - IPMI エージェント<br>13 - SSH エージェント<br> 14 - Telnet エージェント<br>15 - 計算済み<br>16 - JMX エージェント<br>17 - SNMP トラップ<br>18 - 依存アイテム<br>19 - HTTP エージェント<br>20 - SNMP エージェント<br>21 - スクリプト| |**url**<br>(required)|string|URL 文字列。HTTP エージェント アイテム タイプにのみ必要です。 ユーザー マクロ{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 - *(デフォルト)* なし<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 エージェントアイテムフィールド。 データのプール中に応答リダイレクトに従うか<br><br>0 - リダイレクトに従いません<br>1 - *(デフォルト)* リダイレクトに従います| |headers|object|HTTP エージェントアイテムフィールド。 ヘッダー名がキーとして使用され、ヘッダー値が値として使用される HTTP(S) リクエスト ヘッダーを持つオブジェクト。<br><br>例:<br>{ "User-Agent": "Zabbix" }| |history|string|履歴データを保存する時間の単位。 ユーザー マクロも受け入れます。<br><br>デフォルト: 90d| |http\_proxy|string|HTTP エージェントアイテムフィールド。 HTTP(S) プロキシ接続文字列。| |inventory\_link|integer|アイテムによって入力されるホストインベントリフィールドID<br><br>サポートされているホストインベントリフィールドのリストについては、[ホスト インベントリ ページ](/manual/api/reference/host/object#host_inventory) を参照してください。 <br><br>デフォルト: 0。| |ipmi\_sensor|string|IPMI センサー。 IPMI アイテムでのみ使用されます| |jmx\_endpoint|string|JMX エージェントのカスタム接続文字列。<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 エージェントアイテムフィールド。 レスポンスを JSON に変換する必要があります。<br><br>0 - *(デフォルト)* そのまま保存します<br>1 - JSON に変換します| |params|string|アイテムのタイプに応じた追加パラメータ:<br>- SSH および Telnet アイテムの実行スクリプト<br>- データベース監視アイテムの SQL クエリ<br>- 計算アイテムの式<br>- スクリプトのスクリプト アイテム| |parameters|array|スクリプトアイテムの追加パラメーター。 'name' および 'value' プロパティを持つオブジェクトの配列。name は一意である必要があります| |password|string|認証用のパスワード。 簡易チェック、SSH、Telnet、データベース監視、JMX、HTTPエージェントのアイテムで使用| |post\_type|integer|HTTP エージェントアイテムフィールド。 posts プロパティに格納される投稿データ本体のタイプ。<br><br>0 - *(デフォルト)* 生データ。<br>2 - JSON データ。<br>3 - XML データ。| |posts|string|HTTP エージェントアイテムフィールド。 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 エージェントアイテムフィールド。 クエリ パラメータ。 'キー':'値'のペアを持つオブジェクトの配列。値は空の文字列にすることができます。| |request\_method|integer|HTTP エージェントアイテムフィールド。 リクエスト メソッドのタイプ。<br><br>0 - *(デフォルト)* GET<br>1 - POST<br>2 - PUT<br>3 - HEAD| |retrieve\_mode|integer|HTTP エージェントアイテムフィールド。 レスポンスのどの部分を保存するか。<br><br>0 - *(デフォルト)* 本文<br>1 - ヘッダー<br>2 - 本文とヘッダーの両方<br><br>request\_method HEAD の場合、許可される値は 1 のみ| |snmp\_oid|string|SNMP OID.| |ssl\_cert\_file|string|HTTP エージェントアイテムフィールド。 公開 SSL キーファイル パス| |ssl\_key\_file|string|HTTP エージェントアイテムフィールド。 プライベート SSL キーファイル パス| |ssl\_key\_password|string|HTTP エージェントアイテムフィールド。 SSL キー ファイルのパスワード| |state|integer|*(読取専用)* アイテムの状態<br><br>使用可能な値:<br>0 - *(デフォルト)* 通常<br>1 - サポートされていません| |status|integer|アイテムのステータス<br><br>使用可能な値:<br>0 - *(デフォルト)* 有効なアイテム<br>1 - 無効なアイテム| |status\_codes|string|HTTP エージェントアイテムフィールド。 コンマで区切られた必須の HTTP ステータス コードの範囲。 コンマ区切りリストの一部としてユーザー マクロもサポートします。<br><br>例: 200,200-{$M},{$M},200-400| |templateid|string|(読取専用) 親テンプレート アイテムの ID。<br><br>*ヒント*: `hostid` プロパティを使用して、アイテムが属するテンプレートを指定します。| |timeout|string|アイテム データ ポーリング リクエストのタイムアウト。 HTTP エージェントおよびスクリプト アイテムに使用されます。 ユーザー マクロをサポートします。<br><br>デフォルト: 3 秒<br>最大値: 60 秒| |trapper\_hosts|string|許可されたホスト。 トラッパー アイテムまたは HTTP エージェント アイテムで使用されます。| |trends|string|トレンド データを保存する時間の単位。 ユーザー マクロも受け入れます。<br><br>デフォルト: 365d| |units|string|値の単位| |username|string|認証用のユーザー名。 簡易チェック、SSH、Telnet、データベース監視、JMX、HTTPエージェントのアイテムで使用<br><br>SSH、Telnetのアイテムで必須<br>JMX で使用する場合、パスワードもユーザー名と一緒に指定するか、両方のプロパティを空白のままにする必要があります。| |uuid|string|インポートされたアイテムを既存のアイテムにリンクするために使用されるユニバーサル一意識別子。 テンプレートのアイテムにのみ使用されます。 指定されていない場合は自動生成されます。<br><br>更新操作の場合、このフィールドは *読取専用* です。| |valuemapid|string|関連付けられた値マップID| |verify\_host|integer|HTTP エージェントアイテムフィールド。 URL のホスト名がホスト証明書の Common Name フィールドまたは Subject Alternate Name フィールドにあることを検証します。<br><br>0 - *(デフォルト)* 検証しません。<br>1 - 検証します。| |verify\_peer|integer|HTTP エージェントアイテムフィールド。 検証はホスト証明書の認証です。<br><br>0 - *(デフォルト)* 検証しません。<br>1 - 検証します。|

en-us	# > Item object  The following objects are directly related to the `item` API.
ja	# > Itemオブジェクト  次のオブジェクトは、`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>`.  
ja	### 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>`.  

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.
ja	### アイテムの前処理  アイテム前処理オブジェクトには、次のプロパティがあります。  |プロパティ|[タイプ](/manual/api/reference_commentary#data_types)|説明| |--|--|------| |**type**<br>(必須)|integer|前処理オプションのタイプ。<br><br>使用可能な値:<br>1 - カスタム乗数<br>2 - 右トリム<br>3 - 左トリム<br>4 - トリム<br>5 - 正規表現マッチング<br>6 - ブール値から 10 進数へ<br>7 - 8 進数 から10 進数へ<br>8 - 16 進数から 10 進数へ<br>9 - 単純な変更<br>10 - 1 秒あたりの変更<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 サーバーによって設定されます。<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|ブール値から10進数へ|<|<|<|0, 1, 2, 3| |7|8 進数 から10 進数へ|<|<|<|0, 1, 2, 3| |8|16 進数 から10 進数へ|<|<|<|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|Prometheus パターン|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^ ユーザーマクロ\ ^7^ 構文に従う Prometheus パターン: `<metric name>{<label name>="<label value>", ...} == <value>` 各 Prometheus パターン コンポーネント (メトリック、ラベル名、ラベル値、およびメトリック値) は、ユーザー マクロにすることができます。\ ^8^ Prometheus は次の構文で出力します: `<label name>` (ユーザー マクロを使用できます) `label` が 2 番目のパラメーターとして選択されている場合。\ ^9^ 集計関数の 1 つ: `sum`,`min`,`max`,`avg`,`count` (`function` が 2 番目のパラメーターとして選択されている場合)

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.\
ja	#### アイテムプロトタイプ  バグフィックス:\ [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`.\
ja	#### アイテムプロトタイプ  変更点:\ [ZBXNEXT-7049](https://support.zabbix.com/browse/ZBXNEXT-7049) `itemprototype.get`, `itemprototype.create`, `itemprototype.update`: Prometheus パターンの前処理ステップに第三パラメーターを追加しました。第二パラメーターで集計メソッドを決定します: `value`, `label`, `function`。第三パラメーターは、集計メソッド `label` の Prometheus 出力または集計メソッド `function` の集計関数となります。\

en-us	#### itemprototype  Changes:\ [ZBXNEXT-7951](https://support.zabbix.com/browse/ZBXNEXT-7951) `itemprototype.update`: the parameter `uuid` can now be updated.\
ja	#### アイテムプロトタイプ  変更点:\ [ZBXNEXT-7951](https://support.zabbix.com/browse/ZBXNEXT-7951) `itemprototype.update`: パラメーター `uuid` が更新できるようになりました。\

en-us	# itemprototype.create
ja	# itemprototype.create

en-us	# itemprototype.delete
ja	# itemprototype.delete

en-us	# itemprototype.get
ja	# itemprototype.get

en-us	# > Item prototype object  The following objects are directly related to the `itemprototype` API.
ja	# > Item prototypeオブジェクト  次のオブジェクトは、`itemprototype`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>`.  
ja	### 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.
ja	### アイテムプロトタイプの前処理  アイテム プロトタイプの前処理オブジェクトには、次のプロパティがあります。  |プロパティ|[タイプ](/manual/api/reference_commentary#data_types)|説明| |--|--|------| |**type**<br>(必須)|integer|前処理オプションのタイプ。<br><br>使用可能な値:<br>1 - カスタム乗数<br>2 - 右トリム<br>3 - 左トリム<br>4 - トリム<br>5 - 正規表現マッチング<br>6 - ブール値から 10 進数へ<br>7 - 8 進数 から10 進数へ<br>8 - 16 進数から 10 進数へ<br>9 - 単純な変更<br>10 - 1 秒あたりの変更<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 サーバーによって設定されます。<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|ブール値から10進数へ|<|<|<|0, 1, 2, 3| |7|8 進数 から10 進数へ|<|<|<|0, 1, 2, 3| |8|16 進数 から10 進数へ|<|<|<|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|Prometheus パターン|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 パターン コンポーネント (メトリック、ラベル名、ラベル値、およびメトリック値) は、ユーザー マクロかLLDマクロにすることができます。\ ^8^ Prometheus は次の構文で出力します: `<label name>` (ユーザー マクロまたはLLDマクロを使用できます) `label` が 2 番目のパラメーターとして選択されている場合。\ ^9^ 集計関数の 1 つ: `sum`,`min`,`max`,`avg`,`count` (`function` が 2 番目のパラメーターとして選択されている場合)

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)
ja	#### アイテムプロトタイプ  次のスクリーンショットは、アイテムのプロトタイプでこれらのマクロを使用する方法を示しています。  ![](../../../../../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.|
ja	### Item prototype tag  item prototype tagオブジェクトには次のプロパティがあります。  |プロパティ|[タイプ](/manual/api/reference_commentary#data_types)|説明| |--|--|------| |**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.|
ja	### Item prototype  item prototype オブジェクトには次のプロパティがあります。  |プロパティ|[タイプ](/manual/api/reference_commentary#data_types)|説明| |--|--|------| |itemid|string|*(読取専用)* アイテムプロトタイプID| |**delay**<br>(必須)|string|アイテムプロトタイプの更新間隔。 秒またはサフィックス付きの時間単位 (30s、1m、2h、1d) を受け入れます。<br>オプションで、1 つまたは複数の [カスタム間隔](/manual/config/items/item/custom_intervals) を柔軟な間隔またはスケジューリングとして指定できます。<br>複数の間隔はセミコロンで区切ります。<br>ユーザーマクロを使用できます。 1 つのマクロでフィールド全体を埋める必要があります。 フィールド内の複数のマクロまたはテキストと混合されたマクロはサポートされていません。<br>柔軟な間隔は、スラッシュで区切られた 2 つのマクロとして記述できます (例: `{$FLEX_INTERVAL}/{$FLEX_PERIOD}`)。<br><br>Zabbix トラッパー、依存アイテム、および `mqtt.get` キーを使用した Zabbix エージェント (アクティブ) のオプション。| |**hostid**<br>(required)|string|アイテムプロトタイプが属するホストまたはテンプレートの ID<br><br>更新操作の場合、このフィールドは *読取専用* です。| |**ruleid**<br>(required)|string|アイテムが属する LLD ルールの ID。<br><br>更新操作の場合、このフィールドは *読取専用* です。| |**interfaceid**<br>(必須)|string|アイテムプロトタイプのホストインターフェースの ID<br><br>ホスト アイテムプロトタイプにのみ使用されます。 Zabbix エージェント (アクティブ)、Zabbix インターナル、Zabbix トラッパー、計算、依存、データベース モニター、およびスクリプト アイテムには必要ありません。 HTTP エージェント アイテムのオプションです。| |**key\_**<br>(required)|string|アイテムプロトタイプキー| |**name**<br>(required)|string|アイテムプロトタイプ名| ||**type**<br>(required)|integer|アイテムプロトタイプのタイプ<br><br>使用可能な値:<br>0 - Zabbix エージェント<br>2 - Zabbix トラッパー<br>3 - シンプル チェック<br>5 - Zabbix インターナル<br>7 - Zabbix エージェント (アクティブ)<br>9 - Web アイテム<br>10 - 外部チェック<br>11 - データベース監視<br>12 - IPMI エージェント<br>13 - SSH エージェント<br> 14 - Telnet エージェント<br>15 - 計算済み<br>16 - JMX エージェント<br>17 - SNMP トラップ<br>18 - 依存アイテム<br>19 - HTTP エージェント<br>20 - SNMP エージェント<br>21 - スクリプト| |**url**<br>(required)|string|URL 文字列。HTTP エージェント アイテムプロトタイプ タイプにのみ必要です。 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 - *(デフォルト)* なし<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 の従属アイテムプロトタイプが許可されます<br><br>従属アイテムに必要です| |output\_format|integer|HTTP エージェントアイテムプロトタイプフィールド。 レスポンスを JSON に変換する必要があります。<br><br>0 - *(デフォルト)* そのまま保存します<br>1 - JSON に変換します| |params|string|アイテムプロトタイプのタイプに応じた追加パラメータ:<br>- SSH および Telnet アイテムプロトタイプの実行スクリプト<br>- データベース監視アイテムプロトタイプの SQL クエリ<br>- 計算アイテムプロトタイプの式<br>- スクリプトのスクリプト アイテムプロトタイプ| |parameters|array|スクリプトアイテムプロトタイプの追加パラメーター。 'name' および 'value' プロパティを持つオブジェクトの配列。name は一意である必要があります| |password|string|認証用のパスワード。 簡易チェック、SSH、Telnet、データベース監視、JMX、HTTPエージェントのアイテムプロトタイプで使用| |post\_type|integer|HTTP エージェントアイテムプロトタイプフィールド。 posts プロパティに格納される投稿データ本体のタイプ。<br><br>0 - *(デフォルト)* 生データ。<br>2 - JSON データ。<br>3 - XML データ。| |posts|string|HTTP エージェントアイテムプロトタイプフィールド。 HTTP(S) リクエストの本文データ。 post\_type で使用します。| |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 - *(デフォルト)* 本文<br>1 - ヘッダー<br>2 - 本文とヘッダーの両方<br><br>request\_method HEAD の場合、許可される値は 1 のみ| |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>デフォルト: 3 秒<br>最大値: 60 秒| |trapper\_hosts|string|許可されたホスト。 トラッパー アイテムプロトタイプまたは HTTP エージェント アイテムプロトタイプで使用されます。| |trends|string|トレンド データを保存する時間の単位。 ユーザー マクロとLLDマクロも受け入れます。<br><br>デフォルト: 365d| |units|string|値の単位| |username|string|認証用のユーザー名。 簡易チェック、SSH、Telnet、データベース監視、JMX、HTTPエージェントのアイテムプロトタイプで使用<br><br>SSH、Telnetのアイテムプロトタイプで必須<br>JMX で使用する場合、パスワードもユーザー名と一緒に指定するか、両方のプロパティを空白のままにする必要があります。| |uuid|string|インポートされたアイテムプロトタイプを既存のアイテムプロトタイプにリンクするために使用されるユニバーサル一意識別子。 テンプレートのアイテムプロトタイプにのみ使用されます。 指定されていない場合は自動生成されます。<br><br>更新操作の場合、このフィールドは *読取専用* です。| |valuemapid|string|関連付けられた値マップID| |verify\_host|integer|HTTP エージェントアイテムプロトタイプフィールド。 URL のホスト名がホスト証明書の Common Name フィールドまたは Subject Alternate Name フィールドにあることを検証します。<br><br>0 - *(デフォルト)* 検証しません。<br>1 - 検証します。| |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
ja	# Item prototype  このクラスは、アイテムプロトタイプを操作するためのものです。  オブジェクトリファレンス :\  -   [Item prototype](/manual/api/reference/itemprototype/object#item_prototype)  利用可能なメソッド :\  -   [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
ja	# itemprototype.update

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)
ja	##### アイテムのプロトタイプ  次のようなアイテムのプロトタイプを作成することをお勧めします。  ![](../../../../../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
ja	## アイテム

en-us	## Items
ja	## アイテム

en-us	## Items
ja	## アイテム

en-us	## Items
ja	## アイテム

en-us	#### Items  Define items to monitor.  [Item API](/manual/api/reference/item)
ja	#### アイテム  監視するアイテムを定義します  [Item API](/manual/api/reference/item)

en-us	### Items  ##### docker.container_stats  The [docker.container_stats](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#docker) item on Zabbix agent 2 now also returns a `pids_stats` property with the current number of processes/threads on the container.
ja	### アイテム  ##### docker.container_stats  Zabbix エージェント 2 の [docker.container_stats](/manual/config/items/itemtypes/zabbix_agent/zabbix_agent2#docker) アイテムも、 コンテナ上の現在のプロセス/スレッド数とともに`pids_stats`プロパティを返すようになりました。

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.
ja	#### アイテム  別のZabbixインスタンスで内部統計のクエリを設定するには、次の2つの項目を使用します。  -   `zabbix[stats,<ip>,<port>]` internal item - Zabbixサーバー/プロキシの直接リモートクエリ用。 <ip>と<port>は、ターゲットインスタンスを識別するために使用します -   `zabbix.stats[<ip>,<port>]` agent item - Zabbixサーバー/プロキシのエージェントベースのリモートクエリ用。 <ip>と<port>は、ターゲットインスタンスを識別するために使用されます。  参考情報: [内部項目](/manual/config/items/itemtypes/internal), [Zabbixエージェントアイテム](/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.|
ja	### Item tag  item tagオブジェクトには次のプロパティがあります。  |プロパティ|[タイプ](/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
ja	# Item  このクラスは、アイテムを操作するためのものです。  オブジェクトリファレンス :\  -   [Item](/manual/api/reference/item/object#item)  利用可能なメソッド :\  -   [item.create](/manual/api/reference/item/create) - 新しいアイテムの作成 -   [item.delete](/manual/api/reference/item/delete) - アイテムの削除 -   [item.get](/manual/api/reference/item/get) - アイテムの取得 -   [item.update](/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.
ja	##### アイテム  始めに、例えばログファイルを監視するような項目を設定するのがよいでしょう:      log[/var/log/syslog]  ![](../../../../assets/en/manual/config/event_correlation/correlation_item.png)  アイテムが設定された状態で、設定変更が反映されるまで1分ほど待ってから、[Latest data](/manual/web_interface/frontend_sections/monitoring/latest_data)にアクセスして、<br> アイテムがデータ収集を開始したことを確認します。

en-us	# item.update
ja	# item.update

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).
ja	#### アイテムの値ウィジェット  ダッシュボードウィジェットに、*アイテムの値*ウィジェットが追加されました。  このタイプのウィジェットは、単一の項目の値を目立つように表示するのに便利です。さまざまな表示スタイル が可能です:  ![](../../../assets/en/manual/web_interface/frontend_sections/monitoring/item_value_widgets_new.png)  詳細は、[アイテムの値ウィジェット](/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.
ja	##### アイテムの値の保存前処理  **保存前処理** タブでは、受け取った値に対して[変換するルール](/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.
ja	#### item 値のプリプロセッシング  データのプリプロセッシングを可視化するために、以下のような簡略化した図を示します。  ![](../../../../../assets/en/manual/appendix/items/preprocessing_simplified.png)  上の図は、item 値のプリプロセッシングに関連するプロセス、オブジェクト、および主なアクションのみを **簡略化** した形で示しています。<br> この図では条件分岐、エラー処理、ループは示していない。ただ1つのプリプロセスワーカーだけが示されています。<br> （実際は複数のプリプロセスワーカーを使用することも可能です）<br> この項目は少なくとも1つのプリプロセス工程を実行する必要があると想定している。<br> この図の目的は、item 値のプリプロセスパイプラインの考え方を示すことである。<br>  - item データとitem 値は、ソケットベースのIPCメカニズムを使用してプリプロセスマネージャに渡される。 - item はプリプロセスキューに入れられる。  ::: noteclassic item はプリプロセスキューの最後または先頭に配置されます。<br> Zabbix内部アイテムは常にプリプロセスキューの先頭に配置され、その他のアイテムタイプは最後にキューイングされます。<br> :::  - この時点で、少なくとも1つの未使用の(タスクを実行していない)プリプロセスワーカーが存在するまでデータフローは停止します。<br> - プリプロセスワーカーが利用可能になると、プリプロセスタスクはそのワーカーに送られます。<br> - プリプロセスが完了すると（プリプロセスステップの実行に失敗した場合も成功した場合も）処理された値が<br>   プリプロセッシングマネージャに戻されます。<br> - プリプロセスマネージャは、結果を（item 値の型によって定義される）希望する形式に変換し、結果をプリプロセスキューに入れる。<br>   もし現在の item に依存する item がある場合、依存する item もプリプロセスキューに追加されます。<br>   ただし、値が設定され、NOT SUPPORTED 状態でないマスター item に限ります。

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.
ja	#### item 値の処理  データソースからZabbixデータベースへのデータフローを可視化するために、以下の簡略化された図を使用します。  ![](../../../../../assets/en/manual/appendix/items/overall_pic.png)  上の図は、item 値処理に関連するプロセス、オブジェクト、アクションのみを**簡略化**して示しています。<br> この図には条件分岐、エラー処理、ループなどは示していません。プリプロセスマネージャの<br> ローカルデータキャッシュも表示されていません。データフローに直接影響しないためです。<br> この図の目的は、item 値処理に関わるプロセスと、それらが相互作用する方法を示すことです。<  - データ収集は、データソースからの生データから始まる。このデータにはID、タイムスタンプ、値（複数の値も可能）のみが含まれます。 - アクティブチェック、パッシブチェック、トラッパー item など、どのような種類のデータ収集装置を使っても、<br>   考え方は同じで、データ形式と通信の開始方法を変えるだけです。<br>   (データ収集者が接続とデータを待っているか、データ収集者が通信を開始し、データを要求しているか）<br>     生データは検証され、item 設定は設定キャッシュから取得されます。(データは設定データでリッチ化されます)。<br> - データ収集者からプリプロセスマネージャへのデータの受け渡しには、ソケットベースのIPCメカニズムが使用されます。<br>   この時点でデータ収集装置はプリプロセスマネージャからの応答を待たずにデータ収集を続ける。<br> - データのプリプロセッシングが行われる。これには、プリプロセスステップの実行と依存項目処理が含まれます。  ::: noteclassic item はプリプロセッシングが行われている間にいずれかの処理が失敗した場合、状態が NOT SUPPORTED に変更されることがあります。 :::  - プリプロセスマネージャのローカルデータキャッシュからヒストリデータがヒストリーキャッシュに流される。<br> - この時点でデータの流れは止まり、次のヒストリーキャッシュの同期（ヒストリーシンサープロセスがデータの同期を行う）まで<br>    データの流れは停止します。 - 同期処理はデータの正規化から始まり、データをZabbixデータベースに格納することから始まります。<br>   データの正規化では、以下の変換を行います。<br>     目的の item タイプ(item 設定で定義されたタイプ)への変換を行います。<br>     テキストデータについては、あらかじめ定義されたサイズに基づき、切り捨てを行います。<br>     テキストデータは、それらのタイプに許容される事前定義されたサイズ(文字列はHISTORY_STR_VALUE_LEN、<br>     テキストはHISTORY_TEXT_LEN、ログ値にはHISTORY_LOG_VALUE_LEN)に基づいて切り捨てられます。<br>     データは正規化された後、Zabbixデータベースに送信されます。  ::: noteclassic データの正規化に失敗した場合(例：テキスト値を数値に変換できない場合)、item はNOT SUPPORTEDに状態を変更されることがあります。 :::  - 収集されたデータは処理される - トリガーがチェックされ、item が NOT SUPPORTED になった場合は設定が更新される - item 値処理の観点からは、これでデータフローは終了したとみなされる。

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|
ja	#### アイテム値  収集されたアイテム値について次の情報がエクスポートされます。  |フィールド|<|タイプ|説明| |-|---------|---------|---------------------------| |*host*|<|object|アイテムホストのホスト名| | |host|string|ホスト名| |^|name|string|表示ホスト名| |*groups*|<|array|アイテムホストのホストグループのリスト。 配列には少なくとも1つの要素が必要です。| | |\-|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 (for numeric items) or<br>string (for text items)|収集したアイテム値| |*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).  
ja	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)
ja	ウィジェットの左上隅にあるプラスボタンとマイナスボタンを使用するか、マウスのスクロールホイールまたはタッチパッドを使用して、マップをズームインおよびズームアウトできます。 現在のビューをデフォルトとして設定するには、マップ上の任意の場所を右クリックして、[この表示をデフォルトにセット]を選択します。 この設定は、現在のユーザーの*初期ビュー*ウィジェットパラメーターを上書きします。 この操作を元に戻すには、マップ上の任意の場所をもう一度右クリックして、[初期表示にリセット]を選択します。  *初期ビュー*または*デフォルトビュー*が設定されている場合、左側のホームアイコンを押すと、いつでもこのビューに戻ることができます。  ![](../../../../../../../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|Mandatory status|Comments| |--|-|-------| |[android-json](https://mvnrepository.com/artifact/com.vaadin.external.google/android-json)|Yes|Version 4.3r1 or higher.<br>JSON (JavaScript Object Notation) is a lightweight data-interchange format. This is the org.json compatible Android implementation extracted from the Android SDK.| |[logback-classic](https://mvnrepository.com/artifact/ch.qos.logback/logback-classic)|^|Version 1.2.9 or higher.| |[logback-core](https://mvnrepository.com/artifact/ch.qos.logback/logback-core)|^|Version 1.2.9 or higher.| |[slf4j-api](https://mvnrepository.com/artifact/org.slf4j/slf4j-api)|^|Version 1.7.32 or higher.|  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 8|1.8.0| |RHEL 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|
ja	##### Java ゲートウェイ  ソース リポジトリまたはアーカイブから Zabbix を取得した場合、必要な依存関係は既にソース ツリーに含まれています。  ディストリビューションのパッケージから Zabbix を取得した場合、必要な依存関係はパッケージング システムによって既に提供されています。  上記のどちらの場合でも、ソフトウェアを使用する準備ができており、追加のダウンロードは必要ありません。  ただし、これらの依存関係のバージョンを提供したい場合 (たとえば、一部の Linux ディストリビューション用のパッケージを準備している場合)、Java ゲートウェイが動作することがわかっているライブラリ バージョンのリストを以下に示します。 Zabbix は、これらのライブラリの他のバージョンでも動作する場合があります。  次の表に、元のコードで現在 Java ゲートウェイにバンドルされている JAR ファイルを示します。  |ライブラリ|必須ステータス|コメント| |--|-|-------| |[android-json](https://mvnrepository.com/artifact/com.vaadin.external.google/android-json)|Yes|Version 4.3r1 以降<br>JSON (JavaScript Object Notation) の軽量データ交換フォーマットです。 これは、Android SDK から抽出された org.json 互換の Android 実装です。| |[logback-classic](https://mvnrepository.com/artifact/ch.qos.logback/logback-classic)|^|Version 1.2.9 以降| |[logback-core](https://mvnrepository.com/artifact/ch.qos.logback/logback-core)|^|Version 1.2.9 以降| |[slf4j-api](https://mvnrepository.com/artifact/org.slf4j/slf4j-api)|^|Version 1.7.32 以降|  Java ゲートウェイは、Oracle Java またはオープンソースの OpenJDK (バージョン 1.6 以降) を使用して構築できます。 Zabbix が提供するパッケージは、OpenJDK を使用してコンパイルされます。 以下の表は、Zabbix パッケージのビルドに使用される OpenJDK のバージョンに関する情報をディストリビューションごとに示しています。  |ディストリビューション|OpenJDK バージョン| |------------|---------------| |RHEL 8|1.8.0| |RHEL 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.
ja	### Java gateway のインストール  JMXアプリケーションを監視する場合のみ、[Java gateway](/manual/concepts/java)をインストールする必要があります。<br> Javaゲートウェイは軽量で、データベースを必要としません。  必要なリポジトリが追加されたら、以下のコマンドラインを実行することでZabbix Javaをインストールできます:    # dnf install zabbix-java-gateway  Java gatewayの設定と実行の詳細については、[setup](/manual/java) を参照してください。

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).
ja	#### JavaScriptのメソッド  HTTPメソッド PATCH, HEAD, OPTIONS, TRACE, CONNECT をJavaScriptエンジンに追加しました。また、新しい JS メソッド HttpRequest.customRequest を使って、カスタム HTTPメソッドのリクエストを送信できるようになりました。  [追加のJavaScriptオブジェクト](/manual/config/items/preprocessing/javascript/javascript_objects)もあわせて参照してください。

en-us	#### JavaScript preprocessing  JavaScript preprocessing is done by invoking JavaScript function with a single parameter 'value' and user provided function body. The preprocessing step result is the value returned from this function, for example, to perform Fahrenheit to Celsius conversion user must enter:      return (value - 32)  * 5 / 9  in JavaScript preprocessing parameters, which will be wrapped into a JavaScript function by server:  ``` {.java} function (value) {    return (value - 32) * 5 / 9 } ```  The input parameter 'value' is always passed as a string. The return value is automatically coerced to string via ToString() method (if it fails then the error is returned as string value), with a few exceptions:  -   returning undefined value will result in an error -   returning null value will cause the input value to be discarded,     much like 'Discard value' preprocessing on 'Custom on fail' action.  Errors can be returned by throwing values/objects (normally either strings or Error objects).  For example:  ``` {.java} if (value == 0)     throw "Zero input value" return 1/value ```  Each script has a 10 second execution timeout (depending on the script it might take longer for the timeout to trigger); exceeding it will return error. A 512-megabyte heap limit is enforced (64 megabytes before Zabbix 6.0.19).  The JavaScript preprocessing step bytecode is cached and reused when the step is applied next time. Any changes to the item's preprocessing steps will cause the cached script to be reset and recompiled later.  Consecutive runtime failures (3 in a row) will cause the engine to be reinitialized to mitigate the possibility of one script breaking the execution environment for the next scripts (this action is logged with DebugLevel 4 and higher).  JavaScript preprocessing is implemented with Duktape (<https://duktape.org/>) JavaScript engine.  See also: [Additional JavaScript objects and global functions](/manual/config/items/preprocessing/javascript/javascript_objects)
ja	#### JavaScriptのプリプロセッシング  JavaScriptのプリプロセッシングは、JavaScriptの関数を1つのパラメータ'値'とユーザー提供の関数本体で呼び出すことで行われます。プリプロセッシングの結果は、この関数から返される値です。例えば、華氏から摂氏への変換を行う場合、ユーザーは次のように入力する必要があります。      return (value - 32)  * 5 / 9  JavaScript のプリプロセスパラメータは、server でJavaScript関数にラップされます。  ``` {.java} function (value) {    return (value - 32) * 5 / 9 } ```  入力パラメータ'値'は常に文字列として渡されます。戻り値はいくつかの例外とともに<br> 自動的に ToString() メソッドで文字列に変換されます (失敗した場合は、エラーが文字列として返されます)  - 未定義の値を返すとエラーになります。 - null値を返すと、入力値が破棄されます。これは*失敗時のカスタマイズ*の*値を破棄*と似た動作になります。  エラーは、値/オブジェクト (通常は文字列またはエラー オブジェクト) をスローすることによって返されます。<br>  例:  ``` {.java} if (value == 0)     throw "Zero input value" return 1/value ```  JavaScript の前処理ステップのバイトコードはキャッシュされ、次回ステップが適用されたときに再利用されます。アイテムの保存前処理ステップに変更を加えると、キャッシュされたスクリプトがリセットされ、後で再コンパイルされます。  連続したランタイムエラー(3回連続)が発生すると、1つのスクリプトによって次のスクリプトの実行環境が破壊される可能性を軽減するために、エンジンが再初期化されます (このアクションは、デバッグ レベル 4 以上でログに記録されます)。  JavaScriptの保存前処理は、Duktape(<https://duktape.org/>) JavaScriptエンジンを使用して実装されています。  参照: [追加のJavaScriptオブジェクトとグローバル関数](/manual/config/items/preprocessing/javascript/javascript_objects)

en-us	### JavaScript preprocessing  The heap limit for scripts has been upped from 64 to 512 megabytes.
ja	### JavaScript プリプロセッシング  スクリプトのヒープ制限が 64 メガバイトから 512 メガバイトに引き上げられました。

en-us	#### JMX item keys in more detail
ja	#### JMX item キーの詳細

en-us	#### JMX monitoring  See [JMX monitoring](/manual/config/items/itemtypes/jmx_monitoring) page for more details.
ja	#### 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.
ja	#### 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.
ja	#### 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.
ja	#### 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. 
ja	### JMX モニタリング  テンプレート *Generic Java JMX* は、メモリプールとガベージコレクタのローレベルディスカバリのための検知ルールを含むようになりました。

en-us	 #### JSONPath parsing errors in Zabbix 6.0.11  JSONPath parsing errors occur in case of leading whitespace and empty array/object. Fixed in Zabbix 6.0.12.
ja	 #### Zabbix 6.0.11でのJSONPath解析エラー  JSONPath解析エラーは、先頭の空白と空の配列/オブジェクトの場合に発生します。 Zabbix 6.0.12 で修正されました。

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.
ja	 ### 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. :::
ja	#### ヒストリの保持  ヒストリを何日間残すかを設定することができます。  - アイテムの[設定画面](/manual/config/items/item) で設定できます。 - アイテムの一括更新時 - データの保存期間の[設定](/manual/web_interface/frontend_sections/administration/general#housekeeper)を行う時  古いデータは、housekeeperプロセスによって削除されます。  一般的なアドバイスとして、ヒストリはできるだけ少ない日数で保存し、多くのヒストリの値でデータベースに負荷をかけないようにすることが重要です。  例えば、ヒストリを14日間、トレンドを5年間保存することができます。  ヒストリとトレンドのデータでどれくらいの容量が必要かは、[データベースのサイジング](/manual/installation/requirements#database_size)を参照してください。  グラフは古いデータを表示するためにトレンドの値を使用するので、短いヒストリの保存期間であっても、グラフで古いデータを確認することができます。  ::: noteimportant ヒストリの保存期間を'0'に設定すると、アイテムが更新されるのは 依存アイテムとインベントリのみを更新します。<br> トリガー条件式の評価はヒストリの値にのみ基づいて行われるため、トリガー関数は評価されません。<br> :::   ::: 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. :::
ja	#### トレンドの保持  トレンドは、数値データタイプの1時間あたりの最小値、最大値、平均値、および合計値を保存するために組み込まれたヒストリデータ削減メカニズムです。  トレンドは何日間保存されるかを設定することができます。  - アイテムの[設定画面](/manual/config/items/item)で設定できます。 - アイテムの一括更新時 - データの保存期間を設定するとき  トレンドは通常、ヒストリよりもはるかに長い期間保持することができます。古いデータはhousekeeperプロセスによって削除されます。  Zabbixサーバーは、データが流入するにつれて、実行時にトレンドデータをトレンドキャッシュに蓄積します。サーバーは、以下のような場合、すべてのアイテムの**前の1時間**のトレンド をデータベース(Webインターフェースが検索可能な場所)にフラッシュします：  - サーバーがそのアイテムの最初の現在時刻の値を受信したとき - 現在の時間が残り5分以下で、まだそのアイテムの現在の時間の値がないとき - サーバーが停止するとき  グラフでトレンドを見るには、少なくとも次の時間の始まりまで（アイテムが頻繁に更新される場合）、最大でも次の時間の終わりまで（アイテムがほとんど更新されない場合）、つまり最大2時間待つ必要があります。<br>  サーバーがトレンドキャッシュをフラッシュし、データベースにその時間のトレンドが既にある場合<br> （例えば、サーバーが時間の途中で再起動した場合）、サーバーは単純な挿入の代わりに更新ステートメントを使用する必要があります。<br> したがって、大規模なインストールで再起動が必要な場合は、トレンドデータの重複を避けるために、ある時間の終わりにサーバーを停止し、次の時間の初めに開始することが望ましいです。<br>  ヒストリテーブルはトレンドの生成には一切関与しません。  ::: noteimportant トレンドの保存期間が '0' に設定されている場合、Zabbixサーバーはトレンドの計算や保存を全く行いません。 :::  ::: noteclassic トレンドは元の値と同じデータ型で計算され、保存されます。その結果、符号なしデータ型の値の平均値の計算は丸められ、値の間隔が狭いほど結果の精度は低くなります。例えば、項目が0と1の値を持つ場合、平均値は0.5ではなく、0になります。  また、サーバーを再起動すると、符号なしデータ型の平均値の計算の精度が落ちることがあります。<br> :::

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.|
ja	##### カーネルデータ  |アイテムキー|<|<|<| |--|--|------|------| |説明|戻り値|パラメータ|コメント| |**kernel.maxfiles**|<|<|<| |OS がサポートするオープン ファイルの最大数|Integer| | | |**kernel.maxproc**|<|<|<| |OS がサポートするプロセスの最大数|Integer| | | |**kernel.openfiles**|<|<|<| |現在開いているファイル記述子の数|Integer| |このアイテムは 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.
ja	### キーボードによるナビゲーション  フロントエンドのインフォメーションアイコンにキーボードコントロールが実装されました。 これによりキーボードで情報アイコンにフォーカスし、ヒントを開くことができるようになりました。

en-us	 |Key|<|<|<|<| |---|-|-|-|-| |<|**Description**|**Return value**|**Parameters**|**Comments**| |agent.hostmetadata|<|<|<|<| |<|Agent host metadata.|String||Returns the value of HostMetadata or HostMetadataItem parameters, or empty string if none are defined.<br><br>Supported since Zabbix 6.0.| |agent.hostname|<|<|<|<| |<|Agent host name.|String| |Returns:<br>As passive check - the name of the first host listed in the Hostname parameter of the agent configuration file;<br>As active check - the name of the current hostname.| |agent.ping|<|<|<|<| |<|Agent availability check.|Nothing - unavailable<br><br>1 - available| |Use the **nodata()** trigger function to check for host unavailability.| |agent.variant|<|<|<|<| |<|Variant of Zabbix agent (Zabbix agent or Zabbix agent 2).|Integer| |Example of returned value:<br>1 - Zabbix agent<br>2 - Zabbix agent 2| |agent.version|<|<|<|<| |<|Version of Zabbix agent.|String| |Example of returned value:<br>6.0.3| |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 on Linux only since Zabbix 6.0.| |log\[file,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Monitoring of a log file.|Log|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0)- possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> log\[/var/log/syslog\]<br>=> log\[/var/log/syslog,error\]<br>=> log\[/home/zabbix/logs/logfile,,,100\]<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> log\[/app1/app.log,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> log\[/app1/app.log,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |log.count\[file,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Count of matched lines in a monitored log file.|Integer|**file** - full path and name of log file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.4.7) - additional options:<br>*mtime-noreread* - non-unique records, reread only if the file size changes (ignore modification time change). (This parameter is deprecated since 5.0.2, because now mtime is ignored.)<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>If file is missing or permissions do not allow access, item turns unsupported.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |logrt\[file\_regexp,\<regexp\>,\<encoding\>,\<maxlines\>,\<mode\>,\<output\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Monitoring of a log file that is rotated.|Log|**file\_regexp** - absolute path to file and the file name described by a regular [expression](/manual/regular_expressions#overview). *Note* that only the file name is a regular expression<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxlines** - maximum number of new lines per second the agent will send to Zabbix server or proxy. This parameter overrides the value of 'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd)<br>**mode** (since version 2.0) - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**output** (since version 2.2) - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).<br>**maxdelay** (since version 3.2) - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>Note that logrt is designed to work with one currently active log file, with several other matching inactive files rotated. If, for example, a directory has many active log files, a separate logrt item should be created for each one. Otherwise if one logrt item picks up too many files it may lead to exhausted memory and a crash of monitoring.<br><br>If `output` is left empty - the whole line containing the matched text is returned. Note that all global regular expression types except 'Result is TRUE' always return the whole matched line and the `output` parameter is ignored.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>Examples:<br>=> logrt\["/home/zabbix/logs/\^logfile\[0-9\]{1,3}$",,,100\] → will match a file like "logfile1" (will not match ".logfile1")<br>=> logrt\["/home/user/\^logfile\_.\*\_\[0-9\]{1,3}$","pattern\_to\_match","UTF-8",100\] → will collect data from files such "logfile\_abc\_1" or "logfile\_\_001".<br><br>*Using `output` parameter for extracting a number from log record:*<br>=> logrt\[/app1/\^test.\*log$,"task run \[0-9.\]+ sec, processed (\[0-9\]+) records, \[0-9\]+ errors",,,,\\1\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send only '6080' to server. Because a numeric value is being sent, the "Type of information" for this item can be set to "Numeric (unsigned)" and the value can be used in graphs, triggers etc.<br><br>*Using `output` parameter for rewriting log record before sending to server:*<br>=> logrt\[/app1/\^test.\*log$,"(\[0-9 :-\]+) task run (\[0-9.\]+) sec, processed (\[0-9\]+) records, (\[0-9\]+) errors",,,,"\\1 RECORDS: \\3, ERRORS: \\4, DURATION: \\2"\] → will match a log record "2015-11-13 10:08:26 task run 6.08 sec, processed 6080 records, 0 errors" and send a modified record "2015-11-13 10:08:26 RECORDS: 6080, ERRORS: 0, DURATION: 6.08" to server.<br><br>See also additional information on [log monitoring](log_items).| |logrt.count\[file\_regexp,\<regexp\>,\<encoding\>,\<maxproclines\>,\<mode\>,\<maxdelay\>,\<options\>,\<persistent\_dir\>\]|<|<|<|<| |<|Count of matched lines in a monitored log file that is rotated.|Integer|**file\_regexp** - absolute path to file and regular [expression](/manual/regular_expressions#overview) describing the file name pattern<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required content pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**maxproclines** - maximum number of new lines per second the agent will analyze (cannot exceed 10000). Default value is 10\*'MaxLinesPerSecond' in [zabbix\_agentd.conf](/manual/appendix/config/zabbix_agentd).<br>**mode** - possible values:<br>*all* (default), *skip* - skip processing of older data (affects only newly created items).<br>**maxdelay** - maximum delay in seconds. Type: float. Values: 0 - (default) never ignore log file lines; > 0.0 - ignore older lines in order to get the most recent lines analyzed within "maxdelay" seconds. Read the [maxdelay](log_items#using_maxdelay_parameter) notes before using it!<br>**options** (since version 4.0; *mtime-reread*, *mtime-noreread* options since 4.4.7) - type of log file rotation and other options. Possible values:<br>*rotate* (default),<br>*copytruncate* - note that *copytruncate* cannot be used together with *maxdelay*. In this case *maxdelay* must be 0 or not specified; see [copytruncate](log_items#notes_on_handling_copytruncate_log_file_rotation) notes,<br>*mtime-reread* - non-unique records, reread if modification time or size changes (default),<br>*mtime-noreread* - non-unique records, reread only if the size changes (ignore modification time change).<br>**persistent\_dir** (since versions 5.0.18, 5.4.9, only in zabbix\_agentd on Unix systems; not supported in Agent2) - absolute pathname of directory where to store persistent files. See also additional notes on [persistent files](log_items#notes-on-persistent-files-for-log-items).|The item must be configured as an [active check](/manual/appendix/items/activepassive#active_checks).<br>Log rotation is based on the last modification time of files.<br><br>See also additional information on [log monitoring](log_items).<br><br>This item is not supported for Windows Event Log.<br><br>Supported since Zabbix 3.2.0.| |modbus.get\[endpoint,<slave id>,<function>,<address>,<count>,<type>,<endianness>,<offset>\]|<|<|<|<| |<|Reads Modbus data.|JSON object|**endpoint** - endpoint defined as `protocol://connection_string`<br>**slave id** - slave ID<br>**function** - Modbus function<br>**address** - address of first registry, coil or input<br>**count** - number of records to read<br>**type** - type of data<br>**endianness** - endianness configuration<br>**offset** - number of registers, starting from 'address', the results of which will be discarded.<br><br>See a [detailed description](/manual/appendix/items/modbus) of parameters.|Supported since Zabbix 5.2.0.| |net.dns\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Checks if DNS service is up.|0 - DNS is down (server did not respond or DNS resolution failed)<br><br>1 - DNS is up|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol** (since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns*| |net.dns.record\[<ip>,name,<type>,<timeout>,<count>,<protocol>\]|<|<|<|<| |<|Performs a DNS query.|Character string with the required type of information|**ip** - IP address of DNS server (leave empty for the default DNS server, ignored on Windows)<br>**name** - DNS name to query<br>**type** - record type to be queried (default is *SOA*)<br>**timeout** (ignored on Windows) - timeout for the request in seconds (default is 1 second)<br>**count** (ignored on Windows) - number of tries for the request (default is 2)<br>**protocol**(since version 3.0) - the protocol used to perform DNS queries: *udp* (default) or *tcp*|Example:<br>=> net.dns.record\[8.8.8.8,example.com,MX,2,1\]<br><br>The possible values for `type` are:<br>*ANY*, *A*, *NS*, *CNAME*, *MB*, *MG*, *MR*, *PTR*, *MD*, *MF*, *MX*, *SOA*, *NULL*, *WKS* (except for Windows), *HINFO*, *MINFO*, *TXT*, *SRV*<br><br>Internationalized domain names are not supported, please use IDNA encoded names instead.<br><br>SRV record type is supported since Zabbix 1.8.6 (Unix) and 2.0.0 (Windows).<br><br>Naming before Zabbix 2.0 (still supported): *net.tcp.dns.query*| |net.if.collisions\[if\]|<|<|<|<| |<|Number of out-of-window collisions.|Integer|**if** - network interface name| | |net.if.discovery|<|<|<|<| |<|List of network interfaces. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>On FreeBSD, OpenBSD and NetBSD supported since Zabbix 2.2.<br><br>Some Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names.| |net.if.in\[if,<mode>\]|<|<|<|<| |<|Incoming traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*frame* - the number of packet framing errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver<br>*multicast* - the number of multicast frames received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix 1.8.6.<br><br>Examples:<br>=> net.if.in\[eth0,errors\]<br>=> net.if.in\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.out\[if,<mode>\]|<|<|<|<| |<|Outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*collisions (colls)* - the number of collisions detected on the interface<br>*carrier* - the number of carrier losses detected by the device driver<br>*compressed* - the number of compressed packets transmitted by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Multi-byte interface names on Windows are supported since Zabbix agent 1.8.6 version.<br><br>Examples:<br>=> net.if.out\[eth0,errors\]<br>=> net.if.out\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.| |net.if.total\[if,<mode>\]|<|<|<|<| |<|Sum of incoming and outgoing traffic statistics on network interface.|Integer|**if** - network interface name (Unix); network interface full description or IPv4 address; or, if in braces, network interface GUID (Windows)<br>**mode** - possible values:<br>*bytes* - number of bytes (default)<br>*packets* - number of packets<br>*errors* - number of errors<br>*dropped* - number of dropped packets<br>*overruns (fifo)* - the number of FIFO buffer errors<br>*compressed* - the number of compressed packets transmitted or received by the device driver|On Windows, the item gets values from 64-bit counters if available. 64-bit interface statistic counters were introduced in Windows Vista and Windows Server 2008. If 64-bit counters are not available, the agent uses 32-bit counters.<br><br>Examples:<br>=> net.if.total\[eth0,errors\]<br>=> net.if.total\[eth0\]<br><br>You may obtain network interface descriptions on Windows with net.if.discovery or net.if.list items.<br><br>You may use this key with the *Change per second* preprocessing step in order to get bytes per second statistics.<br><br>Note that dropped packets are supported only if both net.if.in and net.if.out work for dropped packets on your platform.| |net.tcp.listen\[port\]|<|<|<|<| |<|Checks if this TCP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - TCP port number|Example:<br>=> net.tcp.listen\[80\]<br><br>On Linux supported since Zabbix 1.8.4<br><br>Since Zabbix 3.0.0, on Linux kernels 2.6.14 and above, information about listening TCP sockets is obtained from the kernel's NETLINK interface, if possible. Otherwise, the information is retrieved from /proc/net/tcp and /proc/net/tcp6 files.| |net.tcp.port\[<ip>,port\]|<|<|<|<| |<|Checks if it is possible to make TCP connection to specified port.|0 - cannot connect<br><br>1 - can connect|**ip** - IP or DNS name (default is 127.0.0.1)<br>**port** - port number|Example:<br>=> net.tcp.port\[,80\] → can be used to test availability of web server running on port 80.<br><br>For simple TCP performance testing use net.tcp.service.perf\[tcp,<ip>,<port>\]<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).| |net.tcp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and accepting TCP connections.|0 - service is down<br><br>1 - service is running|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service\[ftp,,45\] → can be used to test the availability of FTP server on TCP port 45.<br><br>Note that these checks may result in additional messages in system daemon logfiles (SMTP and SSH sessions being logged usually).<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.port for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of TCP service.|0 - service is down<br><br>seconds - the number of seconds spent while connecting to the service|**service** - either of:<br>*ssh*, *ldap*, *smtp*, *ftp*, *http*, *pop*, *nntp*, *imap*, *tcp*, *https*, *telnet* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.tcp.service.perf\[ssh\] → can be used to test the speed of initial response from SSH server.<br><br>Checking of encrypted protocols (like IMAP on port 993 or POP on port 995) is currently not supported. As a workaround, please use net.tcp.service.perf\[tcp,<ip>,<port>\] for checks like these.<br><br>Checking of LDAP and HTTPS on Windows is only supported by Zabbix agent 2.<br><br>Note that the telnet check looks for a login prompt (':' at the end).<br><br>See also [known issues](/manual/installation/known_issues#https_checks) of checking HTTPS service.<br><br>*https* and *telnet* services are supported since Zabbix 2.0.| |net.tcp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *syn\_sent*, *syn\_recv*, *fin\_wait1*, *fin\_wait2*, *time\_wait*, *close*, *close\_wait*, *last\_ack*, *listen*, *closing*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.tcp.socket.count\[,80,,,established\] → check if local TCP port 80 is in "established" state<br><br>This item is supported since Zabbix 6.0.| |net.udp.listen\[port\]|<|<|<|<| |<|Checks if this UDP port is in LISTEN state.|0 - it is not in LISTEN state<br><br>1 - it is in LISTEN state|**port** - UDP port number|Example:<br>=> net.udp.listen\[68\]<br><br>On Linux supported since Zabbix 1.8.4| |net.udp.service\[service,<ip>,<port>\]|<|<|<|<| |<|Checks if service is running and responding to UDP requests.|0 - service is down<br><br>1 - service is running|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service\[ntp,,45\] → can be used to test the availability of NTP service on UDP port 45.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.service.perf\[service,<ip>,<port>\]|<|<|<|<| |<|Checks performance of UDP service.|0 - service is down<br><br>seconds - the number of seconds spent waiting for response from the service|**service** - *ntp* (see [details](/manual/appendix/items/service_check_details))<br>**ip** - IP address (default is 127.0.0.1)<br>**port** - port number (by default standard service port number is used)|Example:<br>=> net.udp.service.perf\[ntp\] → can be used to test response time from NTP service.<br><br>This item is supported since Zabbix 3.0.0, but *ntp* service was available for net.tcp.service\[\] item in prior versions.| |net.udp.socket.count\[<laddr>,<lport>,<raddr>,<rport>,<state>\]|<|<|<|<| |<|Return the number of TCP sockets that match parameters.|Integer|**laddr** - local IPv4/6 address or CIDR subnet<br>**lport** - local port number or service name<br>**raddr** - remote IPv4/6 address or CIDR subnet<br>**rport** - remote port number or service name<br>**state** - connection state (*established*, *unconn*)|This item is supported on Linux only on both Zabbix agent/agent 2. On Zabbix agent 2 it is also supported on 64-bit Windows.<br><br>Example:<br>=> net.udp.socket.count\[,,,,listening\] → check if any UDP socket is in "listening" state<br><br>This item is supported since Zabbix 6.0.| |proc.cpu.util\[<name>,<user>,<type>,<cmdline>,<mode>,<zone>\]|<|<|<|<| |<|Process CPU utilization percentage.|Float|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**type** - CPU utilization type:<br>*total* (default), *user*, *system*<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**mode** - data gathering mode: *avg1* (default), *avg5*, *avg15*<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.cpu.util\[,root\] → CPU utilization of all processes running under the "root" user<br>=> proc.cpu.util\[zabbix\_server,zabbix\] → CPU utilization of all zabbix\_server processes running under the zabbix user<br><br>The returned value is based on single CPU core utilization percentage. For example CPU utilization of a process fully using two cores is 200%.<br><br>The process CPU utilization data is gathered by a collector which supports the maximum of 1024 unique (by name, user and command line) queries. Queries not accessed during the last 24 hours are removed from the collector.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.<br><br>This key is supported since Zabbix 3.0.0 and is available on several platforms (see [Items supported by platform](/manual/appendix/items/supported_by_platform)).| |proc.mem\[<name>,<user>,<mode>,<cmdline>,<memtype>\]|<|<|<|<| |<|Memory used by process in bytes.|Integer - with `mode` as *max*, *min*, *sum*<br><br>Float - with `mode` as *avg*|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**mode** - possible values:<br>*avg*, *max*, *min*, *sum* (default)<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**memtype** - [type of memory](/manual/appendix/items/proc_mem_notes) used by process|Examples:<br>=> proc.mem\[,root\] → memory used by all processes running under the "root" user<br>=> proc.mem\[zabbix\_server,zabbix\] → memory used by all zabbix\_server processes running under the zabbix user<br>=> proc.mem\[,oracle,max,oracleZABBIX\] → memory used by the most memory-hungry process running under oracle having oracleZABBIX in its command line<br><br>*Note*: When several processes use shared memory, the sum of memory used by processes may result in large, unrealistic values.<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.mem[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>The `memtype` parameter is supported on several [platforms](/manual/appendix/items/supported_by_platform) since Zabbix 3.0.0.| |proc.num\[<name>,<user>,<state>,<cmdline>,<zone>\]|<|<|<|<| |<|The number of processes.|Integer|**name** - process name (default is *all processes*)<br>**user** - user name (default is *all users*)<br>**state** (*disk* and *trace* options since version 3.4.0) - possible values:<br>*all* (default),<br>*disk* - uninterruptible sleep,<br>*run* - running,<br>*sleep* - interruptible sleep,<br>*trace* - stopped,<br>*zomb* - zombie<br>**cmdline** - filter by command line (it is a regular [expression](/manual/regular_expressions#overview))<br>**zone** - target zone: *current* (default), *all*. This parameter is supported on Solaris only.|Examples:<br>=> proc.num\[,mysql\] → number of processes running under the mysql user<br>=> proc.num\[apache2,www-data\] → number of apache2 processes running under the www-data user<br>=> proc.num\[,oracle,sleep,oracleZABBIX\] → number of processes in sleep state running under oracle having oracleZABBIX in its command line<br><br>See [notes](/manual/appendix/items/proc_mem_num_notes) on selecting processes with `name` and `cmdline` parameters (Linux-specific).<br><br>On Windows, only the `name` and `user` parameters are supported.<br><br>When this item is invoked from the command line and contains a command line parameter (e.g. using the agent test mode: `zabbix_agentd -t proc.num[,,,apache2]`), one extra process will be counted, as the agent will count itself.<br><br>*Note* that when setting the `zone` parameter to *current* (or default) in case the agent has been compiled on a Solaris without zone support, but running on a newer Solaris where zones are supported, then the agent will return NOTSUPPORTED (the agent cannot limit results to only the current zone). However, *all* is supported in this case.| |sensor\[device,sensor,<mode>\]|<|<|<|<| |<|Hardware sensor reading.|Float|**device** - device name<br>**sensor** - sensor name<br>**mode** - possible values:<br>*avg*, *max*, *min* (if this parameter is omitted, device and sensor are treated verbatim).|Reads /proc/sys/dev/sensors on Linux 2.4.<br><br>Example:<br>=> sensor\[w83781d-i2c-0-2d,temp1\]<br><br>Prior to Zabbix 1.8.4, the *sensor\[temp1\]* format was used.| |^|^|^|^|Reads /sys/class/hwmon on Linux 2.6+.<br><br>See a more detailed description of [sensor](/manual/appendix/items/sensor) item on Linux.| |^|^|^|^|Reads the *hw.sensors* MIB on OpenBSD.<br><br>Examples:<br>=> sensor\[cpu0,temp0\] → temperature of one CPU<br>=> sensor\["cpu\[0-2\]$",temp,avg\] → average temperature of the first three CPU's<br><br>Supported on OpenBSD since Zabbix 1.8.4.| |system.boottime|<|<|<|<| |<|System boot time.|Integer (Unix timestamp)| | | |system.cpu.discovery|<|<|<|<| |<|List of detected CPUs/CPU cores. Used for low-level discovery.|JSON object| |Supported on all platforms since 2.4.0.| |system.cpu.intr|<|<|<|<| |<|Device interrupts.|Integer| | | |system.cpu.load\[<cpu>,<mode>\]|<|<|<|<| |<|[CPU load](http://en.wikipedia.org/wiki/Load_(computing)).|Float|**cpu** - possible values:<br>*all* (default), *percpu* (since version 2.0; total load divided by online CPU count)<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*|Example:<br>=> system.cpu.load\[,avg5\].| |system.cpu.num\[<type>\]|<|<|<|<| |<|Number of CPUs.|Integer|**type** - possible values:<br>*online* (default), *max*|Example:<br>=> system.cpu.num| |system.cpu.switches|<|<|<|<| |<|Count of context switches.|Integer| | | |system.cpu.util\[<cpu>,<type>,<mode>,<logical\_or\_physical>\]|<|<|<|<| |<|CPU utilization percentage.|Float|**cpu** - *<CPU number>* or *all* (default)<br>**type** - possible values:<br>*user* (default), *idle*, *nice*, *system* (default for Windows), *iowait*, *interrupt*, *softirq*, *steal*, *guest* (on Linux kernels 2.6.24 and above), *guest\_nice* (on Linux kernels 2.6.33 and above).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.<br>**mode** - possible values:<br>*avg1* (one-minute average, default), *avg5*, *avg15*<br>**logical\_or\_physical** (since version 5.0.3; on AIX only) - possible values: *logical* (default), *physical*. This parameter is supported on AIX only.|Example:<br>=> system.cpu.util\[0,user,avg5\]<br><br>Old naming: *system.cpu.idleX, system.cpu.niceX, system.cpu.systemX, system.cpu.userX*| |system.hostname\[<type>, <transform>\]|<|<|<|<| |<|System host name.|String|**type** (before version 5.4.7 supported on Windows only) - possible values: *netbios* (default on Windows), *host* (default on Linux), *shorthost* (since version 5.4.7; returns part of the hostname before the first dot, a full string for names without dots).<br>**transform** (since version 5.4.7) - possible values:<br>*none* (default), *lower* (convert to lowercase)|The value is acquired by either GetComputerName() (for **netbios**) or gethostname() (for **host**) functions on Windows and by "hostname" command on other systems.<br><br>Examples of returned values:<br>*on Linux*:<br>=> system.hostname → linux-w7x1<br>=> system.hostname → example.com<br>=> system.hostname\[shorthost\] → example<br>*on Windows*:<br>=> system.hostname → WIN-SERV2008-I6<br>=> system.hostname\[host\] → Win-Serv2008-I6LonG<br>=> system.hostname\[host,lower\] → win-serv2008-i6long<br><br>See also a [more detailed description](/manual/appendix/install/windows_agent#configuration).| |system.hw.chassis\[<info>\]|<|<|<|<| |<|Chassis information.|String|**info** - one of full (default), model, serial, type or vendor|Example: system.hw.chassis\[full\]<br>Hewlett-Packard HP Pro 3010 Small Form Factor PC CZXXXXXXXX Desktop\]<br><br>This key depends on the availability of the [SMBIOS](http://en.wikipedia.org/wiki/System_Management_BIOS) table.<br>Will try to read the DMI table from sysfs, if sysfs access fails then try reading directly from memory.<br><br>**Root permissions** are required because the value is acquired by reading from sysfs or memory.<br><br>Supported since Zabbix 2.0.| |system.hw.cpu\[<cpu>,<info>\]|<|<|<|<| |<|CPU information.|String or integer|**cpu** - *<CPU number>* or *all* (default)<br>**info** - possible values:<br>*full* (default), *curfreq*, *maxfreq*, *model* or *vendor*|Example:<br>=> system.hw.cpu\[0,vendor\] → AuthenticAMD<br><br>Gathers info from /proc/cpuinfo and /sys/devices/system/cpu/\[cpunum\]/cpufreq/cpuinfo\_max\_freq.<br><br>If a CPU number and *curfreq* or *maxfreq* is specified, a numeric value is returned (Hz).<br><br>Supported since Zabbix 2.0.| |system.hw.devices\[<type>\]|<|<|<|<| |<|Listing of PCI or USB devices.|Text|**type** (since version 2.0) - *pci* (default) or *usb*|Example:<br>=> system.hw.devices\[pci\] → 00:00.0 Host bridge: Advanced Micro Devices \[AMD\] RS780 Host Bridge<br>\[..\]<br><br>Returns the output of either lspci or lsusb utility (executed without any parameters).| |system.hw.macaddr\[<interface>,<format>\]|<|<|<|<| |<|Listing of MAC addresses.|String|**interface** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**format** - *full* (default) or *short*|Lists MAC addresses of the interfaces whose name matches the given `interface` regular [expression](/manual/regular_expressions#overview) (*all* lists for all interfaces).<br><br>Example:<br>=> system.hw.macaddr\["eth0$",full\] → \[eth0\] 00:11:22:33:44:55<br><br>If `format` is specified as *short*, interface names and identical MAC addresses are not listed.<br><br>Supported since Zabbix 2.0.| |system.localtime\[<type>\]|<|<|<|<| |<|System time.|Integer - with `type` as *utc*<br><br>String - with `type` as *local*|**type** (since version 2.0) - possible values:<br>*utc* - (default) the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds.<br>*local* - the time in the 'yyyy-mm-dd,hh:mm:ss.nnn,+hh:mm' format<br>|Must be used as a [passive check](/manual/appendix/items/activepassive#passive_checks) only.<br><br>Example:<br>=> system.localtime\[local\] → create an item using this key and then use it to display host time in the *Clock* [dashboard widget](/manual/web_interface/frontend_sections/monitoring/dashboard/widgets#clock).| |system.run\[command,<mode>\]|<|<|<|<| |<|Run specified command on the host.|Text result of the command<br><br>1 - with `mode` as *nowait* (regardless of command result)|**command** - command for execution<br>**mode** - possible values:<br>*wait* - wait end of execution (default),<br>*nowait* - do not wait|Up to 512KB of data can be returned, including trailing whitespace that is truncated.<br>To be processed correctly, the output of the command must be text.<br><br>Example:<br>=> system.run\[ls -l /\] → detailed file list of root directory.<br><br>*Note*: system.run items are disabled by default. Learn how to [enable them](/manual/config/items/restrict_checks).<br><br>The return value of the item is standard output together with standard error produced by command. The exit code is not checked.<br><br>Empty result is allowed starting with Zabbix 2.4.0.<br>See also: [Command execution](/manual/appendix/command_execution).| |system.stat\[resource,<type>\]|<|<|<|<| |<|System statistics.|Integer or float|**ent** - number of processor units this partition is entitled to receive (float)<br>**kthr,<type>** - information about kernel thread states:<br>*r* - average number of runnable kernel threads (float)<br>*b* - average number of kernel threads placed in the Virtual Memory Manager wait queue (float)<br>**memory,<type>** - information about the usage of virtual and real memory:<br>*avm* - active virtual pages (integer)<br>*fre* - size of the free list (integer)<br>**page,<type>** - information about page faults and paging activity:<br>*fi* - file page-ins per second (float)<br>*fo* - file page-outs per second (float)<br>*pi* - pages paged in from paging space (float)<br>*po* - pages paged out to paging space (float)<br>*fr* - pages freed (page replacement) (float)<br>*sr* - pages scanned by page-replacement algorithm (float)<br>**faults,<type>** - trap and interrupt rate:<br>*in* - device interrupts (float)<br>*sy* - system calls (float)<br>*cs* - kernel thread context switches (float)<br>**cpu,<type>** - breakdown of percentage usage of processor time:<br>*us* - user time (float)<br>*sy* - system time (float)<br>*id* - idle time (float)<br>*wa* - idle time during which the system had outstanding disk/NFS I/O request(s) (float)<br>*pc* - number of physical processors consumed (float)<br>*ec* - the percentage of entitled capacity consumed (float)<br>*lbusy* - indicates the percentage of logical processor(s) utilization that occurred while executing at the user and system level (float)<br>*app* - indicates the available physical processors in the shared pool (float)<br>**disk,<type>** - disk statistics:<br>*bps* - indicates the amount of data transferred (read or written) to the drive in bytes per second (integer)<br>*tps* - indicates the number of transfers per second that were issued to the physical disk/tape (float)|<| |<|^|^|Comments|<| |<|^|^|This item is [supported](/manual/appendix/items/supported_by_platform) on AIX only, since Zabbix 1.8.1.<br>Take note of the following limitations in these items:<br>=> system.stat\[cpu,app\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,ec\] - supported on AIX LPAR of type "Shared" and "Dedicated" ("Dedicated" always returns 100 (percent))<br>=> system.stat\[cpu,lbusy\] - supported only on AIX LPAR of type "Shared"<br>=> system.stat\[cpu,pc\] - supported on AIX LPAR of type "Shared" and "Dedicated"<br>=> system.stat\[ent\] - supported on AIX LPAR of type "Shared" and "Dedicated"|<| |system.sw.arch|<|<|<|<| |<|Software architecture information.|String| |Example:<br>=> system.sw.arch → i686<br><br>Info is acquired from uname() function.<br><br>Supported since Zabbix 2.0.| |system.sw.os\[<info>\]|<|<|<|<| |<|Operating system information.|String|**info** - possible values:<br>*full* (default), *short* or *name*|Example:<br>=> system.sw.os\[short\]→ Ubuntu 2.6.35-28.50-generic 2.6.35.11<br><br>Info is acquired from (note that not all files and options are present in all distributions):<br>/proc/version (*full*)<br>/proc/version\_signature (*short*)<br>PRETTY\_NAME parameter from /etc/os-release on systems supporting it, or /etc/issue.net (*name*)<br><br>Supported since Zabbix 2.0.| |system.sw.packages\[<package>,<manager>,<format>\]|<|<|<|<| |<|Listing of installed packages.|Text|**package** - *all* (default) or a regular [expression](/manual/regular_expressions#overview)<br>**manager** - *all* (default) or a package manager<br>**format** - *full* (default) or *short*|Lists (alphabetically) installed packages whose name matches the given `package` regular [expression](/manual/regular_expressions#overview) (*all* lists them all).<br><br>Example:<br>=> system.sw.packages\[mini,dpkg,short\] → python-minimal, python2.6-minimal, ubuntu-minimal<br><br>Supported package managers (executed command):<br>dpkg (dpkg --get-selections)<br>pkgtool (ls /var/log/packages)<br>rpm (rpm -qa)<br>pacman (pacman -Q)<br><br>If `format` is specified as *full*, packages are grouped by package managers (each manager on a separate line beginning with its name in square brackets).<br>If `format` is specified as *short*, packages are not grouped and are listed on a single line.<br><br>Supported since Zabbix 2.0.| |system.swap.in\[<device>,<type>\]|<|<|<|<| |<|Swap in (from device into memory) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapins), *sectors* (sectors swapped in), *pages* (pages swapped in).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.in\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.out\[<device>,<type>\]|<|<|<|<| |<|Swap out (from memory onto device) statistics.|Integer|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*count* (number of swapouts), *sectors* (sectors swapped out), *pages* (pages swapped out).<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.out\[,pages\]<br><br>The source of this information is:<br>/proc/swaps, /proc/partitions, /proc/stat (Linux 2.4)<br>/proc/swaps, /proc/diskstats, /proc/vmstat (Linux 2.6)| |system.swap.size\[<device>,<type>\]|<|<|<|<| |<|Swap space size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**device** - device used for swapping (default is *all*)<br>**type** - possible values:<br>*free* (free swap space, default), *pfree* (free swap space, in percent), *pused* (used swap space, in percent), *total* (total swap space), *used* (used swap space)<br>Note that *pfree*, *pused* are not supported on Windows if swap size is 0.<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) details for this parameter.|Example:<br>=> system.swap.size\[,pfree\] → free swap space percentage<br><br>If *device* is not specified Zabbix agent will only take into account swap devices (files), physical memory will be ignored. For example, on Solaris systems *swap -s* command includes a portion of physical memory and swap devices (unlike *swap -l*).<br><br>Note that this key might report incorrect swap space size/percentage on virtualized (VMware ESXi, VirtualBox) Windows platforms. In this case you may use the `perf_counter[\700(_Total)\702]` key to obtain correct swap space percentage.| |system.uname|<|<|<|<| |<|Identification of the system.|String| |Example of returned value (Unix):<br>FreeBSD localhost 4.2-RELEASE FreeBSD 4.2-RELEASE \#0: Mon Nov i386<br><br>Example of returned value (Windows):<br>Windows ZABBIX-WIN 6.0.6001 Microsoft® Windows Server® 2008 Standard Service Pack 1 x86<br><br>On Unix since Zabbix 2.2.0 the value for this item is obtained with uname() system call. Previously it was obtained by invoking "uname -a". The value of this item might differ from the output of "uname -a" and does not include additional information that "uname -a" prints based on other sources.<br><br>On Windows since Zabbix 3.0 the value for this item is obtained from Win32\_OperatingSystem and Win32\_Processor WMI classes. Previously it was obtained from volatile Windows APIs and undocumented registry keys. The OS name (including edition) might be translated to the user's display language. On some versions of Windows it contains trademark symbols and extra spaces.<br><br>Note that on Windows the item returns OS architecture, whereas on Unix it returns CPU architecture.| |system.uptime|<|<|<|<| |<|System uptime in seconds.|Integer| |In [item configuration](/manual/config/items/item#configuration), use **s** or **uptime** units to get readable values.| |system.users.num|<|<|<|<| |<|Number of users logged in.|Integer| |**who** command is used on the agent side to obtain the value.| |vfs.dev.discovery|<|<|<|<| |<|List of block devices and their type. Used for low-level discovery.|JSON object| |This item is supported on Linux platform only.<br><br>Supported since Zabbix 4.4.0.| |vfs.dev.read\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk read statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.read\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 devices (1023 individual and one for *all*).| |vfs.dev.write\[<device>,<type>,<mode>\]|<|<|<|<| |<|Disk write statistics.|Integer - with `type` in *sectors*, *operations*, *bytes*<br><br>Float - with `type` in *sps*, *ops*, *bps*<br><br>*Note*: if using an update interval of three hours or more^**[2](#footnotes)**^, will always return '0'|**device** - disk device (default is *all* ^**[3](#footnotes)**^)<br>**type** - possible values: *sectors*, *operations*, *bytes*, *sps*, *ops*, *bps*<br>Note that 'type' parameter support and defaults depend on the platform. See [platform-specific](/manual/appendix/items/supported_by_platform) details.<br>*sps*, *ops*, *bps* stand for: sectors, operations, bytes per second, respectively.<br>**mode** - possible values: *avg1* (one-minute average, default), *avg5*, *avg15*.<br>This parameter is supported only with `type` in: sps, ops, bps.|You may use relative device names (for example, `sda`) as well as an optional /dev/ prefix (for example, `/dev/sda`).<br><br>LVM logical volumes are supported.<br><br>Default values of 'type' parameter for different OSes:<br>AIX - operations<br>FreeBSD - bps<br>Linux - sps<br>OpenBSD - operations<br>Solaris - bytes<br><br>Example:<br>=> vfs.dev.write\[,operations\]<br><br>*sps*, *ops* and *bps* on supported platforms used to be limited to 8 devices (7 individual and one *all*). Since Zabbix 2.0.1 this limit is 1024 (1023 individual and one for *all*).| |vfs.dir.count\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry count.|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to count, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT count. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT counted.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be counted. Smaller files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be counted. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be counted. More recent entries will not be counted. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be counted. Entries so old and older will not be counted (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never counted.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are counted only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be counted).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial count will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.count\[/dev\] - monitors number of devices in /dev (Linux)<br>⇒ vfs.dir.count\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - monitors number of files in temporary directory (Windows)<br><br>Supported since Zabbix 4.0.0.| |vfs.dir.get\[dir,<regex\_incl>,<regex\_excl>,<types\_incl>,<types\_excl>,<max\_depth>,<min\_size>,<max\_size>,<min\_age>,<max\_age>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory entry list.|JSON|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**types\_incl** - directory entry types to list, possible values:<br>*file* - regular file, *dir* - subdirectory, *sym* - symbolic link, *sock* - socket, *bdev* - block device, *cdev* - character device, *fifo* - FIFO, *dev* - synonymous with "bdev,cdev", *all* - all types (default), i.e. "file,dir,sym,sock,bdev,cdev,fifo". Multiple types must be separated with comma and quoted.<br>**types\_excl** - directory entry types (see <types\_incl>) to NOT list. If some entry type is in both <types\_incl> and <types\_excl>, directory entries of this type are NOT listed.<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**min\_size** - minimum size (in bytes) for file to be listed. Smaller files will not be listed. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**max\_size** - maximum size (in bytes) for file to be listed. Larger files will not be counted. [Memory suffixes](/manual/appendix/suffixes#memory_suffixes) can be used.<br>**min\_age** - minimum age (in seconds) of directory entry to be listed. More recent entries will not be listed. [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**max\_age** - maximum age (in seconds) of directory entry to be listed. Entries so old and older will not be listed (modification time). [Time suffixes](/manual/appendix/suffixes#time_suffixes) can be used.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Environment variables, e.g. %APP\_HOME%, $HOME and %TEMP% are not supported.<br><br>Pseudo-directories "." and ".." are never listed.<br><br>Symbolic links are never followed for directory traversal.<br><br>On Windows, directory symlinks are skipped and hard links are listed only once.<br><br>Both `regex_incl` and `regex_excl` are being applied to files and directories when calculating entry size, but are ignored when picking subdirectories to traverse (if regex\_incl is “(?i)\^.+\\.zip$” and max\_depth is not set, then all subdirectories will be traversed, but only files of type zip will be listed).<br><br>Execution time is limited by the default timeout value in agent [configuration](/manual/appendix/config/zabbix_agentd) (3 sec). Since large directory traversal may take longer than that, no data will be returned and the item will turn unsupported. Partial list will not be returned.<br><br>When filtering by size, only regular files have meaningful sizes. Under Linux and BSD, directories also have non-zero sizes (a few Kb typically). Devices have zero sizes, e.g. the size of **/dev/sda1** does not reflect the respective partition size. Therefore, when using `<min_size>` and `<max_size>`, it is advisable to specify `<types_incl>` as "*file*", to avoid surprises.<br><br>Examples:<br>⇒ vfs.dir.get\[/dev\] - retrieves device list in /dev (Linux)<br>⇒ vfs.dir.get\["C:\\Users\\ADMINI\~1\\AppData\\Local\\Temp"\] - retrieves file list in temporary directory (Windows)<br><br>Supported since Zabbix 6.0.0.| |vfs.dir.size\[dir,<regex\_incl>,<regex\_excl>,<mode>,<max\_depth>,<regex\_excl\_dir>\]|<|<|<|<| |<|Directory size (in bytes).|Integer|**dir** - absolute path to directory<br>**regex\_incl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to include; include all if empty (default value)<br>**regex\_excl** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the entity (file, directory, symbolic link) to exclude; don't exclude any if empty (default value)<br>**mode** - possible values:<br>*apparent* (default) - gets apparent file sizes rather than disk usage (acts as `du -sb dir`), *disk* - gets disk usage (acts as `du -s -B1 dir`). Unlike du command, vfs.dir.size item takes hidden files in account when calculating directory size (acts as `du -sb .[^.]* *` within dir).<br>**max\_depth** - maximum depth of subdirectories to traverse. **-1** (default) - unlimited, **0** - no descending into subdirectories.<br>**regex\_excl\_dir** - regular [expression](/manual/regular_expressions#overview) describing the name pattern of the directory to exclude. All content of the directory will be excluded (in contrast to regex\_excl)|Only directories with at least read permission for *zabbix* user are calculated.<br><br>On Windows any symlink is skipped and hard links are taken into account only once.<br><br>With large directories or slow drives this item may time out due to the Timeout setting in [agent](/manual/appendix/config/zabbix_agentd) and [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) configuration files. Increase the timeout values as necessary.<br><br>Examples:<br>⇒ vfs.dir.size\[/tmp,log\] - calculates size of all files in /tmp which contain 'log'<br>⇒ vfs.dir.size\[/tmp,log,\^.+\\.old$\] - calculates size of all files in /tmp which contain 'log', excluding files containing '.old'<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Supported since Zabbix 3.4.0.| |vfs.file.cksum\[file,<mode>\]|<|<|<|<| |<|File checksum, calculated by the UNIX cksum algorithm.|Integer - with `mode` as *crc32*<br><br>String - with `mode` as *md5*, *sha256*|**file** - full path to file<br>**mode** - *crc32* (default), *md5*, *sha256*|Example:<br>=> vfs.file.cksum\[/etc/passwd\]<br><br>Example of returned values (crc32/md5/sha256 respectively):<br>675436101<br>9845acf68b73991eb7fd7ee0ded23c44<br>ae67546e4aac995e5c921042d0cf0f1f7147703aa42bfbfb65404b30f238f2dc<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.contents\[file,<encoding>\]|<|<|<|<| |<|Retrieving contents of a file.|Text|**file** - full path to file<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)|Returns an empty string if the file is empty or contains LF/CR characters only.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Example:<br>=> vfs.file.contents\[/etc/passwd\]<br><br>This item is limited to files no larger than 64 Kbytes.<br><br>Supported since Zabbix 2.0.| |vfs.file.exists\[file,<types\_incl>,<types\_excl>\]|<|<|<|<| |<|Checks if file exists.|0 - not found<br><br>1 - file of the specified type exists|**file** - full path to file<br>**types\_incl** - list of file types to include, possible values: *file* (regular file, default (if types\_excl is not set)), *dir* (directory), *sym* (symbolic link), *sock* (socket), *bdev* (block device), *cdev* (character device), *fifo* (FIFO), *dev* (synonymous with "bdev,cdev"), *all* (all mentioned types, default if types\_excl is set).<br>**types\_excl** - list of file types to exclude, see types\_incl for possible values (by default no types are excluded)|Multiple types must be separated with a comma and the entire set enclosed in quotes "".<br>On Windows the double quotes have to be backslash '\\' escaped and the whole item key enclosed in double quotes when using the command line utility for calling zabbix\_get.exe or agent2.<br><br>If the same type is in both <types\_incl> and <types\_excl>, files of this type are excluded.<br><br>Examples:<br>=> vfs.file.exists\[/tmp/application.pid\]<br>=> vfs.file.exists\[/tmp/application.pid,"file,dir,sym"\]<br>=> vfs.file.exists\[/tmp/application\_dir,dir\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>Note that the item may turn unsupported on Windows if a directory is searched within a non-existing directory, e.g. vfs.file.exists\[C:\\no\\dir,dir\] (where 'no' does not exist).| |vfs.file.get\[file\]|<|<|<|<| |<|Return information about a file.|JSON object|**file** - full path to file|Supported file types on UNIX-like systems: regular file, directory, symbolic link, socket, block device, character device, FIFO<br><br>Supported file types on Windows: regular file, directory, symbolic link<br><br>Example:<br>=> vfs.file.get\[/etc/passwd\] → return a JSON with information about the /etc/passwd file (type, user, permissions, SID, uid etc)<br><br>Supported since Zabbix 6.0.| |vfs.file.md5sum\[file\]|<|<|<|<| |<|MD5 checksum of file.|Character string (MD5 hash of the file)|**file** - full path to file|Example:<br>=> vfs.file.md5sum\[/usr/local/etc/zabbix\_agentd.conf\]<br><br>Example of returned value:<br>b5052decb577e0fffd622d6ddc017e82<br><br>The file size limit (64 MB) for this item was removed in version 1.8.6.<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.file.owner\[file,<ownertype>,<resulttype>\]|<|<|<|<| |<|Retrieve owner of a file.|Character string|**file** - full path to file<br>**ownertype** - *user* (default) or *group* (Unix only)<br>**resulttype** - *name* (default) or *id*; for id - return uid/gid on Unix, SID on Windows|Example:<br>=> vfs.file.owner\[/tmp/zabbix\_server.log\] → return file owner of /tmp/zabbix\_server.log<br>=> vfs.file.owner\[/tmp/zabbix\_server.log,,id\] → return file owner ID of /tmp/zabbix\_server.log<br><br>Supported since Zabbix 6.0.| |vfs.file.permissions\[file\]|<|<|<|<| |<|Return a 4-digit string containing the octal number with Unix permissions.|String|**file** - full path to the file|Not supported on Windows.<br><br>Example:<br>=> vfs.file.permissions\[/etc/passwd\] → return permissions of /etc/passwd, for example, '0644'<br><br>Supported since Zabbix 6.0.| |vfs.file.regexp\[file,regexp,<encoding>,<start line>,<end line>,<output>\]|<|<|<|<| |<|Find string in a file.|The line containing the matched string, or as specified by the optional `output` parameter|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|Only the first matching line is returned.<br>An empty string is returned if no line matched the expression.<br><br>Byte order mark (BOM) is excluded from the output.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `start line`, `end line` and `output` parameters are supported from version 2.2.<br><br>Examples:<br>=> vfs.file.regexp\[/etc/passwd,zabbix\]<br>=> vfs.file.regexp\[/path/to/some/file,"(\[0-9\]+)$",,3,5,\\1\]<br>=> vfs.file.regexp\[/etc/passwd,"\^zabbix:.:(\[0-9\]+)",,,,\\1\] → getting the ID of user *zabbix*| |vfs.file.regmatch\[file,regexp,<encoding>,<start line>,<end line>\]|<|<|<|<| |<|Find string in a file.|0 - match not found<br><br>1 - found|**file** - full path to file<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**encoding** - code page [identifier](/manual/config/items/itemtypes/zabbix_agent#encoding_settings)<br>**start line** - the number of first line to search (first line of file by default).<br>**end line** - the number of last line to search (last line of file by default).|Byte order mark (BOM) is ignored.<br><br>The `start line` and `end line` parameters are supported from version 2.2.<br><br>Example:<br>=> vfs.file.regmatch\[/var/log/app.log,error\]| |vfs.file.size\[file,<mode>\]|<|<|<|<| |<|File size (in bytes).|Integer|**file** - full path to file<br>**mode** - possible values:<br>*bytes* (default) or *lines* (empty lines are counted, too)|The file must have read permissions for user *zabbix*.<br><br>Example:<br>=> vfs.file.size\[/var/log/syslog\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).<br><br>The `mode` parameter is supported since Zabbix 6.0.| |vfs.file.time\[file,<mode>\]|<|<|<|<| |<|File time information.|Integer (Unix timestamp)|**file** - full path to the file<br>**mode** - possible values:<br>*modify* (default) - last time of modifying file content,<br>*access* - last time of reading file,<br>*change* - last time of changing file properties|Example:<br>=> vfs.file.time\[/etc/passwd,modify\]<br><br>The file size limit depends on [large file support](/manual/appendix/items/large_file_support).| |vfs.fs.discovery|<|<|<|<| |<|List of mounted filesystems and their types. Used for low-level discovery.|JSON object| |Supported since Zabbix 2.0.<br><br>The {\#FSDRIVETYPE} macro is supported on Windows since Zabbix 3.0.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.get|<|<|<|<| |<|List of mounted filesystems, their types, disk space and inode statistics. Can be used for low-level discovery.|JSON object| |Supported since Zabbix 4.4.5.<br><br>The {\#FSLABEL} macro is supported on Windows since Zabbix 6.0.| |vfs.fs.inode\[fs,<mode>\]|<|<|<|<| |<|Number or percentage of inodes.|Integer - for number<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, //pfree // (free, percentage), *pused* (used, percentage)|Example:<br>=> vfs.fs.inode\[/,pfree\]| |vfs.fs.size\[fs,<mode>\]|<|<|<|<| |<|Disk space in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**fs** - filesystem<br>**mode** - possible values:<br>*total* (default), *free*, *used*, *pfree* (free, percentage), *pused* (used, percentage)|In case of a mounted volume, disk space for local file system is returned.<br><br>Example:<br>=> vfs.fs.size\[/tmp,free\]<br><br>Reserved space of a file system is taken into account and not included when using the *free* mode.| |vm.memory.size\[<mode>\]|<|<|<|<| |<|Memory size in bytes or in percentage from total.|Integer - for bytes<br><br>Float - for percentage|**mode** - possible values:<br>*total* (default), *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*, *used*, *pused* (used, percentage), *available*, *pavailable* (available, percentage)<br>See also [platform-specific](/manual/appendix/items/supported_by_platform) support and [additional details](/manual/appendix/items/vm.memory.size_params) for this parameter.|This item accepts three categories of parameters:<br><br>1) *total* - total amount of memory;<br>2) platform-specific memory types: *active*, *anon*, *buffers*, *cached*, *exec*, *file*, *free*, *inactive*, *pinned*, *shared*, *slab*, *wired*;<br>3) user-level estimates on how much memory is used and available: *used*, *pused*, *available*, *pavailable*.| |web.page.get\[host,<path>,<port>\]|<|<|<|<| |<|Get content of web page.|Web page source as text (including headers)|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.get\[www.example.com,index.php,80\]<br>=> web.page.get\[https://www.example.com\]<br>=> web.page.get\[https://blog.example.com/?s=zabbix\]<br>=> web.page.get\[localhost:80\]<br>=> web.page.get\["\[::1\]/server-status"\]| |web.page.perf\[host,<path>,<port>\]|<|<|<|<| |<|Loading time of full web page (in seconds).|Float|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Example:<br>=> web.page.perf\[www.example.com,index.php,80\]<br>=> web.page.perf\[https://www.example.com\]| |web.page.regexp\[host,<path>,<port>,regexp,<length>,<output>\]|<|<|<|<| |<|Find string on a web page.|The matched string, or as specified by the optional `output` parameter|**host** - hostname or URL (as `scheme://host:port/path`, where only *host* is mandatory).<br>Allowed URL schemes: *http*, *https*^**[4](#footnotes)**^. Missing scheme will be treated as *http*. If URL is specified `path` and `port` must be empty. Specifying user name/password when connecting to servers that require authentication, for example: `http://user:password@www.example.com` is only possible with cURL support ^**[4](#footnotes)**^.<br>Punycode is supported in hostnames.<br>**path** - path to HTML document (default is /)<br>**port** - port number (default is 80 for HTTP)<br>**regexp** - regular [expression](/manual/regular_expressions#overview) describing the required pattern<br>**length** - maximum number of characters to return<br>**output** - an optional output formatting template. The **\\0** escape sequence is replaced with the matched part of text (from the first character where match begins until the character where match ends) while an **\\N** (where N=1...9) escape sequence is replaced with Nth matched group (or an empty string if the N exceeds the number of captured groups).|This item turns unsupported if the resource specified in `host` does not exist or is unavailable.<br><br>`host` can be hostname, domain name, IPv4 or IPv6 address. But for IPv6 address Zabbix agent must be compiled with IPv6 support enabled.<br><br>Content extraction using the `output` parameter takes place on the agent.<br><br>The `output` parameter is supported from version 2.2.<br><br>Example:<br>=> web.page.regexp\[www.example.com,index.php,80,OK,2\]<br>=> web.page.regexp\[https://www.example.com,,,OK,2\]| |zabbix.stats\[<ip>,<port>\]|<|<|<|<| |<|Return a set of Zabbix server or proxy internal metrics remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.<br><br>A selected set of internal metrics is returned by this item. For details, see [Remote monitoring of Zabbix stats](/manual/appendix/items/remote_stats#exposed_metrics).| |zabbix.stats\[<ip>,<port>,queue,<from>,<to>\]|<|<|<|<| |<|Return number of monitored items in the queue which are delayed on Zabbix server or proxy remotely.|JSON object|**ip** - IP/DNS/network mask list of servers/proxies to be remotely queried (default is 127.0.0.1)<br>**port** - port of server/proxy to be remotely queried (default is 10051)<br>**queue** - constant (to be used as is)<br>**from** - delayed by at least (default is 6 seconds)<br>**to** - delayed by at most (default is infinity)|Note that the stats request will only be accepted from the addresses listed in the 'StatsAllowedIP' [server](/manual/appendix/config/zabbix_server)/[proxy](/manual/appendix/config/zabbix_proxy) parameter on the target instance.|  
ja	##### Footnotes  ^**1**^A Linux-specific note. Zabbix agent must have read-only access to filesystem */proc*. Kernel patches from www.grsecurity.org limit access rights of non-privileged users.  ^**2**^ `vfs.dev.read[]`, `vfs.dev.write[]`: Zabbix agent will terminate "stale" device connections if the item values are not accessed for more than 3 hours. This may happen if a system has devices with dynamically changing paths or if a device gets manually removed. Note also that these items, if using an update interval of 3 hours or more, will always return '0'.  ^**3**^ `vfs.dev.read[]`, `vfs.dev.write[]`: If default *all* is used for the first parameter then the key will return summary statistics, including all block devices like sda, sbd and their partitions (sda1, sda2, sdb3...) and multiple devices (MD raid) based on those block devices/partitions and logical volumes (LVM) based on those block devices/partitions. In such cases returned values should be considered only as relative value (dynamic in time) but not as absolute values.  ^**4**^ SSL (HTTPS) is supported only if agent is compiled with cURL support. Otherwise the item will turn unsupported.  

en-us	##### Key file authentication  To use key based authentication for SSH items, certain changes to the server configuration are required.  Open the Zabbix server configuration file ([zabbix\_server.conf](/manual/appendix/config/zabbix_server)) as `root` and look for the following line:      # SSHKeyLocation=  Uncomment it and set full path to a folder where public and private keys will be located:      SSHKeyLocation=/home/zabbix/.ssh  Save the file and restart zabbix\_server afterwards.  */home/zabbix* here is the home directory for the *zabbix* user account and *.ssh* is a directory where by default public and private keys will be generated by a [ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen) command inside the home directory.  Usually installation packages of zabbix-server from different OS distributions create *zabbix* user account with a home directory in not very well-known places (as for system accounts), e. g. */var/lib/zabbix*.  Before starting to generate the keys, an approach to reallocate the home directory to a better known place (intuitively expected) could be considered. This will correspond with the *SSHKeyLocation* Zabbix server configuration parameter mentioned above.  These steps can be skipped if *zabbix* account has been added manually according to the [installation section](/manual/installation/install#create_user_account) because in this case most likely the home directory is already located at */home/zabbix*.  To change the setting for the *zabbix* user account all working processes which are using it have to be stopped:      # service zabbix-agent stop     # service zabbix-server stop  To change the home directory location with an attempt to move it (if it exists) a command should be executed:      # usermod -m -d /home/zabbix zabbix  It's absolutely possible that a home directory did not exist in the old place, so it should be created at the new place. A safe attempt to do that is:      # test -d /home/zabbix || mkdir /home/zabbix  To be sure that all is secure, additional commands could be executed to set permissions to the home directory:      # chown zabbix:zabbix /home/zabbix     # chmod 700 /home/zabbix  Previously stopped processes now can be started again:      # service zabbix-agent start     # service zabbix-server start  Now steps to generate public and private keys can be performed by a command:      # sudo -u zabbix ssh-keygen -t rsa     Generating public/private rsa key pair.     Enter file in which to save the key (/home/zabbix/.ssh/id_rsa):      Created directory '/home/zabbix/.ssh'.     Enter passphrase (empty for no passphrase):      Enter same passphrase again:      Your identification has been saved in /home/zabbix/.ssh/id_rsa.     Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub.     The key fingerprint is:     90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0     The key's randomart image is:     +--[ RSA 2048]----+     |                 |     |       .         |     |      o          |     | .     o         |     |+     . S        |     |.+   o =         |     |E .   * =        |     |=o . ..* .       |     |... oo.o+        |     +-----------------+  Note: public and private keys (*id\_rsa.pub* and *id\_rsa* respectively) have been generated by default in the */home/zabbix/.ssh* directory which corresponds to the Zabbix server *SSHKeyLocation* configuration parameter.  ::: noteimportant Key types other than "rsa" may be supported by the ssh-keygen tool and SSH servers but they may not be supported by libssh2, used by Zabbix. :::
ja	##### キーファイル認証  SSHアイテムに鍵ベースの認証を使用するためには、サーバーに特定の設定を行うことが必要です。  Zabbixサーバーの設定ファイル([zabbix_server.conf](/manual/appendix/config/zabbix_server))をroot権限で開き、以下の行を確認します。      # SSHKeyLocation=  コメントを外して、公開鍵と秘密鍵が格納されるフォルダのフルパスを設定します。      SSHKeyLocation=/home/zabbix/.ssh  ファイルを保存し、その後 zabbix\_serverを再起動します。  */home/zabbix* ここに *zabbix* ユーザアカウントのホームディレクトリがあります。*/.ssh は、ホームディレクトリ内で[ssh-keygen](http://en.wikipedia.org/wiki/Ssh-keygen) コマンドを使用して公開鍵と秘密鍵を生成するディレクトリです。  通常、様々なOSディストリビューションからのzabbix-serverインストールパッケージでは、あまり知られていない場所（システムアカウントのように）にホームディレクトリを持つ*zabbix*ユーザーアカウントを作成します。例えば */var/lib/zabbix*) 。  鍵の生成を開始する前に、ホームディレクトリをより良く知られた場所(直感的に予想できる場所)に再配置するアプローチを検討することができます。これは、前述の *SSHKeyLocation* というZabbix server の設定パラメータに対応します。  [ソースコードからのインストール](/manual/installation/install#create_user_account)に従って手動で *zabbix* アカウントを追加した場合、ホームディレクトリが既に */home/zabbix* にある可能性が高いため、これらの手順は省略することができます。  *zabbix* ユーザーアカウントの設定を変更するには、そのアカウントを使用しているすべての作業プロセスを停止する必要があります。      # service zabbix-agent stop     # service zabbix-server stop  ホームディレクトリの場所を変更するには（存在する場合）、コマンドを実行する必要があります。      # usermod -m -d /home/zabbix zabbix  古い場所にホームディレクトリが存在しない可能性が十分にあるので、新しい場所に作成する必要があります。そのためには以下のように実行します：      # test -d /home/zabbix || mkdir /home/zabbix  すべてが安全であることを確認するために、追加のコマンドを実行して、ホームディレクトリのパーミッションを設定することができます。      # chown zabbix:zabbix /home/zabbix     # chmod 700 /home/zabbix  停止していたプロセスを再び起動できるようになります：      # service zabbix-agent start     # service zabbix-server start  これで、公開鍵と秘密鍵を生成する手順を、コマンドで実行できるようになりました:      # sudo -u zabbix ssh-keygen -t rsa     Generating public/private rsa key pair.     Enter file in which to save the key (/home/zabbix/.ssh/id_rsa):      Created directory '/home/zabbix/.ssh'.     Enter passphrase (empty for no passphrase):      Enter same passphrase again:      Your identification has been saved in /home/zabbix/.ssh/id_rsa.     Your public key has been saved in /home/zabbix/.ssh/id_rsa.pub.     The key fingerprint is:     90:af:e4:c7:e3:f0:2e:5a:8d:ab:48:a2:0c:92:30:b9 zabbix@it0     The key's randomart image is:     +--[ RSA 2048]----+     |                 |     |       .         |     |      o          |     | .     o         |     |+     . S        |     |.+   o =         |     |E .   * =        |     |=o . ..* .       |     |... oo.o+        |     +-----------------+  注: 公開鍵と秘密鍵(それぞれ *id\_rsa.pub* と *id\_rsa*) は、デフォルトで Zabbixサーバーの *SSHKeyLocation* 設定パラメータに対応する */home/zabbix/.ssh* ディレクトリに生成されています。  ::: noteimportant "rsa" 以外の鍵の種類は、ssh-keygenツールやSSHサーバーではサポートされていますが、Zabbixで使用されているlibssh2ではサポートされていない場合があります。 :::

en-us	#### Key name  The key name itself has a limited range of allowed characters, which just follow each other. Allowed characters are:      0-9a-zA-Z_-.  Which means:  -   all numbers; -   all lowercase letters; -   all uppercase letters; -   underscore; -   dash; -   dot.  ![](../../../../../assets/en/manual/config/key_name.png)
ja	#### キー名  キー名自体には、使用できる文字の範囲が限られており、その文字が相互に続くだけです。 許容される文字は :       0-9a-zA-Z_-. です。  つまり、以下の文字種を指します。  - すべての数字 - すべての小文字 - すべての大文字 - アンダースコア - ダッシュ - ドット  ![](../../../../../assets/en/manual/config/key_name.png)

en-us	#### Key parameters  An item key can have multiple parameters that are comma separated.  ![](../../../../../assets/en/manual/config/key_parameters.png)  Each key parameter can be either a quoted string, an unquoted string or an array.  ![](../../../../../assets/en/manual/config/item_parameter.png)  The parameter can also be left empty, thus using the default value. In that case, the appropriate number of commas must be added if any further parameters are specified. For example, item key **icmpping\[,,200,,500\]** would specify that the interval between individual pings is 200 milliseconds, timeout - 500 milliseconds, and all other parameters are left at their defaults.  It is possible to include macros in the parameters. Those can be [user macros](/manual/appendix/macros/supported_by_location_user#items-item-prototypes) or some of the built-in macros. To see what particular built-in macros are supported in item key parameters, search the page [Supported macros](/manual/appendix/macros/supported_by_location) for "item key parameters".
ja	#### キーパラメーター  アイテムキーは、カンマ区切りで複数のパラメータを持つことができます。  ![](../../../../../assets/en/manual/config/key_parameters.png)  各キーパラメータは、引用符で囲まれた文字列、引用符で囲まれていない文字列、または配列のいずれかになります。  ![](../../../../../assets/en/manual/config/item_parameter.png)  また、パラメータを空にして、デフォルト値を使用することも可能です。 その場合、さらにパラメータを指定する場合は、適切な数のカンマを追加する必要があります。 例えば、アイテムキー**icmpping\[,,200,,500]** は、個々の ping の間隔が 200 ミリ秒、ping のタイムアウトが 500 ミリ秒、その他のパラメータはデフォルトのままです。   パラメータにマクロを含めることができます。マクロは[ユーザー マクロ](/manual/appendix/macros/supported_by_location_user#items-item-prototypes)または組み込みマクロの一部です。アイテム キー パラメータでサポートされている特定の組み込みマクロを確認するには、[サポートされているマクロ](/manual/appendix/macros/supported_by_location)ページで「アイテム キー パラメータ」を検索してください。

en-us	#### Kiosk mode  The kiosk mode in supported frontend pages can be activated using URL parameters. For example, in dashboards:  -   `/zabbix.php?action=dashboard.view&kiosk=1` - activate kiosk mode -   `/zabbix.php?action=dashboard.view&kiosk=0` - activate normal mode
ja	#### キオスクモード  フロントエンドページのキオスクモードは、そのページでサポートされていればURLパラメータを使用してアクティブ化できます。たとえば、ダッシュボードでは次のようになります。  -   `/zabbix.php?action=dashboard.view&kiosk=1` - キオスクモードをアクティブに -   `/zabbix.php?action=dashboard.view&kiosk=0` - ノーマルモードをアクティブに

en-us	#### Known issues  See [known issues](/manual/installation/known_issues#graphs) for graphs.
ja	#### 既知の問題  グラフについては、[known issues](/manual/installation/known_issues#graphs)を参照してください。

en-us	#### Kubernetes   - *Kubernetes nodes by HTTP*  - *Kubernetes cluster state by HTTP* - *Kubernetes API server by HTTP* - *Kubernetes Controller manager by HTTP* - *Kubernetes Scheduler by HTTP* - *Kubernetes kubelet by HTTP*  To enable Kubernetes monitoring, you need to use the new tool [Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0), which installs Zabbix proxy and Zabbix agents in the Kubernetes cluster.  To learn more about configuring templates, see [HTTP template operation](/manual/config/templates_out_of_the_box/http).
ja	#### Kubernetes  - *Kubernetes nodes by HTTP* - *Kubernetes cluster state by HTTP* - *Kubernetes API server by HTTP* - *Kubernetes Controller manager by HTTP* - *Kubernetes Scheduler by HTTP* - *Kubernetes kubelet by HTTP*  Kubernetesの監視を有効にするには、新しいツール[Zabbix Helm Chart](https://git.zabbix.com/projects/ZT/repos/kubernetes-helm/browse?at=refs%2Fheads%2Frelease%2F6.0)を使用し、KubernetesクラスタにZabbixプロキシとZabbixエージェントをインストールする必要があります。  テンプレートの設定の詳細については、[HTTPテンプレートの操作](/manual/config/templates_out_of_the_box/http)を参照してください。

en-us	##### Large file support  Zabbix has large file support for SNMP trapper files. The maximum file size that Zabbix can read is 2\^63 (8 EiB). Note that the filesystem may impose a lower limit on the file size.
ja	##### ラージファイルサポート  Zabbixは、SNMPトラッパーのラージファイルをサポートしています。Zabbix が読み取れる最大ファイル サイズは 2\^63 (8 EiB) です。 ファイルシステムによってはファイルサイズに下限があることに注意してください。

en-us	 ### Latest data link for hosts shows numbers  The latest data link for hosts in [*Monitoring* -> *Hosts*](/manual/web_interface/frontend_sections/monitoring/hosts) now shows the number of items with latest data.
ja	### ホストの最新データリンクに数値が表示される  [*監視データ* -> *ホスト*](/manual/web_interface/frontend_sections/monitoring/hosts) にあるホストの最新データリンクは、最新データのアイテム数を表示するようになりました。