<?xml version='1.0' encoding='UTF-8'?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
<file source-language="en" target-language="nb-NO" datatype="plaintext" original="manual/definitions.md">
<trans-unit id="bd3d4e41" xml:space="preserve">
<source># 2 Definitions</source>
<trans-unit id="99b1c1f4" xml:space="preserve">
In this section you can learn the meaning of some terms commonly used in
<trans-unit id="77400725" xml:space="preserve">
***[host](/manual/config/hosts)***
\- *any physical or virtual device, application, service, or any other logically-related collection of monitored parameters.*
***[host group](/manual/config/hosts)***
\- *a logical grouping of hosts.
Host groups are used when assigning access rights to hosts
for different user groups.*
***[item](/manual/config/items)***
\- *a particular piece of data that you want to receive from a host, a
preprocessing](/manual/config/items/item#item_value_preprocessing)***
\- *a transformation of received metric value* before saving it to the
***[trigger](/manual/config/triggers)***
\- *a logical expression that defines a problem threshold and is used to
"evaluate" data received in items.*
When received data are above the threshold, triggers go from 'Ok' into a
'Problem' state. When received data are below the threshold, triggers
stay in/return to an 'Ok' state.
***[template](/manual/config/templates)***
\- *a set of entities (items, triggers, graphs, low-level discovery
rules, web scenarios) ready to be applied to one or several hosts.*
The job of templates is to speed up the deployment of monitoring tasks
on a host; also to make it easier to apply mass changes to monitoring
tasks. Templates are linked directly to individual hosts.
***[template group](/manual/config/templates)***
\- *a logical grouping of templates.
Template groups are used when assigning access rights to templates
for different user groups.*
***[event](/manual/config/events)***