Zabbix Documentation 3.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:config:hosts:host

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:config:hosts:host [2016/09/13 10:52]
martins-v describing how access permissions are set when creating nested host group children/parents
manual:config:hosts:host [2017/05/26 09:26] (current)
dotneft
Line 44: Line 44:
  
 Listed template names are clickable links leading to the template configuration form. Listed template names are clickable links leading to the template configuration form.
- 
-See also [[manual/​installation/​known_issues#​problems_with_pressing_enter_in_configuration_forms|known issues]] about template linkage. 
  
 The **IPMI** tab contains IPMI management attributes. The **IPMI** tab contains IPMI management attributes.
Line 68: Line 66:
 |//​Connections to host// ​  |How Zabbix server or proxy connects to Zabbix agent on a host: no encryption (default), using PSK (pre-shared key) or certificate.| |//​Connections to host// ​  |How Zabbix server or proxy connects to Zabbix agent on a host: no encryption (default), using PSK (pre-shared key) or certificate.|
 |//​Connections from host// |Select what type of connections are allowed from the host (i.e. from Zabbix agent and Zabbix sender). Several connection types can be selected at the same time (useful for testing and switching to other connection type). Default is "No encryption"​.| |//​Connections from host// |Select what type of connections are allowed from the host (i.e. from Zabbix agent and Zabbix sender). Several connection types can be selected at the same time (useful for testing and switching to other connection type). Default is "No encryption"​.|
-|//​Issuer// ​               |Allowed issuer of certificate. Certificate is first validated with CA (certificate authority). If it is valid, signed by the CA, then the //Issuer// field can be used to further restrict allowed CA. This field is optional, ​intended to use if your Zabbix installation uses certificates from multiple CAs.|+|//​Issuer// ​               |Allowed issuer of certificate. Certificate is first validated with CA (certificate authority). If it is valid, signed by the CA, then the //Issuer// field can be used to further restrict allowed CA. This field is intended to be used if your Zabbix installation uses certificates from multiple CAs. If this field is empty then any CA is accepted.|
 |//​Subject// ​              ​|Allowed subject of certificate. Certificate is first validated with CA. If it is valid, signed by the CA, then the //Subject// field can be used to allow only one value of //Subject// string. If this field is empty then any valid certificate signed by the configured CA is accepted.| |//​Subject// ​              ​|Allowed subject of certificate. Certificate is first validated with CA. If it is valid, signed by the CA, then the //Subject// field can be used to allow only one value of //Subject// string. If this field is empty then any valid certificate signed by the configured CA is accepted.|
 |//PSK identity// ​         |Pre-shared key identity string.| |//PSK identity// ​         |Pre-shared key identity string.|
Line 84: Line 82:
  
 ^Parameter ​    ​^Description^ ^Parameter ​    ​^Description^
-|//Group name//​|Enter a unique host group name.\\ To create a nested host group, use the '/'​ forward slash separator, for example ''​Europe/​Latvia/​Riga/​Zabbix servers''​. You can create this group even if none of the three parent host groups (''​Europe/​Latvia/​Riga''​) exist.\\ Leading and trailing slashes, several slashes in a row and any asterisks ​are not allowed. Escaping of '/'​ is not supported.\\ Nested representation of host groups is supported since Zabbix 3.2.0. ​ |+|//Group name//​|Enter a unique host group name.\\ To create a nested host group, use the '/'​ forward slash separator, for example ''​Europe/​Latvia/​Riga/​Zabbix servers''​. You can create this group even if none of the three parent host groups (''​Europe/​Latvia/​Riga''​) exist. In this case creating these parent host groups is up to the user; they will not be created automatically.\\ Leading and trailing slashes, several slashes in a row are not allowed. Escaping of '/'​ is not supported.\\ Nested representation of host groups is supported since Zabbix 3.2.0. ​ |
 |//​Hosts// ​    ​|Select hosts, members of the group. A host group may have zero, one or more hosts. ​ | |//​Hosts// ​    ​|Select hosts, members of the group. A host group may have zero, one or more hosts. ​ |
 +|//Apply permissions to all subgroups// ​ |Mark this checkbox and click on //Update// to apply the same level of permissions to all nested host groups. For user groups that may have had differing [[:​manual/​config/​users_and_usergroups/​usergroup#​configuration|permissions]] assigned to nested host groups, the permission level of the parent host group will be enforced on the nested groups.\\ This is a one-time option that is not saved in the database. It is available to Zabbix Super Admin users only and only when editing an existing host group.\\ This option is supported since Zabbix 3.4.0. ​ |
  
 **Permissions to nested host groups** **Permissions to nested host groups**
Line 91: Line 90:
   * When creating a child host group to an existing parent host group, [[:​manual/​config/​users_and_usergroups/​usergroup|user group]] permissions to the child are inherited from the parent (for example, when creating ''​Riga/​Zabbix servers''​ if ''​Riga''​ already exists)   * When creating a child host group to an existing parent host group, [[:​manual/​config/​users_and_usergroups/​usergroup|user group]] permissions to the child are inherited from the parent (for example, when creating ''​Riga/​Zabbix servers''​ if ''​Riga''​ already exists)
   * When creating a parent host group to an existing child host group, no permissions to the parent are set (for example, when creating ''​Riga''​ if ''​Riga/​Zabbix servers''​ already exists)   * When creating a parent host group to an existing child host group, no permissions to the parent are set (for example, when creating ''​Riga''​ if ''​Riga/​Zabbix servers''​ already exists)
-