en-us	##### Testing cipher strings and allowing only PFS ciphersuites  To see which ciphersuites have been selected you need to set 'DebugLevel=4' in the configuration file, or use the `-vv` option for zabbix\_sender.  Some experimenting with `TLSCipher*` parameters might be necessary before you get the desired ciphersuites. It is inconvenient to restart Zabbix server, proxy or agent multiple times just to tweak `TLSCipher*` parameters. More convenient options are using zabbix\_sender or the `openssl` command. Let's show both.  **1.** Using zabbix\_sender.  Let's make a test configuration file, for example /home/zabbix/test.conf, with the syntax of a zabbix\_agentd.conf file:        Hostname=nonexisting       ServerActive=nonexisting              TLSConnect=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSPSKIdentity=nonexisting       TLSPSKFile=/home/zabbix/agent.psk  You need valid CA and agent certificates and PSK for this example. Adjust certificate and PSK file paths and names for your environment.  If you are not using certificates, but only PSK, you can make a simpler test file:        Hostname=nonexisting       ServerActive=nonexisting              TLSConnect=psk       TLSPSKIdentity=nonexisting       TLSPSKFile=/home/zabbix/agentd.psk  The selected ciphersuites can be seen by running zabbix\_sender (example compiled with OpenSSL 1.1.d):        $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA  Here you see the ciphersuites selected by default. These default values are chosen to ensure interoperability with Zabbix agents running on systems with older OpenSSL versions (from 1.0.1).  With newer systems you can choose to tighten security by allowing only a few ciphersuites, e.g. only ciphersuites with PFS (Perfect Forward Secrecy). Let's try to allow only ciphersuites with PFS using `TLSCipher*` parameters.  ::: noteimportant The result will not be interoperable with systems using OpenSSL 1.0.1 and 1.0.2, if PSK is used. Certificate-based encryption should work. :::  Add two lines to the `test.conf` configuration file:        TLSCipherCert=EECDH+aRSA+AES128       TLSCipherPSK=kECDHEPSK+AES128  and test again:        $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites                   zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA               zabbix_sender [42892]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA               zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA          The "certificate ciphersuites" and "PSK ciphersuites" lists have changed - they are shorter than before, only containing TLS 1.3 ciphersuites and TLS 1.2 ECDHE-\* ciphersuites as expected.  **2.** TLSCipherAll and TLSCipherAll13 cannot be tested with zabbix\_sender; they do not affect "certificate and PSK ciphersuites" value shown in the example above. To tweak TLSCipherAll and TLSCipherAll13 you need to experiment with the agent, proxy or server.  So, to allow only PFS ciphersuites you may need to add up to three parameters        TLSCipherCert=EECDH+aRSA+AES128       TLSCipherPSK=kECDHEPSK+AES128       TLSCipherAll=EECDH+aRSA+AES128:kECDHEPSK+AES128  to zabbix\_agentd.conf, zabbix\_proxy.conf and zabbix\_server\_conf if each of them has a configured certificate and agent has also PSK.  If your Zabbix environment uses only PSK-based encryption and no certificates, then only one:        TLSCipherPSK=kECDHEPSK+AES128  Now that you understand how it works you can test the ciphersuite selection even outside of Zabbix, with the `openssl` command. Let's test all three `TLSCipher*` parameter values:        $ openssl ciphers EECDH+aRSA+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA       $ openssl ciphers kECDHEPSK+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA       $ openssl ciphers EECDH+aRSA+AES128:kECDHEPSK+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA         You may prefer `openssl ciphers` with option `-V` for a more verbose output:        $ openssl ciphers -V EECDH+aRSA+AES128:kECDHEPSK+AES128                 0x13,0x02 - TLS_AES_256_GCM_SHA384  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(256) Mac=AEAD                 0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any      Au=any  Enc=CHACHA20/POLY1305(256) Mac=AEAD                 0x13,0x01 - TLS_AES_128_GCM_SHA256  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(128) Mac=AEAD                 0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(128) Mac=AEAD                 0xC0,0x27 - ECDHE-RSA-AES128-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AES(128)  Mac=SHA256                 0xC0,0x13 - ECDHE-RSA-AES128-SHA    TLSv1 Kx=ECDH     Au=RSA  Enc=AES(128)  Mac=SHA1                 0xC0,0x37 - ECDHE-PSK-AES128-CBC-SHA256 TLSv1 Kx=ECDHEPSK Au=PSK  Enc=AES(128)  Mac=SHA256                 0xC0,0x35 - ECDHE-PSK-AES128-CBC-SHA TLSv1 Kx=ECDHEPSK Au=PSK  Enc=AES(128)  Mac=SHA1  Similarly, you can test the priority strings for GnuTLS:        $ gnutls-cli -l --priority=NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509       Cipher suites for NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509       TLS_ECDHE_RSA_AES_128_GCM_SHA256                        0xc0, 0x2f      TLS1.2       TLS_ECDHE_RSA_AES_128_CBC_SHA256                        0xc0, 0x27      TLS1.2              Protocols: VERS-TLS1.2       Ciphers: AES-128-GCM, AES-128-CBC       MACs: AEAD, SHA256       Key Exchange Algorithms: ECDHE-RSA       Groups: GROUP-SECP256R1, GROUP-SECP384R1, GROUP-SECP521R1, GROUP-X25519, GROUP-X448, GROUP-FFDHE2048, GROUP-FFDHE3072, GROUP-FFDHE4096, GROUP-FFDHE6144, GROUP-FFDHE8192       PK-signatures: SIGN-RSA-SHA256, SIGN-RSA-PSS-SHA256, SIGN-RSA-PSS-RSAE-SHA256, SIGN-ECDSA-SHA256, SIGN-ECDSA-SECP256R1-SHA256, SIGN-EdDSA-Ed25519, SIGN-RSA-SHA384, SIGN-RSA-PSS-SHA384, SIGN-RSA-PSS-RSAE-SHA384, SIGN-ECDSA-SHA384, SIGN-ECDSA-SECP384R1-SHA384, SIGN-EdDSA-Ed448, SIGN-RSA-SHA512, SIGN-RSA-PSS-SHA512, SIGN-RSA-PSS-RSAE-SHA512, SIGN-ECDSA-SHA512, SIGN-ECDSA-SECP521R1-SHA512, SIGN-RSA-SHA1, SIGN-ECDSA-SHA1
zh-cn	 ##### 测试密码字符串并只允许PFS密码套件  要查看哪些加密套件已经被选中，你需要在配置文件中设置'DebugLevel=4'，或者对zabbix\_sender使用' -vv '选项。  在获得所需的密码组之前，可能需要对“TLSCipher*”参数进行一些实验。 为了调整“TLSCipher*”参数，多次重启Zabbix server、proxy或agent是不方便的。 更方便的选项是使用zabbix\_sender或' openssl '命令。 让我们几种都看看如何实现。  **1.** 使用 zabbix\_sender.  让我们做一个测试配置文件，例如/home/zabbix/test.conf，使用zabbix\_agentd.conf文件的规则:        Hostname=nonexisting       ServerActive=nonexisting              TLSConnect=cert       TLSCAFile=/home/zabbix/ca.crt       TLSCertFile=/home/zabbix/agent.crt       TLSKeyFile=/home/zabbix/agent.key       TLSPSKIdentity=nonexisting       TLSPSKFile=/home/zabbix/agent.psk  在本例中，您需要有效的CA和代理证书以及PSK。 为您的环境调整证书和PSK文件路径和名称。  如果你不使用证书，而只使用PSK，你可以制作一个更简单的测试文件:        Hostname=nonexisting       ServerActive=nonexisting              TLSConnect=psk       TLSPSKIdentity=nonexisting       TLSPSKFile=/home/zabbix/agentd.psk  运行zabbix\_sender(用OpenSSL 1.1.d编译的例子)可以看到所选的密码套件:        $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA       zabbix_sender [41271]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA  这里可以看到默认选择的密码套件。 选择这些默认值是为了确保与运行在较早OpenSSL版本(从1.0.1开始)的系统上的Zabbix代理的互操作性。  在较新的系统中，你可以选择通过只允许一些密码套件来加强安全性，例如。 只有PFS(完全向前保密)密码套件。 让我们尝试只允许使用' TLSCipher* '参数的PFS加密套件。  ::: noteimportant 如果使用PSK，结果将无法与使用OpenSSL 1.0.1和1.0.2的系统进行互操作。 基于证书的加密应该可以工作。 :::  添加两行到' test.conf '配置文件:        TLSCipherCert=EECDH+aRSA+AES128       TLSCipherPSK=kECDHEPSK+AES128  然后再测试一次:        $ zabbix_sender -vv -c /home/zabbix/test.conf -k nonexisting_item -o 1 2>&1 | grep ciphersuites                   zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA               zabbix_sender [42892]: DEBUG: zbx_tls_init_child() PSK ciphersuites: TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA               zabbix_sender [42892]: DEBUG: zbx_tls_init_child() certificate and PSK ciphersuites: TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA AES128-GCM-SHA256 AES128-CCM8 AES128-CCM AES128-SHA256 AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA PSK-AES128-GCM-SHA256 PSK-AES128-CCM8 PSK-AES128-CCM PSK-AES128-CBC-SHA256 PSK-AES128-CBC-SHA          “证书密码套件”和“PSK密码套件”列表已更改 - 它们比以前短，只包含预期的TLS 1.3加密套件和TLS 1.2 ECDHE-\*加密套件。  **2.** TLSCipherAll和TLSCipherAll13不能被zabbix\_sender测试; 它们不会影响上面示例中显示的“证书和PSK密码套件”的值。 要调整TLSCipherAll和TLSCipherAll13，你需要用agent、proxy或server进行实验。  因此，为了只允许PFS密码套件，您可能需要添加最多三个参数        TLSCipherCert=EECDH+aRSA+AES128       TLSCipherPSK=kECDHEPSK+AES128       TLSCipherAll=EECDH+aRSA+AES128:kECDHEPSK+AES128  如果zabbix\_agentd.conf、zabbix\_proxy.conf和zabbix\_server\_conf都配置了证书，并且agent也有PSK。  如果Zabbix环境只使用基于psk的加密并且没有证书，那么只有一个:        TLSCipherPSK=kECDHEPSK+AES128  现在您已经了解了它的工作原理，您可以在Zabbix之外使用“openssl”命令测试密码套件的选择。 让我们测试三个' TLSCipher* '参数值:        $ openssl ciphers EECDH+aRSA+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA       $ openssl ciphers kECDHEPSK+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA       $ openssl ciphers EECDH+aRSA+AES128:kECDHEPSK+AES128 | sed 's/:/ /g'       TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256 ECDHE-RSA-AES128-SHA256 ECDHE-RSA-AES128-SHA ECDHE-PSK-AES128-CBC-SHA256 ECDHE-PSK-AES128-CBC-SHA         你可能更喜欢 `openssl ciphers` 带参数 `-V` 执行 得到更详细的信息 输出:        $ openssl ciphers -V EECDH+aRSA+AES128:kECDHEPSK+AES128                 0x13,0x02 - TLS_AES_256_GCM_SHA384  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(256) Mac=AEAD                 0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any      Au=any  Enc=CHACHA20/POLY1305(256) Mac=AEAD                 0x13,0x01 - TLS_AES_128_GCM_SHA256  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(128) Mac=AEAD                 0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(128) Mac=AEAD                 0xC0,0x27 - ECDHE-RSA-AES128-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AES(128)  Mac=SHA256                 0xC0,0x13 - ECDHE-RSA-AES128-SHA    TLSv1 Kx=ECDH     Au=RSA  Enc=AES(128)  Mac=SHA1                 0xC0,0x37 - ECDHE-PSK-AES128-CBC-SHA256 TLSv1 Kx=ECDHEPSK Au=PSK  Enc=AES(128)  Mac=SHA256                 0xC0,0x35 - ECDHE-PSK-AES128-CBC-SHA TLSv1 Kx=ECDHEPSK Au=PSK  Enc=AES(128)  Mac=SHA1  类似地，你可以测试GnuTLS的优先级字符串:        $ gnutls-cli -l --priority=NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509       Cipher suites for NONE:+VERS-TLS1.2:+ECDHE-RSA:+AES-128-GCM:+AES-128-CBC:+AEAD:+SHA256:+CURVE-ALL:+COMP-NULL:+SIGN-ALL:+CTYPE-X.509       TLS_ECDHE_RSA_AES_128_GCM_SHA256                        0xc0, 0x2f      TLS1.2       TLS_ECDHE_RSA_AES_128_CBC_SHA256                        0xc0, 0x27      TLS1.2              Protocols: VERS-TLS1.2       Ciphers: AES-128-GCM, AES-128-CBC       MACs: AEAD, SHA256       Key Exchange Algorithms: ECDHE-RSA       Groups: GROUP-SECP256R1, GROUP-SECP384R1, GROUP-SECP521R1, GROUP-X25519, GROUP-X448, GROUP-FFDHE2048, GROUP-FFDHE3072, GROUP-FFDHE4096, GROUP-FFDHE6144, GROUP-FFDHE8192       PK-signatures: SIGN-RSA-SHA256, SIGN-RSA-PSS-SHA256, SIGN-RSA-PSS-RSAE-SHA256, SIGN-ECDSA-SHA256, SIGN-ECDSA-SECP256R1-SHA256, SIGN-EdDSA-Ed25519, SIGN-RSA-SHA384, SIGN-RSA-PSS-SHA384, SIGN-RSA-PSS-RSAE-SHA384, SIGN-ECDSA-SHA384, SIGN-ECDSA-SECP384R1-SHA384, SIGN-EdDSA-Ed448, SIGN-RSA-SHA512, SIGN-RSA-PSS-SHA512, SIGN-RSA-PSS-RSAE-SHA512, SIGN-ECDSA-SHA512, SIGN-ECDSA-SECP521R1-SHA512, SIGN-RSA-SHA1, SIGN-ECDSA-SHA1

en-us	#### Testing expressions  It is possible to test the configured trigger expression as to what the expression result would be depending on the received value.  The following expression from an official template is taken as an example:      avg(/Cisco IOS SNMPv2/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_WARN}     or     last(/Cisco IOS SNMPv2/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_WARN_STATUS}  To test the expression, click on *Expression constructor* under the expression field.  ![](../../../../assets/en/manual/config/triggers/trigger_test.png)  In the Expression constructor, all individual expressions are listed. To open the testing window, click on *Test* below the expression list.  ![](../../../../assets/en/manual/config/triggers/expr_test_button.png){width="600"}  In the testing window you can enter sample values ('80', '70', '0', '1' in this example) and then see the expression result, by clicking on the *Test* button.  ![](../../../../assets/en/manual/config/triggers/expr_test.png){width="600"}  The result of the individual expressions as well as the whole expression can be seen.  "TRUE" means that the specified expression is correct. In this particular case A, "80" is greater than the {$TEMP\_WARN} specified value, "70" in this example. As expected, a "TRUE" result appears.  "FALSE" means that the specified expression is incorrect. In this particular case B, {$TEMP\_WARN\_STATUS} "1" needs to be equal with specified value, "0" in this example. As expected, a "FALSE" result appears.  The chosen expression type is "OR". If at least one of the specified conditions (A or B in this case) is TRUE, the overall result will be TRUE as well. Meaning that the current value exceeds the warning value and a problem has occurred.
zh-cn	 #### 测试表达式  可以根据接收的值测试配置的触发器表达式，以确定表达式结果。  以官方模板的表达为例：      avg(/Cisco IOS SNMPv2/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_WARN}     or     last(/Cisco IOS SNMPv2/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_WARN_STATUS}  若要测试表达式，请点击表达式字段下的 *Expression constructor（表达式构造器）*。  ![](../../../../assets/en/manual/config/triggers/trigger_test.png)  在表达式构造器列出了所有单个表达式。打开测试窗口，点击在表达式列表下方*Test(测试)*。  ![](../../../../assets/en/manual/config/triggers/expr_test_button.png){width="600"}  在测试窗口中，您可以输入示例值（在这个示例中为“80, 70, 0，1”），然后点击 *测试* 按钮查看表达式结果。  ![](../../../../assets/en/manual/config/triggers/expr_test.png){width="600"}  可以看到每个表达式的结果以及整个表达式的结果。  “TRUE”结果意味着指定的表达式是正确的。在这个特定的情况A下，“80”大于{$TEMP\_WARN}指定值“70”，出现“TRUE”结果。  “FALSE”结果表示指定的表达式不正确。在这个特定的情况B下，在这个例子中{$TEMP\_WARN\_STATUS}是“1”，需要与指定的“0”值相等，这是错误的。出现“FALSE”结果。  选择的表达式类型是“OR”。如果指定条件中的至少一个（在这种情况下为A或B）是真的，那么最终结果也是TRUE。意味着，当前值超过了警告值，出现了异常。

en-us	#### Testing  Testing preprocessing steps is useful to make sure that complex preprocessing pipelines yield the results that are expected from them, without waiting for the item value to be received and preprocessed.  ![](../../../../assets/en/manual/config/items/test_item_steps.png){width="600"}  It is possible to test:  -   against a hypothetical value -   against a real value from a host  Each preprocessing step can be tested individually as well as all steps can be tested together. When you click on the *Test* or *Test all steps* button respectively in the Actions block, a testing window is opened.
zh-cn	#### Testing  测试预处理步骤有助于确保复杂的预处理管道产生预期的结果，而无需等待接收和预处理监控项值。  ![](../../../../assets/en/manual/config/items/test_item_steps.png){width="600"}  可以测试：  -   与假设值相比 -   与主机的实际值相比较  每个预处理步骤都可以单独测试，也可以一起测试所有步骤。 当您分别单击 动作块中的 *Test* 或 *Test all steps* 按钮时，将打开一个测试窗口。

en-us	### Text history  The text history object has the following properties.  |Property|[Type](/manual/api/reference_commentary#data_types)|Description| |--|--|------| |id|string|ID of the history entry.| |clock|timestamp|Time when that value was received.| |itemid|string|ID of the related item.| |ns|integer|Nanoseconds when the value was received.| |value|text|Received value.|
zh-cn	 ### 文本型历史数据  文本型历史数据对象具有以下属性。  |属性|[类型](/manual/api/reference_commentary#data_types)|描述| |--------|---------------------------------------------------|-----------| |id|string|历史条目的 ID。| |clock|timestamp|收到值的时间。| |itemid|string|相关监控项的 ID。| |ns|integer|收到值时的纳秒数。| |value|text|收到的值。|

en-us	# The following krb5.conf variables are only for MIT Kerberos.     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```
zh-cn	 # 以下 krb5.conf 变量仅适用于 MIT Kerberos     kdc_timesync = 1     ccache_type = 4     forwardable = true     proxiable = true  [realms]     EXAMPLE.COM = {     }  [domain_realm]     .example.com=EXAMPLE.COM     example.com=EXAMPLE.COM  ```

en-us	 The **Tags** tab contains [service-level tags](#service-tags). Service-level tags are  used to identify a service. Tags of this type are not used to map  problems to the service (for that, use *[Problem tags](#problem-tags)* from the first tab).  The **Child services** tab allows to specify dependant services. Click on *Add* to add a service from the list of existing services. If you want to add a new child service, save this service first, then click on a plus icon next to the service that you have just created. 
zh-cn	**Tags** 选项卡包含 [服务级别标签](#服务标签)。服务级别标签用于标识服务。这种类型的标签不用于将问题映射到服务（为此，使用第一个选项卡中的 *[问题标签](#问题标签)*）。  **Child services** 选项卡允许指定依赖服务。单击  *Add* 从现有服务列表中添加服务。如果要添加新的子服务，请先保存此服务，然后单击刚刚创建的服务旁边的加号图标。

en-us	 This page contains navigation links for dashboard widget parameters and possible property values for the respective [dashboard widget field](/manual/api/reference/dashboard/object#dashboard-widget-field) objects.  To see the parameters and property values for each widget, go to individual widget pages for:  -   [Action log](/manual/api/reference/dashboard/widget_fields/action_log) -   [Clock](/manual/api/reference/dashboard/widget_fields/clock) -   [Discovery status](/manual/api/reference/dashboard/widget_fields/discovery_status) -   [Favorite graphs](/manual/api/reference/dashboard/widget_fields/favorite_graphs) -   [Favorite maps](/manual/api/reference/dashboard/widget_fields/favorite_maps) -   [Geomap](/manual/api/reference/dashboard/widget_fields/geomap) -   [Graph](/manual/api/reference/dashboard/widget_fields/graph) -   [Graph (classic)](/manual/api/reference/dashboard/widget_fields/graph_classic) -   [Graph prototype](/manual/api/reference/dashboard/widget_fields/graph_prototype) -   [Host availability](/manual/api/reference/dashboard/widget_fields/host_availability) -   [Item value](/manual/api/reference/dashboard/widget_fields/item_value) -   [Map](/manual/api/reference/dashboard/widget_fields/map) -   [Map navigation tree](/manual/api/reference/dashboard/widget_fields/map_tree) -   [Plain text](/manual/api/reference/dashboard/widget_fields/plain_text) -   [Problem hosts](/manual/api/reference/dashboard/widget_fields/problem_hosts) -   [Problems](/manual/api/reference/dashboard/widget_fields/problems) -   [SLA report](/manual/api/reference/dashboard/widget_fields/sla_report) -   [System information](/manual/api/reference/dashboard/widget_fields/system) -   [Problems by severity](/manual/api/reference/dashboard/widget_fields/problems_severity) -   [Top hosts](/manual/api/reference/dashboard/widget_fields/top_hosts) -   [Trigger overview](/manual/api/reference/dashboard/widget_fields/trigger_overview) -   [URL](/manual/api/reference/dashboard/widget_fields/url) -   [Web monitoring](/manual/api/reference/dashboard/widget_fields/web_monitoring)  Deprecated widgets:  -   [Data overview](/manual/api/reference/dashboard/widget_fields/data_overview)
zh-cn	 This page contains navigation links for dashboard widget parameters and possible property values for the respective [dashboard widget field](/manual/api/reference/dashboard/object#dashboard-widget-field) objects.  To see the parameters and property values for each widget, go to individual widget pages for:  -   [Action log](/manual/api/reference/dashboard/widget_fields/action_log) -   [Clock](/manual/api/reference/dashboard/widget_fields/clock) -   [Discovery status](/manual/api/reference/dashboard/widget_fields/discovery_status) -   [Favorite graphs](/manual/api/reference/dashboard/widget_fields/favorite_graphs) -   [Favorite maps](/manual/api/reference/dashboard/widget_fields/favorite_maps) -   [Geomap](/manual/api/reference/dashboard/widget_fields/geomap) -   [Graph](/manual/api/reference/dashboard/widget_fields/graph) -   [Graph (classic)](/manual/api/reference/dashboard/widget_fields/graph_classic) -   [Graph prototype](/manual/api/reference/dashboard/widget_fields/graph_prototype) -   [Host availability](/manual/api/reference/dashboard/widget_fields/host_availability) -   [Item value](/manual/api/reference/dashboard/widget_fields/item_value) -   [Map](/manual/api/reference/dashboard/widget_fields/map) -   [Map navigation tree](/manual/api/reference/dashboard/widget_fields/map_tree) -   [Plain text](/manual/api/reference/dashboard/widget_fields/plain_text) -   [Problem hosts](/manual/api/reference/dashboard/widget_fields/problem_hosts) -   [Problems](/manual/api/reference/dashboard/widget_fields/problems) -   [SLA report](/manual/api/reference/dashboard/widget_fields/sla_report) -   [System information](/manual/api/reference/dashboard/widget_fields/system) -   [Problems by severity](/manual/api/reference/dashboard/widget_fields/problems_severity) -   [Top hosts](/manual/api/reference/dashboard/widget_fields/top_hosts) -   [Trigger overview](/manual/api/reference/dashboard/widget_fields/trigger_overview) -   [URL](/manual/api/reference/dashboard/widget_fields/url) -   [Web monitoring](/manual/api/reference/dashboard/widget_fields/web_monitoring)  Deprecated widgets:  -   [Data overview](/manual/api/reference/dashboard/widget_fields/data_overview)

en-us	##### - Threshold to reach  (**timeleft** only)\ Parameter `threshold` specifies a value the analyzed item has to reach, no difference if from above or from below. Once we have determined f(t) (see below), we should solve equation f(t) = `threshold` and return the root which is closer to now and to the right from now or 999999999999.9999 if there is no such root.  ::: notetip When item values approach the threshold and then cross it, **timeleft** assumes that intersection is already in the past and therefore switches to the next intersection with `threshold` level, if any. Best practice should be to use predictions as a complement to ordinary problem diagnostics, not as a substitution.[^1] :::
zh-cn	##### 2.3 达到阈值  (仅限**timeleft** )\ 参数 `threshold`指定分析监控项必须达到的值，不管从上还是从下达到。一旦确定了f(t) (见下文) ，我们应该求解方程 f(t) = `threshold`并返回更靠近现在和从现在开始向右的根，如果没有这样的根，则返回 999999999999.9999。  ::: notetip 当监控项值接近阈值然后越过它时, **timeleft** 假定交叉点已经过去，因此切换 `threshold` 水平的, 水平的下一个交叉点（如果有）。最佳实践应该是使用预测作为普通问题诊断的补充，而不是替代。[^1] :::

en-us	#### Timeout and session termination  IPMI message timeouts and retry counts are defined in OpenIPMI library. Due to the current design of OpenIPMI, it is not possible to make these values configurable in Zabbix, neither on interface nor item level.  IPMI session inactivity timeout for LAN is 60 +/-3 seconds. Currently it is not possible to implement periodic sending of Activate Session command with OpenIPMI. If there are no IPMI item checks from Zabbix to a particular BMC for more than the session timeout configured in BMC then the next IPMI check after the timeout expires will time out due to individual message timeouts, retries or receive error. After that a new session is opened and a full rescan of the BMC is initiated. If you want to avoid unnecessary rescans of the BMC it is advised to set the IPMI item polling interval below the IPMI session inactivity timeout configured in BMC.
zh-cn	#### 关于IPMI离散传感器的注意事项  要在主机上找到传感器启动Zabbix服务器，启用**DebugLevel=4**。等待几分钟，并在Zabbix服务器日志文件中查找传感器发现记录：      $ grep 'Added sensor' zabbix_server.log     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:7 id:'CATERR' reading_type:0x3 ('discrete_state') type:0x7 ('processor') full_name:'(r0.32.3.0).CATERR'     8358:20130318:111122.170 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'CPU Therm Trip' reading_type:0x3 ('discrete_state') type:0x1 ('temperature') full_name:'(7.1).CPU Therm Trip'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'System Event Log' reading_type:0x6f ('sensor specific') type:0x10 ('event_logging_disabled') full_name:'(7.1).System Event Log'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'PhysicalSecurity' reading_type:0x6f ('sensor specific') type:0x5 ('physical_security') full_name:'(23.1).PhysicalSecurity'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'IPMI Watchdog' reading_type:0x6f ('sensor specific') type:0x23 ('watchdog_2') full_name:'(7.7).IPMI Watchdog'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'Power Unit Stat' reading_type:0x6f ('sensor specific') type:0x9 ('power_unit') full_name:'(21.1).Power Unit Stat'     8358:20130318:111122.171 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Ctrl %' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.1).P1 Therm Ctrl %'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:16 id:'P1 Therm Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(3.2).P1 Therm Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 2' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 2'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:13 id:'System Fan 3' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).System Fan 3'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'P1 Mem Margin' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).P1 Mem Margin'     8358:20130318:111122.172 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'Front Panel Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Front Panel Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:15 id:'Baseboard Temp' reading_type:0x1 ('threshold') type:0x1 ('temperature') full_name:'(7.6).Baseboard Temp'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +5.0V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +5.0V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +3.3V STBY' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V STBY'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:9 id:'BB +3.3V' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +3.3V'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.5V P1 DDR3' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.5V P1 DDR3'     8358:20130318:111122.173 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:17 id:'BB +1.1V P1 Vccp' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.1V P1 Vccp'     8358:20130318:111122.174 Added sensor: host:'192.168.1.12:623' id_type:0 id_sz:14 id:'BB +1.05V PCH' reading_type:0x1 ('threshold') type:0x2 ('voltage') full_name:'(7.1).BB +1.05V PCH'  要解码IPMI传感器类型和状态，请在http:*www.intel.com/content/www/us/en/servers/ipmi/ipmi-specifications.html (在撰写本文时，最新的文件是http:*www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf)获取IPMI2.0规范的副本  开始的第一个参数是“reading\_type”。从规范中使用“表42-1，事件/读取类型代码范围”来解码“reading\_type”代码。我们示例中的大多数传感器都有“reading\_type：0x1”，这意味着是“threshold”传感器。 “表42-3，传感器类型代码”表示：“类型：0x1”表示温度传感器；“类型：0x2” -电压传感器；“类型：0x4” -风扇等阈值传感器有时称为“模拟”传感器，因为它们测量连续参数，如温度，电压，每分钟转数。  另一个例子 -一个带有“read\_type：0x3”的传感器。“表42-1，事件/读取类型代码范围”表示读取类型代码02h-0Ch表示“通用离散”传感器。离散传感器具有多达15个可能的状态（换句话说-最多15个有意义的位）。例如，对于具有“type：0x7”的传感器“CATERR”，“表42-3，传感器类型代码”表示此类型“处理器”，各个位的含义是：00h（最低有效位）-IERR ；01h - 散热等。  在我们的示例中有几个传感器具有“reading\_type：0x6f”。对于这些传感器，“表42-1，事件/读取类型代码范围”建议使用“表42-3，传感器类型代码”来解码位的含义。 例如，传感器“Power Unit Stat”的类型为“0x9”，表示“Power Unit”。 Offset 00h表示“PowerOff / Power Down”。换句话说，如果最低有效位为1，则服务器断电。为了测试这个位，可以使用**band**与掩码1的功能。触发表达式可能就像         {www.zabbix.com:Power Unit Stat.band(#1,1)}=1  警告服务器关机。

en-us	##### Timeout processing  Zabbix will not process a simple check longer than the Timeout seconds defined in the Zabbix server/proxy configuration file.
zh-cn	##### 超时处理  如果简单检查时间超过了 Zabbix server 或是 proxy 配置文件中设置的超时时间，Zabbix 将不会做处理。

en-us	##### Time period selector  Take note of the time period selector above the graph. It allows selecting often required periods with one mouse click.  See also: [Time period selector](/manual/config/visualization/graphs/simple#time_period_selector)
zh-cn	##### 时间段选择器  记下图表上方的时间段选择器。 它允许通过一次鼠标单击选择经常需要的时间段。  另请参见： [时间段选择器](/manual/config/visualization/graphs/simple#time_period_selector)

en-us	#### Time period selector  The [time period selector](/manual/config/visualization/graphs/simple#time_period_selector) allows to select often required periods with one mouse click. The time period selector can be opened by clicking on the time period tab next to the filter.  Clicking on *Show* in the Graph column displays a bar graph where availability information is displayed in bar format each bar representing a past week of the current year.  ![](../../../../../assets/en/manual/web_interface/availability_bar.png){width="600"}  The green part of a bar stands for OK time and red for problem time.
zh-cn	 #### 时间段选择器  [时间段选择器](/manual/config/visualization/graphs/simple#时间段选择器)允许通过单击鼠标选择经常需要的周期。通过单击过滤器旁边的时间段选项卡，可以打开时间段选择器。  单击图形列中的*查看*，将显示一个条形图，其中可用性信息以条形图的形式显示，每个条形图代表当前一年中过去的一周。  ![](../../../../../assets/en/manual/web_interface/availability_bar.png){width="600"}  条形图的绿色部分代表正常时间，红色部分代表异常时间。

en-us	##### Time period  The **second** parameter allows to specify the time period for aggregation. The time period can only be expressed as time, the amount of values (prefixed with **\#**) is not supported.  [Supported unit symbols](/manual/appendix/suffixes) can be used in this parameter for convenience, for example '5m' (five minutes) instead of '300s' (300 seconds) or '1d' (one day) instead of '86400' (86400 seconds).  Time period is ignored by the server if passed with the *last\_foreach* function and can thus be omitted:      last_foreach(/*/key?[group="host group"])  Time period is not supported with the *exists\_foreach* function.
zh-cn	##### 时间段  **second** 参数允许指定时间段 聚合。时间段只能表示为时间，数量 不支持值（以 **\#** 为前缀）。  [Supported unit symbols](/manual/appendix/suffixes) 可以用在这个 为方便起见参数，例如“5m”（五分钟）而不是 '300s'（300 秒）或 '1d'（一天）而不是 '86400'（86400 秒）。  如果与 *last\_foreach* 一起传递，服务器将忽略时间段 函数，因此可以省略：      last_foreach(/*/key?[group="host group"])  *exists\_foreach* 函数不支持时间段。

en-us	 To add a child service, press on the plus icon next to the Zabbix cluster service (the icon is visible only in *Edit* mode).  ![](../../../assets/en/manual/config/service_cluster2.png){width=600}  In the service configuration window, enter name *Zabbix server node 1*. Note that the Parent services parameter is already pre-filled with *Zabbix cluster*.   Availability of this service is affected by problems on the host *HA node 1*, marked with `component:HA node 1` problem tag. In the Problem tags parameter, enter:  - Name: component - Operation: Equals - Value: HA node 1  ![](../../../assets/en/manual/config/service_cluster3.png){width=600}  Switch to the *Tags* tab and add a service tag: `Zabbix server:node 1`. This tag will be used later for service actions and SLA reports.  ![](../../../assets/en/manual/config/service_cluster4.png){width=600}  Save the new service. 
zh-cn	 点击Zabbix集群服务旁边的加号图标(只有*编辑*模式才能看到加号图标)来创建子服务。  ![](../../../assets/en/manual/config/service_cluster2.png){width=600}  在服务配置窗口输入名称*Zabbix server node 1*。注意，父服务的参数已经用*Zabbix集群*预先填充了。   该服务的可用性受主机*HA node 1*产生的问题所影响，通过`component:HA node 1` 问题标签所标记。在问题标签参数中输入：  - 名称：组件 - 操作: 等于 - 值: HA node 1  ![](../../../assets/en/manual/config/service_cluster3.png){width=600}  切换到 *标签* 面板并添加服务标签：`Zabbix server:node 1`。此标签会用于后续的服务动作和SLA报告。   ![](../../../assets/en/manual/config/service_cluster4.png){width=600}  保存新建的服务。

en-us	# token.create
zh-cn	# 创建

en-us	# token.delete
zh-cn	# 删除

en-us	# token.generate
zh-cn	# 生成

en-us	# token.get
zh-cn	# 获取

en-us	# > Token object  The following objects are directly related to the `token` API.
zh-cn	# > 令牌对象  以下对象与 `令牌` API 直接相关。

en-us	# Token  This class is designed to work with tokens.  Object references:\  -   [Token](/manual/api/reference/token/object)  Available methods:\  -   [token.create](/manual/api/reference/token/create) - create new     tokens -   [token.delete](/manual/api/reference/token/delete) - delete tokens -   [token.get](/manual/api/reference/token/get) - retrieve tokens -   [token.update](/manual/api/reference/token/update) - update tokens -   [token.generate](/manual/api/reference/token/generate) - generate     tokens
zh-cn	# 令牌  此类用于管理令牌。  对象引用：\  -   [令牌](/manual/api/reference/token/object)  可用方法：\  -   [token.create](/manual/api/reference/token/create) - 创建新的令牌 -   [token.delete](/manual/api/reference/token/delete) - 删除令牌 -   [token.get](/manual/api/reference/token/get) - 获取令牌 -   [token.update](/manual/api/reference/token/update) - 更新令牌 -   [token.generate](/manual/api/reference/token/generate) - 生成令牌

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

en-us	#### Too long PSK value used with OpenSSL 1.1.1  In connecting-side log:      ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK 1"     ...zbx_psk_client_cb() requested PSK identity "PSK 1"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() set result code to SSL_ERROR_SSL: file ssl\statem\extensions_clnt.c line 801: error:14212044:SSL routines:tls_construct_ctos_early_data:internal error: TLS write fatal alert "internal error"'  In accepting-side log:      ...Message from 123.123.123.123 is missing header. Message ignored.  This problem typically arises when upgrading OpenSSL from 1.0.x or 1.1.0 to 1.1.1 and if the PSK value is longer than 512-bit (64-byte PSK, entered as 128 hexadecimal digits).  See also: [Value size limits](/manual/encryption/using_pre_shared_keys#size_limits)
zh-cn	 #### OpenSSL 1.1.1 使用了过长的PSK值  在连接发起端的日志中，会有如下信息显示：      ...OpenSSL library (version OpenSSL 1.1.1  11 Sep 2018) initialized     ...     ...In zbx_tls_connect(): psk_identity:"PSK 1"     ...zbx_psk_client_cb() requested PSK identity "PSK 1"     ...End of zbx_tls_connect():FAIL error:'SSL_connect() set result code to SSL_ERROR_SSL: file ssl\statem\extensions_clnt.c line 801: error:14212044:SSL routines:tls_construct_ctos_early_data:internal error: TLS write fatal alert "internal error"'  在连接接收端的日志中，会有如下信息显示：      ...Message from 123.123.123.123 is missing header. Message ignored.  将 OpenSSL 从 1.0.x 或 1.1.0 升级到 1.1.1 以及 PSK 值的长度超过 512 位（64 字节 PSK，以 128 个十六进制数字输入）时，通常会出现此问题。  参考: [值大小限制](/manual/encryption/using_pre_shared_keys#size_limits)

en-us	#### Translating customized severity names  ::: noteimportant If Zabbix frontend translations are used, custom severity names will override translated names by default. ::: Default trigger severity names are available for translation in all locales. If a severity name is changed, a custom name is used in all locales and additional manual translation is needed.  Custom severity name translation procedure:  -   set required custom severity name, for example, 'Important' -   edit     <frontend\_dir>/locale/<required\_locale>/LC\_MESSAGES/frontend.po -   add 2 lines:  ```{=html} <!-- --> ```     msgid "Important"     msgstr "<translation string>"  and save file.  -   create .mo files as described in <frontend\_dir>/locale/README  Here **msgid** should match the new custom severity name and **msgstr** should be the translation for it in the specific language.  This procedure should be performed after each severity name change.
zh-cn	#### 翻译自定义严重性的名称  ::: noteimportant 如果使用Zabbix前端翻译, 自定义严重性名称将会覆盖默认翻译名称。 ::: 默认触发器严重性名称可用于在所有语言环境中进行翻译。如果更改严重性名称，则会在所有区域设置中使用自定义名称，并且需要额外的手动翻译。  自定义严重性名称的翻译步骤:  -   设置自定义严重性名称，例如 '重要' -   编辑<frontend\_dir>/locale/<required\_locale>/LC\_MESSAGES/frontend.po -   添加如下2行:  ```{=html} <!-- --> ```     msgid "Important"     msgstr "<translation string>"  保存文件。  -   在<frontend\_dir>/locale/README创建.mo文件作为描述  这里 **msgid** 应该匹配新的自定义严重性名称， **msgstr** 应该是用特定语言翻译的。  此过程应在每个严重性名称更改之后执行。

en-us	#### Trapper process  Receiving internal metric requests from an external Zabbix instance is handled by the trapper process that validates the request, gathers the metrics, creates the JSON data buffer and sends the prepared JSON back, for example, from server:  ``` {.java} {   "response": "success",   "data": {     "boottime": N,     "uptime": N,     "hosts": N,     "items": N,     "items_unsupported": N,     "preprocessing_queue": N,     "process": {       "alert manager": {         "busy": {           "avg": N,           "max": N,           "min": N         },         "idle": {           "avg": N,           "max": N,           "min": N         },         "count": N       }, ...     },     "queue": N,     "rcache": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "requiredperformance": N,     "triggers": N,     "uptime": N,     "vcache": {       "buffer": {         "total": N,         "free": N,         "pfree": N,         "used": N,         "pused": N       },       "cache": {         "requests": N,         "hits": N,         "misses": N,         "mode": N       }     },     "vmware": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "version": "N",     "wcache": {       "values": {         "all": N,         "float": N,         "uint": N,         "str": N,         "log": N,         "text": N,         "not supported": N       },       "history": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "index": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "trend": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       }     }   } } ```
zh-cn	 #### 捕捉器执行过程  Zabbix实例接收内部指标请求由trapper进程处理，trapper进程验证请求、收集、创建JSON数据缓冲区并将准备好的JSON发回，例如从服务器:  ``` {.java} {   "response": "success",   "data": {     "boottime": N,     "uptime": N,     "hosts": N,     "items": N,     "items_unsupported": N,     "preprocessing_queue": N,     "process": {       "alert manager": {         "busy": {           "avg": N,           "max": N,           "min": N         },         "idle": {           "avg": N,           "max": N,           "min": N         },         "count": N       }, ...     },     "queue": N,     "rcache": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "requiredperformance": N,     "triggers": N,     "uptime": N,     "vcache": {       "buffer": {         "total": N,         "free": N,         "pfree": N,         "used": N,         "pused": N       },       "cache": {         "requests": N,         "hits": N,         "misses": N,         "mode": N       }     },     "vmware": {       "total": N,       "free": N,       "pfree": N,       "used": N,       "pused": N     },     "version": "N",     "wcache": {       "values": {         "all": N,         "float": N,         "uint": N,         "str": N,         "log": N,         "text": N,         "not supported": N       },       "history": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "index": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       },       "trend": {         "pfree": N,         "free": N,         "total": N,         "used": N,         "pused": N       }     }   } } ```

en-us	# trend.get
zh-cn	# 检索趋势

en-us	# > Trend object  The following objects are directly related to the `trend` API.  ::: noteclassic Trend objects differ depending on the item's type of information. They are created by the Zabbix server and cannot be modified via the API. :::
zh-cn	# > 趋势对象  以下对象与 `trend` API 直接相关.  ::: noteclassic 趋势对象根据监控项类型的信息而有所不同，它们由Zabbix Server创建，不能通过API进行修改. :::

en-us	#### Trends  Retrieve trend values calculated by Zabbix server for presentation or further processing.  [Trend API](/manual/api/reference/trend)
zh-cn	#### 趋势  检索由 Zabbix Server 计算的趋势值以进行展示或进一步处理。  [Trend API](/manual/api/reference/trend)

en-us	# Trend  This class is designed to work with trend data.  Object references:\  -   [Trend](/manual/api/reference/trend/object#trend)  Available methods:\  -   [trend.get](/manual/api/reference/trend/get) - retrieving trends
zh-cn	# 趋势  此类用于处理趋势数据.  对象引用:  -   [趋势](/manual/api/reference/trend/object#trend)  可用方法:  -   [trend.get](/manual/api/reference/trend/get) - 检索趋势数据

en-us	# trigger.create
zh-cn	# 创建触发器

en-us	# trigger.delete
zh-cn	# 删除触发器

en-us	#### Trigger events  The following information is exported for a problem event:  |Field|<|<|Type|Description| |-|-|----------|----------|------------------------------| |*clock*|<|<|number|Number of seconds since Epoch to the moment when problem was detected (integer part).| |*ns*|<|<|number|Number of nanoseconds to be added to `clock` to get a precise problem detection time.| |*value*|<|<|number|1 (always).| |*eventid*|<|<|number|Problem event ID.| |*name*|<|<|string|Problem event name.| |*severity*|<|<|number|Problem event severity (0 - Not classified, 1 - Information, 2 - Warning, 3 - Average, 4 - High, 5 - Disaster).| |*hosts*|<|<|array|List of hosts involved in the trigger expression; there should be at least one element in array.| | |\-|<|object|<| |^| |*host*|string|Host name.| |^|^|*name*|string|Visible host name.| |*groups*|<|<|array|List of host groups of all hosts involved in the trigger expression; there should be at least one element in array.| | |\-|<|string|Host group name.| |*tags*|<|<|array|List of problem tags (can be empty).| | |\-|<|object|<| |^| |*tag*|string|Tag name.| |^|^|*value*|string|Tag value (can be empty).|  The following information is exported for a recovery event:  |Field|Type|Description| |--|--|------| |*clock*|number|Number of seconds since Epoch to the moment when problem was resolved (integer part).| |*ns*|number|Number of nanoseconds to be added to `clock` to get a precise problem resolution time.| |*value*|number|0 (always).| |*eventid*|number|Recovery event ID.| |*p\_eventid*|number|Problem event ID.|
zh-cn	#### 触发器事件  为问题事件导出以下信息:  |字段|<|<|类型|描述| |-----|-|-|----|-----------| |*clock*|<|<|number|检测到问题的那一刻的时间秒数（整数部分）| |*ns*|<|<|number|要添加到`clock`以获得精确问题检测时间的纳秒数。| |*value*|<|<|number|1 (总是).| |*eventid*|<|<|number|问题事件ID.| |*name*|<|<|string|问题事件名称.| |*severity*|<|<|number|问题事件严重性 (0 - 未分类, 1 - 信息, 2 - 警告, 3 - 一般严重, 4 - 严重, 5 - 灾难).| |*hosts*|<|<|array|触发器表达式中涉及的主机列表;数组中应至少有一个元素。| |<|\-|<|object|<| |<|<|*host*|string|主机名.| |<|<|*name*|string|可见主机名| |*groups*|<|<|array|触发器表达式中涉及的所有主机的主机组列表;数组中应至少有一个元素.| |<|\-|<|string|主机组名称.| |*tags*|<|<|array|问题标签列表（可以为空）.| |<|\-|<|object|<| |<|<|*tag*|string|标签名称.| |<|<|*value*|string|标签值(可以为空).|  为恢复事件导出以下信息:  |字段|类型|描述| |-----|----|-----------| |*clock*|number|问题恢复那一刻的时间秒数（整数部分）.| |*ns*|number|要添加到`clock`以获得精确问题恢复时间的纳秒数。| |*value*|number|0 (总是).| |*eventid*|number|恢复事件ID.| |*p\_eventid*|number|问题事件ID.|

en-us	# trigger.get
zh-cn	# 检索触发器

en-us	##### Trigger lines  Simple triggers are displayed as lines with black dashes over trigger severity color -- take note of the blue line on the graph and the trigger information displayed in the legend. Up to 3 trigger lines can be displayed on the graph; if there are more triggers then the triggers with lower severity are prioritized. Triggers are always displayed in simple graphs, whereas displaying them in [custom graphs](custom#configuring_custom_graphs) is a user preference.  ![simple\_graph\_trigger.png](../../../../../assets/en/manual/config/simple_graph_trigger.png)
zh-cn	##### 触发器线  单一触发器显示成一条带有触发器严重性颜色的黑色虚线——注意图表上的蓝线和图例中显示的触发信息。最多 3 条触发器线可以显示在图表上；如果有更多触发器，那么严重性较低的触发器优先展示。触发器总是会显示在单一图表中，而在[自定义图表](custom#configuring_custom_graphs) 中可按照用户偏好显示。  ![simple\_graph\_trigger.png](../../../../../assets/en/manual/config/simple_graph_trigger.png)

en-us	# > Trigger object  The following objects are directly related to the `trigger` API.
zh-cn	# > 触发器对象  以下对象与`trigger`API直接相关.

en-us	# triggerprototype.create
zh-cn	# 创建触发器原型

en-us	# triggerprototype.delete
zh-cn	# 删除触发器原型

en-us	# triggerprototype.get
zh-cn	# 检索触发器原型

en-us	# > Trigger prototype object  The following objects are directly related to the `triggerprototype` API.
zh-cn	# > 触发器原型对象  以下对象与`triggerprototype`API直接相关.

en-us	# Trigger prototype  This class is designed to work with trigger prototypes.  Object references:\  -   [Trigger     prototype](/manual/api/reference/triggerprototype/object#trigger_prototype)  Available methods:\  -   [triggerprototype.create](/manual/api/reference/triggerprototype/create) -     creating new trigger prototypes -   [triggerprototype.delete](/manual/api/reference/triggerprototype/delete) -     deleting trigger prototypes -   [triggerprototype.get](/manual/api/reference/triggerprototype/get) -     retrieving trigger prototypes -   [triggerprototype.update](/manual/api/reference/triggerprototype/update) -     updating trigger prototypes
zh-cn	# 触发器原型  此类用于管理触发器原型.  对象引用:  -   [触发器原型](/manual/api/reference/triggerprototype/object#trigger_prototype)  可用方法:  -   [triggerprototype.create](/manual/api/reference/triggerprototype/create) - 创建新的触发器原型 -   [triggerprototype.delete](/manual/api/reference/triggerprototype/delete) - 删除触发器原型 -   [triggerprototype.get](/manual/api/reference/triggerprototype/get) - 检索触发器原型 -   [triggerprototype.update](/manual/api/reference/triggerprototype/update) - 更新触发器原型

en-us	# triggerprototype.update
zh-cn	# triggerprototype.update

en-us	#### Triggers  Configure triggers to notify you about problems in your system. Manage trigger dependencies.  [Trigger API](/manual/api/reference/trigger)
zh-cn	#### 触发器  配置触发器以通知您系统中的问题。管理触发器依赖关系。  [Trigger API](/manual/api/reference/trigger)

en-us	##### Triggers  Triggers have an 'OK event generation' setting that controls how OK events are generated:  -   *Expression* - an OK event is generated for a trigger in problem     state when its expression evaluates to FALSE. This is the simplest     setting, enabled by default. -   *Recovery expression* - an OK event is generated for a trigger in     problem state when its expression evaluates to FALSE and the     recovery expression evaluates to TRUE. This can be used if trigger     recovery criteria is different from problem criteria. -   *None* - an OK event is never generated. This can be used in     conjunction with multiple problem event generation to simply send a     notification when something happens.  Additionally triggers have an 'OK event closes' setting that controls which problem events are closed:  -   *All problems* - an OK event will close all open problems created by     the trigger -   *All problems if tag values match* - an OK event will close open     problems created by the trigger and having at least one matching tag     value. The tag is defined by 'Tag for matching' trigger setting. If     there are no problem events to close then OK event is not generated.     This is often called trigger level event correlation.
zh-cn	##### 触发器  触发器有“正常事件生成”的设置用来控制如何生成正常事件：  -   *表达式*——当触发器在问题状态其表达式评估为FALSE时，会生成一个正常事件。这是最简单的设置，默认启用。 -   *恢复表达式*——当触发器在问题状态其表达式评估为FALSE且恢复表达式评估为TRUE。如果触发器恢复标准与问题标准不同可以使用此设置。 -   *无*——不生成正常事件，可以与多个问题事件生成组合使用，当某事件发生时可以简单地发送通知。  此外，触发器有“正常事件关闭”的设置用来控制关闭问题事件：  -   *所有问题* ——正常事件会关闭该触发器打开的所有问题事件。 -   *标签值匹配的所有问题* ——正常事件会关闭该触发器打开的所有问题事件并且至少有一个匹配的标签值。此标签由“匹配标签“的触发器设置。如果没有要关闭的问题事件就不会生成正常事件。这通常称为触发器级别事件关联。

en-us	# trigger.update
zh-cn	# 更新触发器

en-us	##### Trigger  With the item working you need to configure the [trigger](/manual/config/triggers/trigger). It's important to decide what entries in the log file are worth paying attention to. For example, the following trigger expression will search for a string like 'Stopping' to signal potential problems:      find(/My host/log[/var/log/syslog],,"regexp","Stopping")=1   ::: noteimportant To make sure that each line containing the string "Stopping" is considered a problem also set the *Problem event generation mode* in trigger configuration to 'Multiple'. :::  Then define a recovery expression. The following recovery expression will resolve all problems if a log line is found containing the string "Starting":      find(/My host/log[/var/log/syslog],,"regexp","Starting")=1   Since we do not want that it's important to make sure somehow that the corresponding root problems are closed, not just all problems. That's where tagging can help.  Problems and resolutions can be matched by specifying a tag in the trigger configuration. The following settings have to be made:  -   *Problem event generation mode*: Multiple -   *OK event closes*: All problems if tag values match -   Enter the name of the tag for event matching  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger.png)  -   configure the [tags](/manual/config/tagging) to extract tag values     from log lines  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger2.png)  If configured successfully you will be able to see problem events tagged by application and matched to their resolution in *Monitoring* → *Problems*.  ![](../../../../assets/en/manual/config/matched_problems.png){width="600"}  ::: notewarning Because misconfiguration is possible, when similar event tags may be created for **unrelated** problems, please review the cases outlined below! :::  -   With two applications writing error and recovery messages to the     same log file a user may decide to use two *Application* tags in the     same trigger with different tag values by using separate regular     expressions in the tag values to extract the names of, say,     application A and application B from the {ITEM.VALUE} macro (e.g.     when the message formats differ). However, this may not work as     planned if there is no match to the regular expressions.     Non-matching regexps will yield empty tag values and a single empty     tag value in both problem and OK events is enough to correlate them.     So a recovery message from application A may accidentally close an     error message from application B.  ```{=html} <!-- --> ``` -   Actual tags and tag values only become visible when a trigger fires.     If the regular expression used is invalid, it is silently replaced     with an \*UNKNOWN\* string. If the initial problem event with an     \*UNKNOWN\* tag value is missed, there may appear subsequent OK     events with the same \*UNKNOWN\* tag value that may close problem     events which they shouldn't have closed.  ```{=html} <!-- --> ``` -   If a user uses the {ITEM.VALUE} macro without macro functions as the     tag value, the 255-character limitation applies. When log messages     are long and the first 255 characters are non-specific, this may     also result in similar event tags for unrelated problems.
zh-cn	##### 触发器  要让监控项工作，你需要配置[触发器](/manual/config/triggers/trigger)。重要的是要决定日志文件中哪些条目值得注意。例如，以下触发表达式将搜索像“Stopping”这样的字符串来发现潜在问题的信号：      find(/My host/log[/var/log/syslog],,"regexp","Stopping")=1   ::: noteimportant 为了确保包含字符串“Stopping”的每一行都被视为问题，还要在触发器配置中将*问题事件生成模式*设置为"多种”。 :::  然后定义一个恢复表达式。如果发现包含字符串“starting”的日志行，以下恢复表达式将解决所有问题：      find(/My host/log[/var/log/syslog],,"regexp","Starting")=1   由于以某种方式确保相应的根因问题得到解决很重要，我们不希望仅仅是解决所有问题。这就是标签可以提供帮助的地方。  问题和解决方案可以通过在触发器配置中指定标签来匹配。必须进行以下设置：  -   *问题事件生成模式*：多种 -   *正常事件关闭*：如果标签匹配所有事件 -   输入事件匹配的标签名称  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger.png)  -   配置[标签](/manual/config/tagging)从日志行中获取标签值  ![](../../../../assets/en/manual/config/event_correlation/correlation_trigger2.png)  如果配置成功，你将在*监控*→*问题*里看到问题事件被应用程序标识并匹配它们的解决方案  ![](../../../../assets/en/manual/config/matched_problems.png){width="600"}  ::: notewarning 因为可能配置错误，会为不*关联*的问题创建相似的事件标签，请阅读下面列出的案例！ :::  -   两个应用程序向同一个日志文件写入错误和恢复消息时，用户可能决定为同一个触发器使用两个标签值不同的*应用*标签，在标签值中使用不同的正则表达式从{ITEM.VALUE}宏获取应用名称A和B（例如，当消息格式不同时）。然而，如果没有与正则表达式匹配，这可能无法按计划工作。不匹配的正则表达式会产生空的标签值，同一个空标签值足以将问题事件和正常事件关联起来。所以，一个来自应用A的恢复消息会意外地关闭一个来自应用B的错误消息。  ```{=html} <!-- --> ``` -   实际标签和标签值仅在触发器触发时可见。如果正则表达式使用不正确，会不做提示的自动替换为一个\*UNKNOWN\*字符串。如果最初的有\*UNKNOWN\*标签值的问题事件被错过了，随后可能会出现一个有相同\*UNKNOWN\*标签值的正常事件来关闭本不该关闭的问题事件。  ```{=html} <!-- --> ``` -   如果用户使用{ITEM.VALUE}宏而没有将宏函数设为标签值，255个字符的限制会生效。当日志消息很长并且前255个字符不是特定的，这也可能导致非关联问题拥有相似的事件标签。

en-us	#### Troubleshooting and removing agent  This section lists some useful commands that can be used for troubleshooting and removing Zabbix agent installation.  See if Zabbix agent is running:      ps aux | grep zabbix_agentd  See if Zabbix agent has been installed from packages:      $ pkgutil --pkgs | grep zabbix      com.zabbix.pkg.ZabbixAgent  See the files that were installed from the installer package (note that the initial `/` is not displayed in this view):      $ pkgutil --only-files --files com.zabbix.pkg.ZabbixAgent     Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist                                                                                                                                                                                                                                usr/local/bin/zabbix_get                                                                                                                                                                                                                                                            usr/local/bin/zabbix_sender                                                                                                                                                                                                                                                         usr/local/etc/zabbix/zabbix_agentd/userparameter_examples.conf.NEW                                                                                                                                                                                                                  usr/local/etc/zabbix/zabbix_agentd/userparameter_mysql.conf.NEW                                                                                                                                                                                                                     usr/local/etc/zabbix/zabbix_agentd.conf.NEW                                                                                                                                                                                                                                         usr/local/sbin/zabbix_agentd  Stop Zabbix agent if it was launched with `launchctl`:      sudo launchctl unload /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist  Remove files (including configuration and logs) that were installed with installer package:      sudo rm -f /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist     sudo rm -f /usr/local/sbin/zabbix_agentd     sudo rm -f /usr/local/bin/zabbix_get     sudo rm -f /usr/local/bin/zabbix_sender     sudo rm -rf /usr/local/etc/zabbix     sudo rm -rf /var/log/zabbix  Forget that Zabbix agent has been installed:      sudo pkgutil --forget com.zabbix.pkg.ZabbixAgent
zh-cn	#### 故障排除和删除代理  本节列出了一些有用的命令，可用于故障排除和删除 Zabbix 代理安装。  查看 Zabbix 代理是否正在运行：      ps aux| grep zabbix_agentd  查看是否已经从包中安装了 Zabbix 代理：      $ pkgutil --pkgs | grep zabbix     com.zabbix.pkg.ZabbixAgent  查看从安装程序包中安装的文件（请注意此视图中不显示初始的 `/` ）：      $ pkgutil --only-files --files com.zabbix.pkg.ZabbixAgent     库/LaunchDaemons/com.zabbix.zabbix_agentd.plist     usr/local/bin/zabbix_get     usr/local/bin/zabbix_sender     usr/local/etc/zabbix/zabbix_agentd/userparameter_examples.conf.NEW     usr/local/etc/zabbix/zabbix_agentd/userparameter_mysql.conf.NEW     usr/local/etc/zabbix/zabbix_agentd.conf.NEW     usr/local/sbin/zabbix_agentd  停止Zabbix代理，如果它是用 `launchctl` 启动的：      sudo launchctl unload /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist  删除随安装程序包一起安装的文件（包括配置和日志）：      sudo rm -f /Library/LaunchDaemons/com.zabbix.zabbix_agentd.plist     sudo rm -f /usr/local/sbin/zabbix_agentd     sudo rm -f /usr/local/bin/zabbix_get     sudo rm -f /usr/local/bin/zabbix_sender     sudo rm -rf /usr/local/etc/zabbix     sudo rm -rf /var/log/zabbix  移除Zabbix agent安装包：      sudo pkgutil --forget com.zabbix.pkg.ZabbixAgent

en-us	#### Troubleshooting  The following steps may help you troubleshoot problems with Elasticsearch setup:  1.  Check if the mapping is correct (GET request to required index URL     like `http://localhost:9200/uint`). 2.  Check if shards are not in failed state (restart of Elasticsearch     should help). 3.  Check the configuration of Elasticsearch. Configuration should allow     access from the Zabbix frontend host and the Zabbix server host. 4.  Check Elasticsearch logs.  If you are still experiencing problems with your installation then please create a bug report with all the information from this list (mapping, error logs, configuration, version, etc.)
zh-cn	#### 故障排除 以下步骤可以帮助您解决Elasticsearch设置问题：  1.  检查映射是否正确 (通过URL的发送GET请求获取索引信息，例如： `http://localhost:9200/uint`) 2.  检查shards状态是否正常 (不正常时重启Elasticsearch可能解决问题) 3.  检查Elasticsearch配置文件，配置文件应允许从Zabbix前端及Zabbix server主机访问。 4.  检查Elasticsearch日志  如果您仍然遇到安装问题，请创建一个错误报告，包含此列表中的所有信息（映射，错误日志，配置，版本等信息）

en-us	###      **unencrypted**   connect without encryption (default)  ```{=html} <!-- --> ```    **psk**   connect using TLS and a pre-shared key  ```{=html} <!-- --> ```    **cert**   connect using TLS and a certificate  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.  **--tls-crl-file** *CRL-file*   Full pathname of a file containing revoked certificates.  **--tls-agent-cert-issuer** *cert-issuer*   Allowed agent certificate issuer.  **--tls-agent-cert-subject** *cert-subject*   Allowed agent certificate subject.  **--tls-cert-file** *cert-file*   Full pathname of a file containing the certificate or certificate chain.  **--tls-key-file** *key-file*   Full pathname of a file containing the private key.  **--tls-psk-identity** *PSK-identity*   PSK-identity string.  **--tls-psk-file** *PSK-file*   Full pathname of a file containing the pre-shared key.  **--tls-cipher13** *cipher-string*   Cipher string for OpenSSL 1.1.1 or newer for TLS 1.3. Override the default ciphersuite selection criteria. This option is not available if OpenSSL version is less than 1.1.1.  **--tls-cipher** *cipher-string*   GnuTLS priority string (for TLS 1.2 and up) or OpenSSL cipher string (only for TLS 1.2). Override the default ciphersuite selection criteria.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAG}
zh-cn	 ###      **unencrypted**   无加密连接（默认）  ```{=html} <!-- --> ```    **psk**   使用TLS和预共享密钥进行连接  ```{=html} <!-- --> ```    **cert**   使用TLS和证书进行连接  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   包含用于对等证书验证的顶级CA证书的文件的完整路径名。  **--tls-crl-file** *CRL-file*   包含已吊销证书的文件的完整路径名。  **--tls-agent-cert-issuer** *cert-issuer*   允许的agent证书颁发者。  **--tls-agent-cert-subject** *cert-subject*   允许的agent证书主题。  **--tls-cert-file** *cert-file*   包含证书或证书链的文件的完整路径名。  **--tls-key-file** *key-file*   包含私钥的文件的完整路径名。  **--tls-psk-identity** *PSK-identity*   PSK标识字符串。  **--tls-psk-file** *PSK-file*   包含预共享密钥的文件的完整路径名。  **--tls-cipher13** *cipher-string*   OpenSSL 1.1.1或更新版本TLS 1.3的密码字符串。覆盖默认的密码套件选择条件。如果OpenSSL版本低于1.1.1，则此选项不可用。  **--tls-cipher** *cipher-string*   GnuTLS优先级字符串（适用于TLS 1.2及以上版本）或OpenSSL密码字符串（仅适用于TLS 1.2）。覆盖默认的密码套件选择条件。  **-h**, **--help**   显示本帮助信息然后退出。  **-V**, **--version**   输出版本信息然后退出  [ ]{#lbAG}

en-us	###      **unencrypted**   connect without encryption (default)  ```{=html} <!-- --> ```    **psk**   connect using TLS and a pre-shared key  ```{=html} <!-- --> ```    **cert**   connect using TLS and a certificate  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   Full pathname of a file containing the top-level CA(s) certificates for peer certificate verification.  **--tls-crl-file** *CRL-file*   Full pathname of a file containing revoked certificates.  **--tls-server-cert-issuer** *cert-issuer*   Allowed server certificate issuer.  **--tls-server-cert-subject** *cert-subject*   Allowed server certificate subject.  **--tls-cert-file** *cert-file*   Full pathname of a file containing the certificate or certificate chain.  **--tls-key-file** *key-file*   Full pathname of a file containing the private key.  **--tls-psk-identity** *PSK-identity*   PSK-identity string.  **--tls-psk-file** *PSK-file*   Full pathname of a file containing the pre-shared key.  **--tls-cipher13** *cipher-string*   Cipher string for OpenSSL 1.1.1 or newer for TLS 1.3. Override the default ciphersuite selection criteria. This option is not available if OpenSSL version is less than 1.1.1.  **--tls-cipher** *cipher-string*   GnuTLS priority string (for TLS 1.2 and up) or OpenSSL cipher string (only for TLS 1.2). Override the default ciphersuite selection criteria.  **-v**, **--verbose**   Verbose mode, **-vv** for more details.  **-h**, **--help**   Display this help and exit.  **-V**, **--version**   Output version information and exit.  [ ]{#lbAG}
zh-cn	 ###      **unencrypted**   无加密连接（默认）  ```{=html} <!-- --> ```    **psk**   使用TLS和预共享密钥进行连接  ```{=html} <!-- --> ```    **cert**   使用TLS和证书进行连接  ```{=html} <!-- --> ``` **--tls-ca-file** *CA-file*   包含用于对等证书验证的顶级CA证书的文件的完整路径名。  **--tls-crl-file** *CRL-file*   包含已吊销证书的文件的完整路径名。  **--tls-server-cert-issuer** *cert-issuer*   允许的服务器证书颁发者。  **--tls-server-cert-subject** *cert-subject*   允许的服务器证书主题。  **--tls-cert-file** *cert-file*   包含证书或证书链的文件的完整路径名。  **--tls-key-file** *key-file*   包含私钥的文件的完整路径名。  **--tls-psk-identity** *PSK-identity*   PSK标识字符串。  **--tls-psk-file** *PSK-file*   包含预共享密钥的文件的完整路径名。  **--tls-cipher13** *cipher-string*   OpenSSL 1.1.1或更新版本TLS 1.3的密码字符串。覆盖默认的密码套件选择条件。如果OpenSSL版本低于1.1.1，则此选项不可用。  **--tls-cipher** *cipher-string*   GnuTLS优先级字符串（适用于TLS 1.2及以上版本）或OpenSSL密码字符串（仅适用于TLS 1.2）。覆盖默认的密码套件选择条件。  **-v**, **--verbose**   详细模式，**-vv**了解更多详细信息。  **-h**, **--help**   显示这个帮助的内容并退出。  **-V**, **--version**   输出版本信息并退出。  [ ]{#lbAG}

en-us	#### Uninstalling agent Windows service  To uninstall a single instance of Zabbix agent using the default configuration file:         zabbix_agentd.exe --uninstall  To uninstall a single instance of Zabbix agent using a non-default configuration file:         zabbix_agentd.exe --config <your_configuration_file> --uninstall  To uninstall multiple instances of Zabbix agent from Windows services:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --uninstall --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --uninstall --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --uninstall --multiple-agents
zh-cn	#### 卸载Windows 服务上的 zabbix agent   使用默认配置文件卸载单个实例的 Zabbix agent:         zabbix_agentd.exe --uninstall  指定配置文件卸载单个实例的 Zabbix agent:         zabbix_agentd.exe --config <your_configuration_file> --uninstall  卸载多个Zabbix agent实例，请执行以下操作:        zabbix_agentd.exe --config <configuration_file_for_instance_1> --uninstall --multiple-agents       zabbix_agentd.exe --config <configuration_file_for_instance_2> --uninstall --multiple-agents       ...       zabbix_agentd.exe --config <configuration_file_for_instance_N> --uninstall --multiple-agents

en-us	#### Unit conversion  By default, specifying a unit for an item results in a multiplier prefix being added - for example, an incoming value '2048' with unit 'B' would be displayed as '2KB'.  To prevent a unit from conversion, use the `!` prefix, for example, `!B`. To better understand how the conversion works with and without the exclamation mark, see the following examples of values and units:      1024 !B → 1024 B     1024 B → 1 KB     61 !s → 61 s     61 s → 1m 1s     0 !uptime → 0 uptime     0 uptime → 00:00:00     0 !! → 0 !     0 ! → 0  ::: noteclassic Before Zabbix 4.0, there was a hardcoded unit stoplist consisting of `ms`, `rpm`, `RPM`, `%`. This stoplist has been deprecated, thus the correct way to prevent converting such units is `!ms`, `!rpm`, `!RPM`, `!%`. :::
zh-cn	#### 单位转换  默认情况下，为监控项指定单位会自动添加该单位的乘数前缀 - 例如，单位为“B”的传入值“2048”将显示为“2KB”。  但是，可以通过使用 `!` 前缀来阻止单位转换，例如 `!B`。为了更好地理解在有单位转换和没有单位转换的情况下转换的方式，请参见以下值和单位示例：      1024 !B → 1024 B     1024 B → 1 KB     61 !s → 61 s     61 s → 1m 1s     0 !uptime → 0 uptime     0 uptime → 00:00:00     0 !! → 0 !     0 ! → 0  ::: noteclassic 在Zabbix 4.0之前，有一个硬编码的单位黑名单包括 `ms`, `rpm`, `RPM`, `%`。这个黑名单已被弃用，因此阻止这些单位转换的正确方法是使用 `!ms`, `!rpm`, `!RPM`, `!%`。 :::

en-us	#### Unreachable interface  A host interface is treated as unreachable after a failed check (network error, timeout) by Zabbix, SNMP, IPMI or JMX agents. Note that Zabbix agent active checks do not influence interface availability in any way.  From that moment **UnreachableDelay** defines how often an interface is rechecked using one of the items (including LLD rules) in this unreachability situation and such rechecks will be performed already by unreachable pollers (or IPMI pollers for IPMI checks). By default it is 15 seconds before the next check.  In the Zabbix server log unreachability is indicated by messages like these:      Zabbix agent item "system.cpu.load[percpu,avg1]" on host "New host" failed: first network error, wait for 15 seconds     Zabbix agent item "system.cpu.load[percpu,avg15]" on host "New host" failed: another network error, wait for 15 seconds  Note that the exact item that failed is indicated and the item type (Zabbix agent).  ::: noteclassic The *Timeout* parameter will also affect how early an interface is rechecked during unreachability. If the Timeout is 20 seconds and UnreachableDelay 30 seconds, the next check will be in 50 seconds after the first attempt. :::  The **UnreachablePeriod** parameter defines how long the unreachability period is in total. By default UnreachablePeriod is 45 seconds. UnreachablePeriod should be several times bigger than UnreachableDelay, so that an interface is rechecked more than once before an interface becomes unavailable.
zh-cn	 #### 不可达主机接口  主机接口在检查失败后被视为不可访问（网络 错误，超时）由 Zabbix、SNMP、IPMI 或 JMX agent。请注意，Zabbix agent主动检查不会以任何方式影响接口可用性。  从**UnreachableDelay** 那一刻起定义了在这种无法访问的情况下使用其中一项（包括 LLD 规则）重新检查接口的频率，并且此类重新检查将由无法访问的轮询器（或用于 IPMI 检查的 IPMI 轮询器）执行。默认情况下，下次15 秒后再次检查。  在 Zabbix 服务器日志中，不可达性由以下消息指示这些：      Zabbix agent item "system.cpu.load[percpu,avg1]" on host "New host" failed: first network error, wait for 15 seconds     Zabbix agent item "system.cpu.load[percpu,avg15]" on host "New host" failed: another network error, wait for 15 seconds  请注意，指示失败的确切监控项和监控项类型 （Zabbix agent）。  ::: noteclassic 在主机不可达期间，*Timeout* 参数也会影响主机再次被检查的时间。如果Timeout 是 20 秒，但是 UnreachableDelay 是 30 秒, 下一次检查在 50 秒后 。 :::  **UnreachablePeriod**参数定义了不可达的总时长。 UnreachablePeriod 应该比 UnreachableDelay大几倍, 这样在主机变为不可用之前，主机会被检查不止一次。  如果不可达主机再次出现，监控自动恢复正常:  恢复 Zabbix agent 对主机 "New host"的检查: 连接恢复

en-us	#### Unsupported items  An item can become unsupported if its value cannot be retrieved for some reason. Such items are still rechecked at their standard *[Update interval](/manual/config/items/item?#configuration)*.  Unsupported items are reported as having a NOT SUPPORTED state.
zh-cn	#### 不支持的监控项  如果由于某种原因无法检索到值，则该监控项会变为不受支持的。但是该监控项仍会以设定的*[更新间隔](/manual/config/items/item?#configuration)*重新检索。  不支持的监控项会被报告为“不支持（NOT SUPPORTED）”状态。

en-us	#### Upgrade procedure
zh-cn	#### 升级程序

en-us	#### Upgrade procedure
zh-cn	#### 升级过程

en-us	#### Usage example  Executing the script **check\_oracle.sh** with the first parameters '-h'. The second parameter will be replaced by IP address or DNS name, depending on the selection in the host properties.      check_oracle.sh["-h","{HOST.CONN}"]  Assuming host is configured to use IP address, Zabbix will execute:      check_oracle.sh '-h' '192.168.1.4'
zh-cn	#### 用法示例  使用第一个参数执行脚本 **check\_oracle.sh** '-h'。第二个参数将替换为 IP 地址或 DNS 名称， 取决于主机属性中的选择。      check_oracle.sh["-h","{HOST.CONN}"]  假设主机配置为使用 IP 地址，Zabbix 将执行：      check_oracle.sh '-h' '192.168.1.4'

en-us	#### Usage examples
zh-cn	#### 用法示例

en-us	#### Usage examples  Examples of keys for aggregate calculations.
zh-cn	#### 使用示例  用于聚合计算的键的示例

en-us	#### Use cases
zh-cn	#### 用例

en-us	#### Use cases
zh-cn	#### 用例

en-us	### Use cases  Some use cases for recovery operations are as follows:  1.  Notify on a recovery all users that were notified on the problem:     -  Select *Notify all involved* as operation type.  2.  Have multiple operations upon recovery: send a notification and execute a remote command:     -  Add operation types for sending a message and executing a command.  3.  Open a ticket in external helpdesk/ticketing system and close it when the problem is resolved:     -  Create an external script that communicates with the helpdesk system.     -  Create an action having operation that executes this script and thus opens a ticket.     -  Have a recovery operation that executes this script with other parameters and closes the ticket.     -  Use the {EVENT.ID} macro to reference the original problem.
zh-cn	### 用例  恢复操作的一些用例如下：  1.   通知所有收到问题通知的用户恢复：    -  选择*通知所有相关人员*作为操作类型。  2.   恢复后有多个操作：发送通知和执行远程命令：    -  添加发送消息和执行命令的操作类型。  3.   在外部帮助台/工单系统中打开一个工单，并在问题解决后将其关闭：    -  创建一个与服务台系统通信的外部脚本。    -  创建一个具有执行此脚本并因此打开工单的操作的动作。    -  进行恢复操作，使用其他参数执行此脚本并关闭票证。    -  使用 {EVENT.ID} 宏来引用原始问题。

en-us	#### Use cases  User macros with context can be defined to accomplish more flexible thresholds in trigger expressions (based on the values retrieved by low-level discovery). For example, you may define the following macros:  -   {$LOW\_SPACE\_LIMIT} = 10 -   {$LOW\_SPACE\_LIMIT:/home} = 20 -   {$LOW\_SPACE\_LIMIT:regex:"\^\\/\[a-z\]+$"} = 30  Then a low-level discovery macro may be used as macro context in a trigger prototype for mounted file system discovery:      last(/host/vfs.fs.size[{#FSNAME},pfree])<{$LOW_SPACE_LIMIT:"{#FSNAME}"}  After the discovery different low-space thresholds will apply in triggers depending on the discovered mount points or file system types. Problem events will be generated if:  -   /home folder has less than 20% of free disk space -   folders that match the regexp pattern (like /etc, /tmp or /var) have     less than 30% of free disk space -   folders that don't match the regexp pattern and are not /home have     less than 10% of free disk space
zh-cn	####  用例  可以定义具有上下文的用户宏以实现更灵活触发器表达式中的阈值（基于检索到的值低级发现）。例如，您可以定义以下宏：  - {$LOW\_SPACE\_LIMIT} = 10 - {$LOW\_SPACE\_LIMIT:/home} = 20 - {$LOW\_SPACE\_LIMIT:正则表达式:"\^\\/\[a-z\]+$"} = 30  然后一个低级发现宏可以用作宏上下文已挂载文件系统发现的触发器原型：   · last(/host/vfs.fs.size[{#FSNAME},pfree])<{$LOW_SPACE_LIMIT:"{#FSNAME}"}  发现后将应用不同的低空间阈值根据发现的挂载点或文件系统类型触发。如果出现以下情况，将生成问题事件：  - /home 文件夹的可用磁盘空间不足 20% - 匹配正则表达式模式的文件夹（如 /etc、/tmp 或 /var）具有不到 30% 的可用磁盘空间 - 与正则表达式模式不匹配且不是 /home 的文件夹有不到 10% 的可用磁盘空间

en-us	# user.checkAuthentication
zh-cn	# 检查认证

en-us	# user.create
zh-cn	# 创建用户

en-us	# user.delete
zh-cn	# 删除用户

en-us	# user.get
zh-cn	# 查询用户

en-us	# usergroup.create
zh-cn	# 创建用户组

en-us	# usergroup.delete
zh-cn	# 删除用户组

en-us	# usergroup.get
zh-cn	# 查询用户组

en-us	# > User group object  The following objects are directly related to the `usergroup` API.
zh-cn	# > 用户组对象  以下对象与`usergroup` 接口相关.

en-us	# User group  This class is designed to work with user groups.  Object references:\  -   [User group](/manual/api/reference/usergroup/object#user_group)  Available methods:\  -   [usergroup.create](/manual/api/reference/usergroup/create) -     creating new user groups -   [usergroup.delete](/manual/api/reference/usergroup/delete) -     deleting user groups -   [usergroup.get](/manual/api/reference/usergroup/get) - retrieving     user groups -   [usergroup.update](/manual/api/reference/usergroup/update) -     updating user groups
zh-cn	# 用户组  这个类用于操作用户组.  对象引用:\  -   [用户组](/manual/api/reference/usergroup/object#user_group)  可用方法:\  -   [usergroup.create](/manual/api/reference/usergroup/create) - 创建新用户组 -   [usergroup.delete](/manual/api/reference/usergroup/delete) - 删除用户组 -   [usergroup.get](/manual/api/reference/usergroup/get) - 查询用户组 -   [usergroup.update](/manual/api/reference/usergroup/update) - 更新用户组

en-us	# usergroup.update
zh-cn	# 更新用户组

en-us	# user.login
zh-cn	# 登录用户

en-us	# user.logout
zh-cn	# 注销用户

en-us	#### User macro context  See [user macros with context](/manual/config/macros/user_macros_context).
zh-cn	#### 用户宏上下文  请参阅 [用户宏上下文](/manual/config/macros/user_macros_context)。

en-us	# usermacro.create
zh-cn	# 创建用户宏

en-us	# usermacro.createglobal
zh-cn	# 创建全局宏

en-us	# usermacro.delete
zh-cn	# 删除主机宏

en-us	# usermacro.deleteglobal
zh-cn	# 删除全局宏

en-us	# usermacro.get
zh-cn	# 查询用户宏

en-us	# > User macro object  The following objects are directly related to the `usermacro` API.
zh-cn	# > 用户宏对象  以下对象均与 `usermacro` 接口相关 .

en-us	# usermacro.update
zh-cn	# 更新主机宏

en-us	# usermacro.updateglobal
zh-cn	# 更新全局宏

en-us	# > User object  The following objects are directly related to the `user` API.
zh-cn	# > 用户对象  以下对象都是与 `user` 相关的API.

en-us	#### Users of Zabbix  Many organizations of different size around the world rely on Zabbix as a primary monitoring platform.
zh-cn	#### Zabbix 用户  世界各地许多不同规模的组织都依赖 Zabbix 作为主要监控平台。

en-us	# User  This class is designed to work with users.  Object references:\  -   [User](/manual/api/reference/user/object#user)  Available methods:\  -   [user.checkauthentication](/manual/api/reference/user/checkauthentication) -     checking and prolonging user sessions -   [user.create](/manual/api/reference/user/create) - creating new     users -   [user.delete](/manual/api/reference/user/delete) - deleting users -   [user.get](/manual/api/reference/user/get) - retrieving users -   [user.login](/manual/api/reference/user/login) - logging in to the     API -   [user.logout](/manual/api/reference/user/logout) - logging out of     the API -   [user.unblock](/manual/api/reference/user/unblock) - unblocking     users -   [user.update](/manual/api/reference/user/update) - updating users
zh-cn	# 用户  这个类用于操作用户.  对象属性:\  -   [用户](/manual/api/reference/user/object#user)  可用方法:\  -   [user.checkauthentication](/manual/api/reference/user/checkauthentication) - 检查并延长用户会话 -   [user.create](/manual/api/reference/user/create) - 创建用户 -   [user.delete](/manual/api/reference/user/delete) - 删除用户 -   [user.get](/manual/api/reference/user/get) - 查询用户 -   [user.login](/manual/api/reference/user/login) - 登录用户 -   [user.logout](/manual/api/reference/user/logout) - 注销用户 -   [user.unblock](/manual/api/reference/user/unblock) - 解锁用户 -   [user.update](/manual/api/reference/user/update) - 更新用户

en-us	# user.unblock
zh-cn	# 解锁用户

en-us	# user.update
zh-cn	# 更新用户

en-us	##### Using a custom tile service provider  The Geomap widget is capable to load raster tile images from a custom self-hosted or a third-party tile provider service. To use a custom third-party tile provider service or a self-hosted tile folder or server, select *Other* in the *Tile provider* field and specify the custom URL in the *Tile URL* field using proper placeholders.
zh-cn	##### 使用自定义瓦片服务提供者  Geomap 小部件能够从自定义的自托管或第三方切片提供商服务加载光栅切片图像。 要使用自定义第三方切片提供商服务或自托管切片文件夹或服务器，请在 *Tile provider* 字段中选择 *Other*，并在 *Tile URL* 字段中使用适当的占位符指定自定义 URL。

en-us	#### Using custom MIB files  There are standard MIB files coming with every GNU/Linux distribution. But some device vendors provide their own.  Let's say, you would like to use [CISCO-SMI](ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my) MIB file. The following instructions will download and install it:      # wget ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my -P /tmp     # mkdir -p /usr/local/share/snmp/mibs     # grep -q '^mibdirs +/usr/local/share/snmp/mibs' /etc/snmp/snmp.conf 2>/dev/null || echo "mibdirs +/usr/local/share/snmp/mibs" >> /etc/snmp/snmp.conf     # cp /tmp/CISCO-SMI.my /usr/local/share/snmp/mibs  Now you should be able to use it. Try to translate the name of the object *ciscoProducts* from the MIB file to OID:      # snmptranslate -IR -On CISCO-SMI::ciscoProducts     .1.3.6.1.4.1.9.1  If you receive errors instead of the OID, ensure all the previous commands did not return any errors.  The object name translation worked, you are ready to use custom MIB file. Note the MIB name prefix (*CISCO-SMI::*) used in the query. You will need this when using command-line tools as well as Zabbix.  Don't forget to restart Zabbix server/proxy before using this MIB file in Zabbix.  ::: noteimportant Keep in mind that MIB files can have dependencies. That is, one MIB may require another. In order to satisfy these dependencies you have to install all the affected MIB files. :::
zh-cn	#### 使用自定义 MIB 文件  每个 GNU/Linux 发行版都有标准的 MIB 文件。 但是一些设备供应商提供他们自己的。  假设您想使用[CISCO-SMI](ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my) MIB 文件。这 以下说明将下载并安装它：      # wget ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SMI.my -P /tmp     # mkdir -p /usr/local/share/snmp/mibs     # grep -q '^mibdirs +/usr/local/share/snmp/mibs' /etc/snmp/snmp.conf 2>/dev/null || echo "mibdirs +/usr/local/share/snmp/mibs" >> /etc/snmp/snmp.conf     # cp /tmp/CISCO-SMI.my /usr/local/share/snmp/mibs  现在你应该可以使用它了。试着翻译一下名字 对象 *ciscoProducts* 从 MIB 文件到 OID：      # snmptranslate -IR -On CISCO-SMI::ciscoProducts     .1.3.6.1.4.1.9.1  如果您收到错误而不是 OID，请确保之前的所有命令没有返回任何错误。  对象名称翻译成功，您可以使用自定义 MIB文件。请注意查询中使用的 MIB 名称前缀 (*CISCO-SMI::*)。你在使用命令行工具以及 Zabbix 时将需要这个。  Zabbix使用这个 MIB 文件之前不要忘记重启 Zabbix server/proxy服务。  ::: noteimportant 请记住，MIB 文件可以具有依赖关系。 也就是说，一个 MIB 可能需要另一个 MIB。为了满足这些您必须安装所有受影响的 MIB 的依赖项文件。 :::

en-us	#### Using db.odbc.discovery  As a practical example to illustrate how the SQL query is transformed into JSON, let us consider low-level discovery of Zabbix proxies by performing an ODBC query on Zabbix database. This is useful for automatic creation of "zabbix\[proxy,<name>,lastaccess\]" [internal items](/manual/config/items/itemtypes/internal) to monitor which proxies are alive.  Let us start with discovery rule configuration:  ![lld\_rule\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_odbc.png)  All mandatory input fields are marked with a red asterisk.  Here, the following direct query on Zabbix database is used to select all Zabbix proxies, together with the number of hosts they are monitoring. The number of hosts can be used, for instance, to filter out empty proxies:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  By the internal workings of "db.odbc.discovery\[,{$DSN}\]" item, the result of this query gets automatically transformed into the following JSON:  ``` {.java} [     {         "{#HOST}": "Japan 1",         "{#COUNT}": "5"     },     {         "{#HOST}": "Japan 2",         "{#COUNT}": "12"     },     {         "{#HOST}": "Latvia",         "{#COUNT}": "3"     } ] ```  It can be seen that column names become macro names and selected rows become the values of these macros.  ::: noteclassic  If it is not obvious how a column name would be transformed into a macro name, it is suggested to use column aliases like "COUNT(h2.host) AS count" in the example above.  In case a column name cannot be converted into a valid macro name, the discovery rule becomes not supported, with the error message detailing the offending column number. If additional help is desired, the obtained column names are provided under DebugLevel=4 in Zabbix server log file:      $ grep db.odbc.discovery /tmp/zabbix_server.log      ...      23876:20150114:153410.856 In db_odbc_discovery() query:'SELECT h1.host, COUNT(h2.host) FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;'      23876:20150114:153410.860 db_odbc_discovery() column[1]:'host'      23876:20150114:153410.860 db_odbc_discovery() column[2]:'COUNT(h2.host)'      23876:20150114:153410.860 End of db_odbc_discovery():NOTSUPPORTED      23876:20150114:153410.860 Item [Zabbix server:db.odbc.discovery[proxies,{$DSN}]] error: Cannot convert column #2 name to macro.   :::  Now that we understand how a SQL query is transformed into a JSON object, we can use {\#HOST} macro in item prototypes:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)  Once discovery is performed, an item will be created for each proxy:  ![discovered\_items\_odbc1.png](../../../../../assets/en/manual/discovery/low_level_discovery/discovered_items_odbc1.png)
zh-cn	#### 使用db.odbc.discovery  让我们看一个SQL查询转换为JSON数组的真实案例。思考一下如何在Zabbix数据库上使用ODBC查询对Zabbix proxy执行低级别自动发现。 此功能对于自动创建 "zabbix\[proxy,<name>,lastaccess\]" [内部监控项](/manual/config/items/itemtypes/internal) 并监控存活的proxy很有用。  下面开始配置自动发现规则：  ![lld\_rule\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/lld_rule_odbc.png)  所有强制输入区域均标记为红色星号。  此处Zabbix数据库上的查询用于查询所有Zabbix proxy，连同proxy所监控的主机数量. 比如，主机数量可用于过滤掉没有监控任何主机的proxy：      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  通过 "db.odbc.discovery\[,{$DSN}\]" 监控项的内部工作机制, 查询结果会自动转换为下面的JSON数组：  ``` {.java} [     {         "{#HOST}": "Japan 1",         "{#COUNT}": "5"     },     {         "{#HOST}": "Japan 2",         "{#COUNT}": "12"     },     {         "{#HOST}": "Latvia",         "{#COUNT}": "3"     } ] ```  可以看到字段名称变为宏的名称, 所选的记录变成这些宏的值。  ::: noteclassic  如果通过这种方式展示字段名称转换为宏名称不是很明显，那建议在上面的例子中使用字段别名，比如 "COUNT(h2.host) AS count"。  如果字段名称无法转换为有效的宏名称，则自动发现规则变为unsupport(不支持的)状态，其错误消息显示不合规字段的编号. 如果需要额外帮助, debug级别DebugLevel=4的Zabbix server日志文件中可找到获取的字段名称：      $ grep db.odbc.discovery /tmp/zabbix_server.log      ...      23876:20150114:153410.856 In db_odbc_discovery() query:'SELECT h1.host, COUNT(h2.host) FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;'      23876:20150114:153410.860 db_odbc_discovery() column[1]:'host'      23876:20150114:153410.860 db_odbc_discovery() column[2]:'COUNT(h2.host)'      23876:20150114:153410.860 End of db_odbc_discovery():NOTSUPPORTED      23876:20150114:153410.860 Item [Zabbix server:db.odbc.discovery[proxies,{$DSN}]] error: Cannot convert column #2 name to macro.   :::  现在理解了SQL查询如何转换成一个JSON对象后, 可以在监控项原型中使用 {\#HOST} 宏了：  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)  一旦自动发现开始执行, 会根据每个proxy创建一个对应的监控项：  ![discovered\_items\_odbc1.png](../../../../../assets/en/manual/discovery/low_level_discovery/discovered_items_odbc1.png)

en-us	#### Using db.odbc.get  Using `db.odbc.get[,{$DSN}]` and the following SQL example:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  this JSON will be returned:  ``` {.java} [     {         "host": "Japan 1",         "count": "5"     },     {         "host": "Japan 2",         "count": "12"     },     {         "host": "Latvia",         "count": "3"     } ] ```  As you can see, there are no low-level discovery macros there. However, custom low-level discovery macros can be created in the [LLD macros](/manual/discovery/low_level_discovery#custom_macros) tab of a discovery rule using JSONPath, for example:      {#HOST} → $.host  Now this {\#HOST} macro may be used in item prototypes:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)
zh-cn	#### 使用db.odbc.get  请看下面使用 `db.odbc.get[,{$DSN}]` 和相关SQL语句的例子:      mysql> SELECT h1.host, COUNT(h2.host) AS count FROM hosts h1 LEFT JOIN hosts h2 ON h1.hostid = h2.proxy_hostid WHERE h1.status IN (5, 6) GROUP BY h1.host;     +---------+-------+     | host    | count |     +---------+-------+     | Japan 1 |     5 |     | Japan 2 |    12 |     | Latvia  |     3 |     +---------+-------+     3 rows in set (0.01 sec)  会返回这个JSON数组:  ``` {.java} [     {         "host": "Japan 1",         "count": "5"     },     {         "host": "Japan 2",         "count": "12"     },     {         "host": "Latvia",         "count": "3"     } ] ```  可以看到, 返回的JSON数组中不包含低级别自动发现的宏. 然而, 可以在自动发现规则的[LLD 宏](/manual/discovery/low_level_discovery#custom_macros) 选项卡中利用JSONPath来自定义宏, 比如:      {#HOST} → $.host  现在这个 {\#HOST} 宏可用在监控项原型中了:  ![item\_prototype\_odbc.png](../../../../../assets/en/manual/discovery/low_level_discovery/item_prototype_odbc.png)

en-us	#### Using DNS as default interface  HostInterface and HostInterfaceItem [configuration parameters](/manual/appendix/config/zabbix_agentd) allow to specify a custom value for the host interface during autoregistration.  More specifically, they are useful if the host should be autoregistered with a DNS name as the default agent interface rather than its IP address. In that case the DNS name should be specified or returned as the value of either HostInterface or HostInterfaceItem parameters. Note that if the value of one of the two parameters changes, the autoregistered host interface is updated. So it is possible to update the default interface to another DNS name or update it to an IP address. For the changes to take effect though, the agent has to be restarted.  ::: noteclassic If HostInterface or HostInterfaceItem parameters are not configured, the listen\_dns parameter is resolved from the IP address. If such resolving is configured incorrectly, it may break autoregistration because of invalid hostname. :::
zh-cn	#### 使用DNS作为默认接口  在自动注册过程中，主机接口(HostInterface)和主机接口监控项(HostInterfaceItem) [配置参数](/manual/appendix/config/zabbix_agentd)的值允许自定义。   具体来说，如果主机使用DNS名称而不是IP地址作为默认agent接口进行自动注册时，对参数的值进行自定义就发挥作用了。这种情况下，DNS名称应通过HostInterface或HostInterfaceItem参数进行设置。 注意，如果上述参数的值发生改变，自动注册的主机接口也会更新。所以可以通过更换DNS名称来更新默认接口，或给DNS名称改成IP地址来更新接口。 Zabbix agent需要重启来使变更生效。 ::: noteclassic 如果不配置HostInterface和HostInterfaceItem这两个参数，那么listen\_dns参数会从IP地址来解析。如果解析配置错误，可能会因为主机名称无效导致自动注册失败。 :::

en-us	##### Using filter  The page shows a list of all web scenarios of the selected host. To view web scenarios for another host or host group without returning to the *Monitoring → Hosts* page, select that host or group in the filter. You may also filter scenarios based on tags.
zh-cn	##### 使用过滤器   该页显示所选主机的所有 Web 监测的列表。若要查看其他主机或主机组的 Web 监测而不返回到 *监测  → 主机*  页面，请在筛选器中选择该主机或组。你还可以根据标签筛选方案。

en-us	##### Using filter  You can use the filter to display only the actions you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of actions. If you click on it, a filter becomes available where you can filter actions by name and status.  ![](../../../../../assets/en/manual/web_interface/action_filter.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用筛选器只显示您感兴趣的动作。为了获得更好的搜索性能，在搜索数据时不解析宏。  *过滤器*链接可以在动作列表的上方找到。如果单击它，就会出现一个过滤器，您可以根据名称和状态过滤动作。  ![](../../../../../assets/en/manual/web_interface/action_filter.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the discovery rules you are interested in. For better search performance, data is searched with macros unresolved.  With nothing selected in the filter, all enabled discovery rules are displayed. To select a specific discovery rule for display, start typing its name in the filter. All matching enabled discovery rules will be listed for selection. More than one discovery rule can be selected.
zh-cn	##### 使用过滤器  可以使用筛选器显示感兴趣的发现规则。为了获得更好的搜索性能，使用未解析的宏搜索数据。如果在筛选器中未选择任何内容，则会显示所有已启用的 发现规则。  若要选择要显示的特定发现规则， 请开始在筛选器中键入其名称。将列出所有匹配的已启用发现规则以供选择。 可以选择多个发现规则。

en-us	##### Using filter  You can use the filter to display only the host groups you are interested in. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  你可以通过使用过滤器仅仅展示你感兴趣的主机组。为了更好的搜索性能，搜索数据的时候不会解析宏

en-us	##### Using filter  You can use the filter to display only the maps you are interested in. For better search performance, data is searched with macros unresolved.
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的地图。为了获得更好的搜索性能，使用未解析的宏搜索数据。

en-us	##### Using filter  You can use the filter to display only the media types you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of media types. If you click on it, a filter becomes available where you can filter media types by name and status.  ![](../../../../../assets/en/manual/web_interface/media_types_filter1.png){width="600"}
zh-cn	##### 使用过滤器  可以使用过滤器仅显示您感兴趣的媒介类型。为了获得更好的搜索性能，搜索数据时未解析宏。  *过滤器* 链接位于媒介类型列表上方。 如果单击它，则会出现一个过滤器，可以按名称和状态过滤媒介类型。  ![](../../../../../assets/en/manual/web_interface/media_types_filter1.png){width="600"}

en-us	##### Using filter  You can use the filter to display only the user groups you are interested in. For better search performance, data is searched with macros unresolved.  The *Filter* link is available above the list of user groups. If you click on it, a filter becomes available where you can filter user groups by name and status.  ![](../../../../../assets/en/manual/web_interface/user_groups_filter1.png){width="600"}
zh-cn	##### 使用过滤器  您可以使用过滤器仅显示您感兴趣的用户组。为了获得更好的搜索性能，使用未解析的宏搜索数据。  *过滤器* 链接位于用户组列表上方。如果单击它，将出现一个过滤器，您可以在其中按名称和状态过滤用户组。  ![](../../../../../assets/en/manual/web_interface/user_groups_filter1.png){width="600"}

en-us	#### Using jmx.discovery  This item returns a JSON object with low-level discovery macros describing MBean objects or attributes. For example, in the discovery of MBean attributes (reformatted for clarity):  ``` {.javascript} [     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionCount",         "{#JMXATTR}":"CollectionCount"     },     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionTime",         "{#JMXATTR}":"CollectionTime"     },     {         "{#JMXVALUE}":"true",         "{#JMXTYPE}":"java.lang.Boolean",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Valid",         "{#JMXATTR}":"Valid"     },     {         "{#JMXVALUE}":"PS Scavenge",         "{#JMXTYPE}":"java.lang.String",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Name",         "{#JMXATTR}":"Name"     },     {         "{#JMXVALUE}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXTYPE}":"javax.management.ObjectName",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,ObjectName",         "{#JMXATTR}":"ObjectName"     } ] ```  In the discovery of MBeans (reformatted for clarity):  ``` {.javascript} [     {         "{#JMXDOMAIN}":"java.lang",         "{#JMXTYPE}":"GarbageCollector",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXNAME}":"PS Scavenge"     } ]  ```
zh-cn	#### 使用jmx.discovery  此监控项返回一个JSON对象，其中包含低级别自动发现的宏，用于描述MBean对象或对象的属性，比如MBean属性的自动发现(为了清晰重新排版):  ``` {.javascript} [     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionCount",         "{#JMXATTR}":"CollectionCount"     },     {         "{#JMXVALUE}":"0",         "{#JMXTYPE}":"java.lang.Long",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,CollectionTime",         "{#JMXATTR}":"CollectionTime"     },     {         "{#JMXVALUE}":"true",         "{#JMXTYPE}":"java.lang.Boolean",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Valid",         "{#JMXATTR}":"Valid"     },     {         "{#JMXVALUE}":"PS Scavenge",         "{#JMXTYPE}":"java.lang.String",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,Name",         "{#JMXATTR}":"Name"     },     {         "{#JMXVALUE}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXTYPE}":"javax.management.ObjectName",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXDESC}":"java.lang:type=GarbageCollector,name=PS Scavenge,ObjectName",         "{#JMXATTR}":"ObjectName"     } ] ```  又比如MBean的自动发现 (为了清晰重新排版):  ``` {.javascript} [     {         "{#JMXDOMAIN}":"java.lang",         "{#JMXTYPE}":"GarbageCollector",         "{#JMXOBJ}":"java.lang:type=GarbageCollector,name=PS Scavenge",         "{#JMXNAME}":"PS Scavenge"     } ]  ```

en-us	#### Using LLD macros in user macro contexts  LLD macros may be used inside user macro context, for example, [in trigger prototypes](/manual/config/macros/user_macros_context#use_cases).
zh-cn	 #### 在用户宏的上下文中使用LLD宏  LLD宏可用在用户宏的上下文中，比如 [在触发器原型中](/manual/config/macros/user_macros_context#use_cases)。

en-us	#### Using macro functions  Macro functions are supported with low-level discovery macros (except in low-level discovery rule filter), allowing to extract a certain part of the macro value using a regular expression.  For example, you may want to extract the customer name and interface number from the following LLD macro for the purposes of event tagging:      {#IFALIAS}=customername_1  To do so, the `regsub` macro function can be used with the macro in the event tag value field of a trigger prototype:  ![](../../../../assets/en/manual/config/macros/lld_macro_function.png)  Note, that commas are not allowed in unquoted item [key parameters](/manual/config/items/item/key#key_parameters), so the parameter containing a macro function has to be quoted. The backslash (`\`) character should be used to escape double quotes inside the parameter. Example:      net.if.in["{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}",bytes]  For more information on macro function syntax, see: [Macro functions](/manual/config/macros/macro_functions)  Macro functions are supported in low-level discovery macros since Zabbix 4.0.
zh-cn	#### 使用宏函数  低级发现宏支持宏功能（在低级发现规则过滤器），允许提取某个部分使用正则表达式的宏值。  例如，您可能想要提取客户名称和接口用于事件标记的以下 LLD 宏中的编号：  · {#IFALIAS}=customername_1  为此，可以将 `regsub` 宏函数与触发器原型的事件标签值字段：  ![](../../../../assets/en/manual/config/macros/lld_macro_function.png)  请注意，未引用的项目中不允许使用逗号 [key参数](/manual/config/items/item/key#key_parameters)，所以必须引用包含宏函数的参数。反斜杠(`\`) 字符应用于转义范围。例子：      net.if.in["{{#IFALIAS}.regsub(\"(.*)_([0-9]+)\", \1)}",bytes]  有关宏函数语法的更多信息，请参阅：[宏函数](/manual/config/macros/macro_functions)  自 Zabbix 以来，低级发现宏支持宏功能4.0。

en-us	#### Using maxdelay parameter  The 'maxdelay' parameter in log items allows ignoring some older lines from log files in order to get the most recent lines analyzed within the 'maxdelay' seconds.  ::: notewarning Specifying 'maxdelay' > 0 may lead to **ignoring important log file records and missed alerts**. Use it carefully at your own risk only when necessary. :::  By default items for log monitoring follow all new lines appearing in the log files. However, there are applications which in some situations start writing an enormous number of messages in their log files. For example, if a database or a DNS server is unavailable, such applications flood log files with thousands of nearly identical error messages until normal operation is restored. By default, all those messages will be dutifully analyzed and matching lines sent to server as configured in `log` and `logrt` items.  Built-in protection against overload consists of a configurable 'maxlines' parameter (protects server from too many incoming matching log lines) and a 10\*'maxlines' limit (protects host CPU and I/O from overloading by agent in one check). Still, there are 2 problems with the built-in protection. First, a large number of potentially not-so-informative messages are reported to server and consume space in the database. Second, due to the limited number of lines analyzed per second the agent may lag behind the newest log records for hours. Quite likely, you might prefer to be sooner informed about the current situation in the log files instead of crawling through old records for hours.  The solution to both problems is using the 'maxdelay' parameter. If 'maxdelay' > 0 is specified, during each check the number of processed bytes, the number of remaining bytes and processing time is measured. From these numbers the agent calculates an estimated delay - how many seconds it would take to analyze all remaining records in a log file.  If the delay does not exceed 'maxdelay' then the agent proceeds with analyzing the log file as usual.  If the delay is greater than 'maxdelay' then the agent **ignores a chunk of a log file by "jumping" over it** to a new estimated position so that the remaining lines could be analyzed within 'maxdelay' seconds.  Note that agent does not even read ignored lines into buffer, but calculates an approximate position to jump to in a file.  The fact of skipping log file lines is logged in the agent log file like this:      14287:20160602:174344.206 item:"logrt["/home/zabbix32/test[0-9].log",ERROR,,1000,,,120.0]"     logfile:"/home/zabbix32/test1.log" skipping 679858 bytes     (from byte 75653115 to byte 76332973) to meet maxdelay  The "to byte" number is approximate because after the "jump" the agent adjusts the position in the file to the beginning of a log line which may be further in the file or earlier.  Depending on how the speed of growing compares with the speed of analyzing the log file you may see no "jumps", rare or often "jumps", large or small "jumps", or even a small "jump" in every check. Fluctuations in the system load and network latency also affect the calculation of delay and hence, "jumping" ahead to keep up with the "maxdelay" parameter.  Setting 'maxdelay' < 'update interval' is not recommended (it may result in frequent small "jumps").
zh-cn	#### 使用maxdelay参数  日志监控项中的“maxdelay”参数允许忽略日志文件中的一些较旧的行，以便在“maxdelay”秒内获取最近分析的行。  ::: notewarning 指定'maxdelay'>0可能导致**忽略重要的日志文件记录和错过的报警**，只有在必要时才使用否则后果自负。 :::  默认情况下，日志监控项将跟踪出现在日志文件中的所有新行。 但是，有些应用程序在某些情况下开始在其日志文件中写入大量的消息。例如，如果数据库或DNS服务器不可用，则此类应用程序会向日志文件中注入数千条几乎相同错误消息，直到恢复正常为止。默认情况下，所有这些消息将被完全分析，并将匹配的行发送到配置为`log` 和`logrt`监控项的服务器上。  内置的过载保护包括一个可配置的“maxlines”参数（保护服务器免受过多传入匹配日志行的影响）和 10\*“maxlines”限制（保护主机 CPU 和 I/O 免于agent在一次检查中过载） . 尽管如此，内置保护仍存在两个问题。 首先，大量可能不那么有用的消息被报告给服务器并占用数据库空间。 其次，由于每秒分析的行数有限，agent可能会落后于最新的日志记录数小时。 很可能，您可能更愿意尽快了解日志文件中的当前情况，而不是花几个小时在旧记录中爬行。  这两个问题的解决方案是使用“maxdelay”参数。 如果指定 'maxdelay' > 0，则在每次检查处理的字节数时，测量剩余字节数和处理时间。 agent根据这些数字计算估计的延迟——分析日志文件中所有剩余记录需要多少秒。  如果延迟不超过“maxdelay”，那么agent将像往常一样继续分析日志文件。  如果延迟大于“maxdelay”，那么agent将**通过“跳转”到一个新的估计位置来忽略日志文件的一个块**，以便在“maxdelay”秒内分析剩下的行。  请注意，agent甚至不会将忽略的行读入缓冲区，而是计算要在文件中跳转的大致位置。  跳过日志文件行的事实记录在代理日志文件中，如下所示：      14287:20160602:174344.206 item:"logrt["/home/zabbix32/test[0-9].log",ERROR,,1000,,,120.0]"     logfile:"/home/zabbix32/test1.log" skipping 679858 bytes     (from byte 75653115 to byte 76332973) to meet maxdelay  “to byte”数字是近似的，因为在“跳转”之后，agent将文件中的位置调整到日志行开头，日志行可能在文件中更远或更早。  根据增长速度与分析日志文件的速度的不同，你可能会看到没有"跳转"、少有或经常"跳转"、大或小的"跳转"，甚至每次检查中的"跳转"都很小。系统负载和网络延迟的波动也会影响延迟的计算，因此"跳转"可以跟上“maxdelay”参数。  不推荐设置 'maxdelay' <'update interval'（这可能会导致频繁的"jumps"）

en-us	#### Using subfilter  The subfilter is useful for a quick one-click access to related graphs.  The subfilter operates autonomously from the main filter - results are filtered  immediately, no need to click on *Apply* in the main filter.  Note that the subfilter only allows to further modify the filtering from the main filter.   Unlike the main filter, the subfilter is updated together with each table refresh request  to always get up-to-date information of available filtering options and their counter  numbers.  The subfilter shows **clickable links** allowing to filter graphs based on a common  entity - the tag name or tag value. As soon as the entity is clicked, graphs are  immediately filtered; the selected entity is highlighted with gray background.  To remove the filtering, click on the entity again. To add another  entity to the filtered results, click on another entity.  The number of entities displayed is limited to 100 horizontally. If there are more,  a three-dot icon is displayed at the end; it is not clickable. Vertical lists  (such as tags with their values) are limited to 20 entries. If there are more,  a three-dot icon is displayed; it is not clickable.  A number next to each clickable entity indicates the number of graphs it has in the  results of the main filter.  Once one entity is selected, the numbers with other available entities are displayed  with a plus sign indicating how many graphs may be added to the current selection.
zh-cn	#### 使用子筛选器  子筛选器可用于快速一键访问相关图形。子过滤器从主过滤器自主运行- 结果立即过滤， 无需单击主过滤器中的 *应用* 。  请注意，子筛选器仅允许从主筛选器进一步修改筛选。   与主筛选器不同，子筛选器与每个表 刷新请求一起更新，以始终获取可用筛选选项及其计数器 编号的最新信息。  子筛选器显示 **可单击的链接** 允许根据公共实体（标记名称或标记值）筛选图形。一旦单击实体，图形就会立即被过滤；所选图元将以灰色背景突出显示。若要删除筛选，请再次单击该实体。若要将其他实体添加到筛选结果中，请单击另一个实体。  水平方向显示的实体数限制为 100 个。如果还有更多，则在末尾显示一个三点图标；它是可点击的。垂直列表  （比如带值的标签）限制为 20 个。如果有更多，将显示一个三点图标：它是可点击的。  每个可单击实体旁边的数字表示它在主筛选器结果中的图形数。  选择一个图元后，将显示具有其他可用图元的数字，并带有加号，指示可以添加到当前选定内容中的图形数。

en-us	#### Using Zabbix frontend behind proxy  If Zabbix frontend runs behind proxy server, the cookie path in the proxy configuration file needs to be rewritten in order to match the reverse-proxied path. See examples below. If the cookie path is not rewritten, users may experience authorization issues, when trying to login to Zabbix frontend.
zh-cn	####  在代理后面使用 Zabbix 前端  如果 Zabbix 前端在代理服务器后面运行，则需要重写代理配置文件中的 cookie 路径以匹配反向代理路径。请参阅下面的示例。如果不重写 cookie 路径，用户在尝试登录 Zabbix 前端时可能会遇到授权问题。

en-us	# valuemap.create
zh-cn	# 创建

en-us	# valuemap.delete
zh-cn	# 删除

en-us	# valuemap.get
zh-cn	# 获取

en-us	# > Value map object  The following objects are directly related to the `valuemap` API.
zh-cn	# > 值映射对象  以下对象都是与valuemap直接相关的API。

en-us	# Value map  This class is designed to work with value maps.  Object references:\  -   [Value map](/manual/api/reference/valuemap/object#value_map)  Available methods:\  -   [valuemap.create](/manual/api/reference/valuemap/create) - creating     new value maps -   [valuemap.delete](/manual/api/reference/valuemap/delete) - deleting     value maps -   [valuemap.get](/manual/api/reference/valuemap/get) - retrieving     value maps -   [valuemap.update](/manual/api/reference/valuemap/update) - updating     value maps
zh-cn	# 值映射  此类用于值映射。  对象引用：  -   [Value map](/manual/api/reference/valuemap/object#值映射)  可用方法：  -   [valuemap.create](/manual/api/reference/valuemap/create) - 创建新的值映射 -   [valuemap.delete](/manual/api/reference/valuemap/delete) - 删除值映射 -   [valuemap.get](/manual/api/reference/valuemap/get) - 获取值映射 -   [valuemap.update](/manual/api/reference/valuemap/update) - 更新值映射

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

en-us	##### Verify agent parameters  Make sure that in the [agent configuration file](/manual/appendix/config/zabbix_agentd):  -   'Hostname' parameter matches the host name in the frontend -   Servers in the 'ServerActive' parameter are specified for the     processing of active checks
zh-cn	##### 验证代理参数  确保在 [代理配置文件](/manual/appendix/config/zabbix_agentd) 中已设置：  -   'Hostname'参数与前端的主机名一致 -   'ServerActive'参数中的服务器被指定用于处理主动检查

en-us	### Verify CA mode
zh-cn	### 验证 CA 模式

en-us	### Verify CA mode  Copy required MySQL CA to the Zabbix frontend server, assign proper permissions to allow the webserver to read this file.  ::: noteclassic  *Verify CA* mode doesn't work on SLES 12 and RHEL 7 due to older MySQL libraries.  :::
zh-cn	### 验证 CA 模式  将所需的MySQL CA复制到Zabbix前端服务器，分配适当的权限以允许Web服务器读取此文件。  ::: noteclassic  *Verify CA* 模式在 SLES 12 and RHEL 7 不会生效，因为所在系统的 MySQL 库过老.  :::

en-us	### Verify full mode
zh-cn	### 完整验证模式

en-us	### Verify Full mode
zh-cn	### 验证完整模式

en-us	#### Viewing host group elements  This option is available if the "Host group elements" show option is chosen. When selecting "Host group elements" as the *show* option, you will at first see only one icon for the host group. However, when you save the map and then go to the map view, you will see that the map includes all the elements (hosts) of the certain host group:  |Map editing view|Map view| |----------------|--------| |![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_conf.png){width="450"}|![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_view.png){width="450"}|  Notice how the {HOST.NAME} macro is used. In map editing, the macro name is unresolved, while in map view all the unique names of the hosts are displayed.
zh-cn	#### 查看主机组元素  如果“主机组元素”显示选项为选择。选择“主机组元素”作为* show *选项时，您起初只会看到主机组的一个图标。然而，当你保存地图，然后转到地图视图，你会看到地图包括特定主机组的所有元素（主机）：  |地图编辑视图|地图视图| |----------------|--------| |![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_conf.png){width="450"}|![](../../../../../assets/en/manual/config/visualization/maps/map_host_group_view.png){width="450"}|  请注意如何使用 {HOST.NAME} 宏。在地图编辑中，宏名称是不解析的，而在查看地图时，所有唯一名称的主机都被显示。

en-us	#### Viewing maps  To view a map, click on its name in the list of all maps.  ![](../../../../../assets/en/manual/web_interface/maps.png){width="600"}  You can use the drop-down in the map title bar to select the lowest severity level of the problem triggers to display. The severity marked as *default* is the level set in the map configuration. If the map contains a sub-map, navigating to the sub-map will retain the higher-level map severity (except if it is *Not classified*, in this case, it will not be passed to the sub-map).
zh-cn	#### 查看拓扑图  要查看某个拓扑图，单击所有拓扑图列表中对应的名称。  ![](../../../../../assets/en/manual/web_interface/maps.png){width="600"}  您可以使用拓扑图标题栏中的下拉列表来选择要显示问题触发器的最低严重性级别。默认严重性是在拓扑图配置中设置的级别。如果拓扑图包含子拓扑图，则导航到子拓扑图将保留上层级别拓扑图严重性。

en-us	##### Web interface  For an easy access to Zabbix from anywhere and from any platform, the web-based interface is provided. The interface is part of Zabbix server, and usually (but not necessarily) runs on the same physical machine as the one running the server.
zh-cn	##### Web 界面  为了从任何地方和任何平台轻松访问，Zabbix 提供了基于 Web 的界面。该接口是 Zabbix server 的一部分，通常（但不一定）与 server 运行在同一台设备上。

en-us	#### Web monitoring  Configure web scenarios to monitor your web applications and services.  [Web scenario API](/manual/api/reference/httptest)
zh-cn	#### Web 监控  配置 Web 场景以监控 Web 应用程序和服务。  [Web scenario API](/manual/api/reference/httptest)

en-us	#### Web scenario  In a [web scenario](/manual/web_monitoring) configuration, user macros can be used in the following fields:  |Location|<|Multiple macros/mix with text^[1](supported_by_location_user#footnotes)^| |-|------------------------------|----------| |Name|<|yes| |Update interval|<|no| |Agent|<|yes| |HTTP proxy|<|yes| |Variables (values only)|<|yes| |Headers (names and values)|<|yes| |*Steps*|<|<| | |Name|yes| |^|URL^[3](supported_by_location_user#footnotes)^|yes| |^|Variables (values only)|yes| |^|Headers (names and values)|yes| |^|Timeout|no| |^|Required string|yes| |^|Required status codes|no| |*Authentication*|<|<| | |User|yes| |^|Password|yes| |^|SSL certificate|yes| |^|SSL key file|yes| |^|SSL key password|yes| |*Tags*^[2](supported_by_location_user#footnotes)^|<|<| | |Tag names|yes| |^|Tag values|yes|
zh-cn	#### Web 场景  在 [web 场景](/manual/web_monitoring)配置中，用户宏可用于以下地方：  |位置|<|多个宏/混合文本^[1](supported_by_location_user#footnotes)^| |--------|-|------------------------------------------------------------------------| |名称|<|支持| |更新间隔|<|不支持| |Agent|<|支持| |HTTP 代理|<|支持| |变量 (只允许值)|<|支持| |请求头部 (名称和值)|<|支持| |*步骤*|<|<| | |名称|支持| |^|URL^[3](supported_by_location_user#footnotes)^|支持| |^|变量 (只允许值)|支持| |^|请求头部 (名称和值)|支持| |^|超时时间|不支持| |^|返回字符串|支持| |^|返回状态码|不支持| |*认证*|<|<| | |用户|支持| |^|密码|支持| |^|SSL 证书|支持| |^|SSL 密钥文件|支持| |^|SSL 密钥密码|支持| |*标签*|<|<| | |标签名称|支持| |^|标签值|支持|

en-us	# > Web scenario object  The following objects are directly related to the `webcheck` API.
zh-cn	 # > Web场景对象  以下对象都是与`webcheck` 直接相关的API。

en-us	# Web scenario  This class is designed to work with web scenarios.  Object references:\  -   [Web scenario](/manual/api/reference/httptest/object#web_scenario) -   [Scenario step](/manual/api/reference/httptest/object#scenario_step)  Available methods:\  -   [httptest.create](/manual/api/reference/httptest/create) - creating     new web scenarios -   [httptest.delete](/manual/api/reference/httptest/delete) - deleting     web scenarios -   [httptest.get](/manual/api/reference/httptest/get) - retrieving web     scenarios -   [httptest.update](/manual/api/reference/httptest/update) - updating     web scenarios
zh-cn	 # Web场景  此类用于Web场景。  对象引用：\  -   [Web scenario](/manual/api/reference/httptest/object#Web场景) -   [Scenario step](/manual/api/reference/httptest/object#场景步骤)  可用方法：\  -   [httptest.create](/manual/api/reference/httptest/create) - 创建新的Web场景 -   [httptest.delete](/manual/api/reference/httptest/delete) - 删除Web场景 -   [httptest.get](/manual/api/reference/httptest/get) - 获取Web场景 -   [httptest.update](/manual/api/reference/httptest/update) - 更新Web场景

en-us	### Web server hardening
zh-cn	### Web 服务器加固

en-us	#### Whitespace  Whitespace (space, tab characters) can be freely used in bracket notation segments and expressions, for example, `$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`.
zh-cn	#### 空格  空格（空格、制表符）可以在括号符号段和表达式中自由使用，例如，`$[ 'a' ][ 0 ][ ?( $.b == 'c' ) ][ : -1 ].first( )`.

en-us	#### Windows-specific item keys  |Item key|User group|<| |--------|----------|-| | |Recommended|Minimum technically acceptable (functionality is limited)| |eventlog|Event Log Readers|Guests| |net.if.list|Guests|Guests| |perf\_counter|Performance Monitor Users|Performance Monitor Users| |proc\_info|Administrators|Guests| |service.discovery|Guests|Guests| |service.info|Guests|Guests| |services|Guests|Guests| |wmi.get|Administrators|Guests| |vm.vmemory.size|Guests|Guests|
zh-cn	 #### Windows特定的监控项键  |监控项 key|用户组|<| |--------|----------|-| | |推荐的|技术上可接受的最低权限组 (功能有限)| |eventlog|Event Log Readers|Guests| |net.if.list|Guests|Guests| |perf\_counter|Performance Monitor Users|Performance Monitor Users| |proc\_info|Administrators|Guests| |service.discovery|Guests|Guests| |service.info|Guests|Guests| |services|Guests|Guests| |wmi.get|Administrators|Guests| |vm.vmemory.size|Guests|Guests|

en-us	#### YAML export/import  There are some known issues with YAML [export/import](/manual/xml_export_import):  -   Error messages are not translatable; -   Valid JSON with a .yaml file extension sometimes cannot be imported; -   Unquoted human-readable dates are automatically converted to Unix     timestamps.
zh-cn	#### YAML 导出/导入  YAML [导出/导入](/manual/xml_export_import) 存在一些已知问题：  -   错误消息不会被翻译； -   有时会无法导入带有 .yaml 文件扩展名的有效 JSON 文件； -   日期如果不加引号会自动转换为 Unix 时间戳。

en-us	#### Zabbix configuration
zh-cn	#### Zabbix 配置

en-us	#### zabbix\_get and zabbix\_sender with encryption  See [zabbix\_get](/manpages/zabbix_get) and [zabbix\_sender](/manpages/zabbix_sender) manpages for using them with encryption.
zh-cn	 #### zabbix\_get and zabbix\_sender与加密  请参阅[zabbix\_get](/manpages/zabbix_get)和[zabbix\_sender](/manpages/zabbix_sender) 操作说明使用加密。

en-us	# Zabbix manpages  These are Zabbix manpages for Zabbix processes.
zh-cn	# Zabbix 手册页  这些是 Zabbix 进程的手册页。

en-us	# Zabbix Manual  Welcome to the user manual for Zabbix software. These pages are created to help users successfully manage their monitoring tasks with Zabbix, from the simple to the more complex ones.
zh-cn	# Zabbix 使用手册  欢迎查阅Zabbix用户使用手册。  Zabbix产品手册由原厂Zabbix技术团队创建、Zabbix中国——上海宏时数据系统有限公司 组织开源社区志愿者翻译并维护。 希望能帮助用户更好地使用Zabbix，解决和管理日常IT运维监控遇到的各种问题。 翻译虽然结束，优化并未停止，如有优化反馈、申请成为译者，欢迎联系小Z 17502189550，market@grandage.cn。

en-us	##### Zabbix packages from OS repositories  Often, OS distributions (in particular, Debian-based distributions) provide their own Zabbix packages.\ Note, that these packages are not supported by Zabbix, they are typically out of date and lack the latest features and bug fixes. Only the packages from [repo.zabbix.com](https://repo.zabbix.com/) are officially supported.  If you are upgrading from packages provided by OS distributions (or had them installed at some point), follow this procedure to switch to official Zabbix packages:  1.  Always uninstall the old packages first. 2.  Check for residual files that may have been left after     deinstallation. 3.  Install official packages following [installation     instructions](https://www.zabbix.com/download) provided by Zabbix.  Never do a direct update, as this may result in a broken installation.
zh-cn	##### 由操作系统存储库中的Zabbix软件包进行升级  通常，发行版本的操作系统（特别是基于 Debian 的发行版）会提供基于自身系统的Zabbix软件包。\ 请注意，Zabbix 不支持这些软件包，它们通常已经过时并且缺乏最新的功能和错误修复。 建议通过由官方支持的 [repo.zabbix.com](https://repo.zabbix.com/) 软件安装包来完成安装。  若需从 OS 发行版提供的软件包进行升级（或在某时已安装），请按照以下步骤换到官方 Zabbix 软件包：  1. 首先，卸载旧版本的安装包。 2. 检查卸载后可能留下的残留文件。 3. 按照Zabbix提供的 [installation instructions](https://www.zabbix.com/download)安装官方包。  切勿进行直接更新，因为这可能会导致安装中断。

en-us	 ### Zabbix Security Advisories and CVE database  See [Zabbix Security Advisories and CVE database](https://www.zabbix.com/security_advisories).
zh-cn	 ### Zabbix 安全公告和 CVE 数据库  请参阅 [Zabbix 安全公告和 CVE 数据库] (https://www.zabbix.com/security_advisories)。

en-us	#### Zabbix sender request  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value"         }     ] } ```
zh-cn	#### Zabbix 发送请求  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value"         }     ] } ```

en-us	#### Zabbix sender request with a timestamp  Alternatively Zabbix sender can send a request with a timestamp and nanoseconds.  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710794,             "ns":592397170         },         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710795,             "ns":192399456         }     ],     "clock":1516712029,     "ns":873386094 } ```
zh-cn	 #### Zabbix sender 带有时间戳的请求  Zabbix sender可以发送一个带有时间戳的请求。  ``` {.javascript} {     "request":"sender data",     "data":[         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710794,             "ns":592397170         },         {             "host":"<hostname>",             "key":"trap",             "value":"test value",             "clock":1516710795,             "ns":192399456         }     ],     "clock":1516712029,     "ns":873386094 } ```

en-us	##### Zabbix server and frontend  Zabbix server configuration file draft with parameters to be updated:      ### Option: HistoryStorageURL     # History storage HTTP[S] URL.     #     # Mandatory: no     # Default:     # HistoryStorageURL=      ### Option: HistoryStorageTypes     # Comma separated list of value types to be sent to the history storage.     #     # Mandatory: no     # Default:     # HistoryStorageTypes=uint,dbl,str,log,text  Example parameter values to fill the Zabbix server configuration file with:      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text  This configuration forces Zabbix Server to store history values of numeric types in the corresponding database and textual history data in Elasticsearch.  Elasticsearch supports the following item types:      uint,dbl,str,log,text  Supported item type explanation:  |   |   |   | |---|---|---| |**Item value type**|**Database table**|**Elasticsearch type**| |Numeric (unsigned)|history\_uint|uint| |Numeric (float)|history|dbl| |Character|history\_str|str| |Log|history\_log|log| |Text|history\_text|text|  Zabbix frontend configuration file (`conf/zabbix.conf.php`) draft with parameters to be updated:      // Elasticsearch url (can be string if same url is used for all types).     $HISTORY['url']   = [           'uint' => 'http://localhost:9200',           'text' => 'http://localhost:9200'     ];     // Value types stored in Elasticsearch.     $HISTORY['types'] = ['uint', 'text'];  Example parameter values to fill the Zabbix frontend configuration file with:      $HISTORY['url']   = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  This configuration forces to store `Text`, `Character` and `Log` history values in Elasticsearch.  It is also required to make $HISTORY global in `conf/zabbix.conf.php` to ensure everything is working properly (see `conf/zabbix.conf.php.example` for how to do it):      // Zabbix GUI configuration file.     global $DB, $HISTORY;
zh-cn	##### Zabbix 服务端 和 前端  Zabbix 服务器配置文件模板，其中包含要更新的参数：      ### Option: HistoryStorageURL     # History storage HTTP[S] URL.     #     # Mandatory: no     # Default:     # HistoryStorageURL=      ### Option: HistoryStorageTypes     # Comma separated list of value types to be sent to the history storage.     #     # Mandatory: no     # Default:     # HistoryStorageTypes=uint,dbl,str,log,text      用于 Zabbix 服务端配置文件示例的参数值      HistoryStorageURL=http://test.elasticsearch.lan:9200     HistoryStorageTypes=str,log,text      此配置强制 Zabbix Server 在相应的数据库中存储数字类型的历史值，并在Elasticsearch中存储文本历史数据。  Elasticsearch 支持以下 item 类型:      uint,dbl,str,log,text  支持的 item 类型说明:  |   |   |   | |---|---|---| |**Item 类型**|**数据库表**|**Elasticsearch 类型**| |Numeric (unsigned)|history\_uint|uint| |Numeric (float)|history|dbl| |Character|history\_str|str| |Log|history\_log|log| |Text|history\_text|text|  Zabbix 前端配置文件 (`conf/zabbix.conf.php`) 参数待更新:      // Elasticsearch url (can be string if same url is used for all types).     $HISTORY['url']   = [           'uint' => 'http://localhost:9200',           'text' => 'http://localhost:9200'     ];     // Value types stored in Elasticsearch.     $HISTORY['types'] = ['uint', 'text'];  用于 Zabbix 前端配置文件示例的参数值 :      $HISTORY['url']   = 'http://test.elasticsearch.lan:9200';     $HISTORY['types'] = ['str', 'text', 'log'];  此配置强制在Elasticsearch种存储 `Text`, `Character` 及 `Log` 的历史值. 还需要在`conf/zabbix.conf.php`中使用全局变量 $HISTORY，以确保一切正常  (有关如何执行此操作，请参阅`conf/zabbix.conf.php.example` ):      // Zabbix GUI configuration file.     global $DB, $HISTORY;

en-us	#### Zabbix server/proxy configuration  Secure connections to the database can be configured with the respective parameters in the Zabbix [server](/manual/appendix/config/zabbix_server) and/or [proxy](/manual/appendix/config/zabbix_proxy) configuration file.  |Configuration|Result| |--|--| |None|Connection to the database without encryption.| |1\. Set DBTLSConnect=required|Server/proxy make a TLS connection to the database. An unencrypted connection is not allowed.| |1\. Set DBTLSConnect=verify\_ca<br>2. Set DBTLSCAFile - specify the TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate.| |1\. Set DBTLSConnect=verify\_full<br>2. Set DBTLSCAFile - specify TLS certificate authority file|Server/proxy make a TLS connection to the database after verifying the database certificate and the database host identity.| |1\. Set DBTLSCAFile - specify TLS certificate authority file<br>2. Set DBTLSCertFile - specify the client public key certificate file<br>3. Set DBTLSKeyFile - specify the client private key file|Server/proxy provide a client certificate while connecting to the database.| |1\. Set DBTLSCipher - the list of encryption ciphers that the client permits for connections using TLS protocols up to TLS 1.2<br><br>or DBTLSCipher13 - the list of encryption ciphers that the client permits for connections using TLS 1.3 protocol|(MySQL) TLS connection is made using a cipher from the provided list.<br>(PostgreSQL) Setting this option will be considered as an error.|
zh-cn	#### Zabbix 服务器/代理配置  可以使用 Zabbix [server](/manual/appendix/config/zabbix_server) 和/或 [proxy](/manual/appendix/config/zabbix_proxy) 配置文件中的相应参数配置与数据库的安全连接。  |配置|结果| |--|--| |无|未加密的数据库连接。| |1\.  设置 DBTLSConnect=required|服务器/代理与数据库建立 TLS 连接。 不允许未加密的连接。| |1\.  设置 DBTLSConnect=verify\_ca<br>2.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件|服务器/代理在验证数据库证书后与数据库建立 TLS 连接。| |1\. 设置 DBTLSConnect=verify\_full<br>2.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件|服务器/代理在验证数据库证书和数据库主机身份后与数据库建立 TLS 连接。| |1\.  设置 DBTLSCAFile - 指定 TLS 证书颁发机构文件<br>2.  设置 DBTLSCertFile - 指定客户端公钥证书文件<br>3. 设置 DBTLSKeyFile - 指定客户端私钥文件|服务器/代理在连接到数据库时提供客户端证书。| |1\. 设置 DBTLSCipher - 客户端允许使用最高 TLS 1.2 的 TLS 协议进行连接的加密密码列表<br><br>或 DBTLSCipher13 - 客户端允许使用 TLS 1.3 协议进行连接的加密密码列表|(MySQL) TLS 使用提供的列表中的密码建立连接。<br>(PostgreSQL) 设置此选项将被视为错误。|

en-us	#### Zabbix server response  ``` {.javascript} {     "response":"success",     "info":"processed: 1; failed: 0; total: 1; seconds spent: 0.060753" } ```
zh-cn	#### Zabbix server 响应  ``` {.javascript} {     "response":"success",     "info":"processed: 1; failed: 0; total: 1; seconds spent: 0.060753" } ```

en-us	#### Zabbix server response  ``` {.javascript} {     "response":"success",     "info":"processed: 2; failed: 0; total: 2; seconds spent: 0.060904" } ```
zh-cn	#### Zabbix服务器响应  ``` {.javascript} {     "response":"success",     "info":"processed: 2; failed: 0; total: 2; seconds spent: 0.060904" } ```

en-us	acknowledge
zh-cn	确认

en-us	acknowledged
zh-cn	已确认

en-us	Boolean to decimal
zh-cn	布尔值转十进制

en-us	Change per second
zh-cn	每秒变化

en-us	Check for error in JSON
zh-cn	JSON数据错误检查

en-us	Check for error in XML
zh-cn	XML数据错误检查

en-us	Check for error using regular expression
zh-cn	正则表达式检测数据

en-us	Check for not supported value
zh-cn	不支持监控项值检查

en-us	Custom multiplier
zh-cn	自定义倍数

en-us	dashboard
zh-cn	仪表盘

en-us	Discard unchanged
zh-cn	丢弃未变化的值

en-us	Discard unchanged with heartbeat
zh-cn	丢弃检测周期内未变化的值

en-us	discovery
zh-cn	发现

en-us	Does not match regular expression
zh-cn	未匹配正则表达式

en-us	fire
zh-cn	触发

en-us	frontend
zh-cn	前端

en-us	Hexademical to decimal
zh-cn	十六进制转十进制

en-us	host
zh-cn	主机

en-us	In range
zh-cn	区间值

en-us	item
zh-cn	监控项

en-us	Left trim
zh-cn	左截取

en-us	LLD
zh-cn	LLD

en-us	low-level discovery
zh-cn	低级别自动发现

en-us	Matches regular expression
zh-cn	匹配正则表达式

en-us	media type
zh-cn	媒介类型

en-us	Octal to decimal
zh-cn	八进制转十进制

en-us	OK event
zh-cn	恢复事件

en-us	preprocessing
zh-cn	预处理

en-us	preprocessing step
zh-cn	预处理步骤

en-us	problem event
zh-cn	故障事件

en-us	Prometheus pattern
zh-cn	Prometheus模式

en-us	Regular expression
zh-cn	正则表达式

en-us	Replace
zh-cn	替换

en-us	Right trim
zh-cn	右截取

en-us	scheduled report
zh-cn	计划报表

en-us	Simple change
zh-cn	简单变化

en-us	template
zh-cn	模板

en-us	trigger
zh-cn	触发器

en-us	Trim
zh-cn	截取

en-us	unacknowledge
zh-cn	取消确认

en-us	unacknowledged
zh-cn	已取消确认

en-us	webhook
zh-cn	Webhook

en-us	Zabbix
zh-cn	Zabbix

en-us	 © 2001-$year_now$ by Zabbix SIA. 
zh-cn	 © 2001-$year_now$ by Zabbix SIA.¶

en-us	 All rights reserved. 
zh-cn	 所有版权归Zabbix SIA所有.¶

en-us	 Back to top 
zh-cn	 回到顶部¶

en-us	 Close 
zh-cn	 关闭¶

en-us	 Comment (optional) 
zh-cn	 评论 (可选)¶

en-us	 (current) 
zh-cn	 (正确)¶

en-us	 (devel) 
zh-cn	 (开发中)¶

en-us	 Except where otherwise noted, Zabbix Documentation is licensed under the following license: 
zh-cn	 除非另有说明，否则Zabbix文档都是在以下许可证进行发布的:¶

en-us	 General 
zh-cn	总体的¶

en-us	 Have an improvement suggestion for this page? Select a text that could be improved and press Command+Enter to send it to editors. 
zh-cn	 对此页面有改进建议吗？选择您认为可以改进的文本，然后按Command+Enter将其发送给我们.¶

en-us	 Have an improvement suggestion for this page? Select a text that could be improved and press Ctrl+Enter to send it to editors. 
zh-cn	 对此页面有改进建议吗？选择您认为可以改进的文本，然后按Ctrl+Enter将其发送给我们。¶

en-us	 In development 
zh-cn	 开发中¶

en-us	 Report 
zh-cn	 报告¶

en-us	 Search 
zh-cn	 搜索¶

en-us	 Suggest an improvement 
zh-cn	 改进建议¶

en-us	 Supported 
zh-cn	 支持¶

en-us	 Table of Contents 
zh-cn	 目录¶

en-us	 Test translation 
zh-cn	 翻译测试¶

en-us	 This is a translation of the original English documentation page. Help us  make it better. 
zh-cn	 这是原厂英文文档的翻译页面. 欢迎帮助我们  [完善文档](https://www.zabbix.com/documentation/guidelines/en/translator_guidelines).

en-us	 # This topic does not exist yet.   We are sorry, the page you are looking for cannot be found. Return to the homepage, try searching, or get [help](https://www.zabbix.com/support). 
zh-cn	 # 此页面尚无内容.¶  ¶ 很抱歉，本页面尚无内容。可返回首页，尝试搜索其他相关内容，或寻求 [帮助](https://www.zabbix.com/support).¶

en-us	 Trademark Policy 
zh-cn	 商标政策¶

en-us	 Unsupported 
zh-cn	 (不支持)¶

en-us	 We appreciate your feedback! Our documentation writers will review your report and consider making suggested changes. Please note that we cannot respond. If you would like to follow up on the progress or participate in the discussion, please consider creating a documentation bug report at https://support.zabbix.com/ 
zh-cn	 感谢您的反馈！我们将审查您提交的报告并考虑根据您的建议进行更改。请注意，我们无法回复。如果您想跟进进度或参与讨论，请在https://support.zabbix.com/¶创建bug报告文档。

en-us	 You are viewing documentation for the development version, it may be incomplete.          Join our translation project and help translate Zabbix documentation          into your native language. 
zh-cn	 此文档是开发中版本的文档，所以暂不完整. [BR]  欢迎加入翻译团队并制作  [中文文档](https://www.zabbix.com/documentation/guidelines/en/translator_guidelines).

en-us	(0 - infinitely)
zh-cn	(0 - 无穷大)

en-us	0 or 1
zh-cn	0 或 1

en-us	(0 - use action default)
zh-cn	(0 - 使用默认)

en-us	0 - use default port
zh-cn	0 - 使用默认端口

en-us	100 busiest triggers
zh-cn	触发器TOP100

en-us	10 seconds
zh-cn	10秒

en-us	%1$d characters exceeds maximum length of %2$d characters
zh-cn	%1$d 个字符超出了 %2$d 个字符的最大长度

en-us	%1$d day
zh-cn	%1$d 天

en-us	%1$d matches for %2$s found
zh-cn	%1$d 匹配找到的 %2$s

en-us	%1$d of %3$d%2$s problem is shown
zh-cn	%1$d of %3$d%2$s 问题显示

en-us	1 minute
zh-cn	1分

en-us	(%1$s %2$s)
zh-cn	(%1$s %2$s)

en-us	%1$s action
zh-cn	%1$s 动作

en-us	%1$s event
zh-cn	%1$s 事件

en-us	"%1$s" is expected
zh-cn	"%1$s" 预计

en-us	%1$s item
zh-cn	%1$s 项目

en-us	%1$s Item
zh-cn	%1$s 监控项

en-us	%1$s [Line: %2$s | Column: %3$s]
zh-cn	%1$s [线: %2$s | 列: %3$s]

en-us	%1$s message
zh-cn	%1$s 消息

en-us	%1$s minute
zh-cn	%1$s 分

en-us	%1$s of %2$s element in problem state
zh-cn	处于问题状态的 %2$s 元素的 %1$s

en-us	%1$s preselected, use down,up arrow keys and enter to select
zh-cn	选择了 %1$s 项，您可以使用向上和向下箭头键以及回车键进行选择

en-us	%1$s problem
zh-cn	问题发生在 %1$s

en-us	%1$s problem in total
zh-cn	异常问题总计 %1$s

en-us	%1$s, read only
zh-cn	%1$s, 只读

en-us	%1$s retry left
zh-cn	剩余%1$s 重试次数

en-us	%1$s second
zh-cn	%1$s 秒

en-us	%1$s, selected
zh-cn	%1$s, 选择

en-us	%1$s, Severity, %2$s
zh-cn	%1$s, 严重性, %2$s

en-us	%1$s widget
zh-cn	小构件 %1$s 

en-us	%1$s (year %2$s)
zh-cn	%1$s (年 %2$s)

en-us	30 seconds
zh-cn	30秒

en-us	3D view
zh-cn	3D 视图

en-us	%4$s failed login attempt logged. Last failed attempt was from %1$s on %2$s at %3$s.
zh-cn	发生了 %4$s 次失败的登陆尝试。最后一次失败的登陆尝试发生在 %2$s 日 %3$s 客户端IP地址是 %1$s。 连续发生了 %4$s 次失败的登陆尝试。最后一次失败的登陆尝试发生在 %2$s 日 %3$s 客户端IP地址是 %1$s。

en-us	500 latest values
zh-cn	最近500个值

en-us	5 minutes
zh-cn	5分

en-us	5 seconds
zh-cn	5秒

en-us	a boolean is expected
zh-cn	预先设定的布尔值

en-us	abschange() - Absolute difference between last and previous value
zh-cn	abschange() - 后一个值与前一个值变动的绝对值。

en-us	Acceptable SLA
zh-cn	可接受的SLA

en-us	Access denied
zh-cn	访问拒绝

en-us	Access denied!
zh-cn	访问拒绝!

en-us	a character string is expected
zh-cn	请在字符串中指定

en-us	Ack
zh-cn	确认

en-us	Acknowledge
zh-cn	确认

en-us	Acknowledged
zh-cn	已确认

en-us	Acknowledged PROBLEM events
zh-cn	已确认问题事件

en-us	Acknowledged RESOLVED events
zh-cn	确认已解决的事件

en-us	Action
zh-cn	动作

en-us	Action "%1$s" already exists.
zh-cn	动作 "%1$s" 已经存在。

en-us	Action "%1$s" no operations defined.
zh-cn	动作 "%1$s" 没有定义操作。

en-us	Action added
zh-cn	动作已添加

en-us	Action class %1$s must extend %2$s class.
zh-cn	动作类 %1$s 必须扩展 %2$s 类。

en-us	Action condition value must be empty.
zh-cn	动作的条件必须为空。

en-us	Action deleted
zh-cn	动作已删除

en-us	Action disabled
zh-cn	激活 禁用激活 禁用

en-us	Action enabled
zh-cn	激活 启用激活 启用

en-us	Action log
zh-cn	动作日志

en-us	Actions
zh-cn	动作

en-us	#### Actions  Discovery events can be the basis of relevant [actions](/manual/config/notifications/action), such as:  -   Sending notifications -   Adding/removing hosts -   Enabling/disabling hosts -   Adding hosts to a group -   Removing hosts from a group -   Linking hosts to/unlinking from a template -   Executing remote scripts  These actions can be configured with respect to the device type, IP, status, uptime/downtime, etc. For full details on configuring actions for network-discovery based events, see action [operation](/manual/config/notifications/action/operation) and [conditions](/manual/config/notifications/action/conditions) pages.  Since network discovery actions are event-based, they will be triggered both when a discovered host is online and when it is offline. It is highly  recommended to add an action [condition](/manual/config/notifications/action/conditions) *Discovery status: up* to avoid such actions as *Add host* being triggered upon *Service Lost*/*Service Down* events.  Otherwise, if a discovered host is manually removed, it will still generate *Service Lost*/*Service Down* events and will be recreated during the next discovery cycle.  ::: noteclassic Linking a discovered host to templates will fail collectively if any of the linkable templates has a unique entity (e.g. item key) that is the same as a unique entity (e.g. item key) already existing on the host or on another of the linkable templates. :::
zh-cn	#### 动作  发现事件可触发相关[动作](/manual/config/notifications/action)，例如：  -   发送通知 -   添加/删除主机 -   启用/禁用主机 -   添加主机到组 -   从组中移除主机 -   链接/取消链接主机到模板 -   执行远程脚本  这些动作可基于设备类型、IP、状态、运行时长(uptime)/停机时长(downtime)等条件来配置。欲了解如何配置这些动作，参阅动作的[操作](/manual/config/notifications/action/operation) 和[条件](/manual/config/notifications/action/conditions) 页面获取完整细节。  ::: noteclassic 通过网络发现添加的主机，如果其链接的模板中有一个唯一属性(如监控项的键)与该主机上的唯一属性相同，或与该模板链接的其它主机上的唯一属性相同，则这台主机上的所有模板均会链接失败。 :::

en-us	Action updated
zh-cn	动作已更新

en-us	Active
zh-cn	启用中

en-us	Active
zh-cn	主动式

en-us	Active since
zh-cn	启用自从

en-us	Active till
zh-cn	启用直到

en-us	Add
zh-cn	添加

en-us	Add a new widget
zh-cn	添加新构件

en-us	Add child
zh-cn	添加子节点

en-us	Add child element
zh-cn	添加子节点元素

en-us	Added
zh-cn	已添加

en-us	Added, %1$s
zh-cn	%1$s，已添加

en-us	Add host
zh-cn	添加主机

en-us	Add multiple maps
zh-cn	添加多个拓扑图

en-us	Add new data set
zh-cn	添加新数据集

en-us	Add new or existing applications
zh-cn	添加新的或者已经存在的应用

en-us	Add new or existing host groups
zh-cn	添加新的或者已经存在的主机组

en-us	Add new override
zh-cn	添加新的覆盖

en-us	ADD OVERRIDE
zh-cn	添加覆盖

en-us	Add prototype
zh-cn	添加原型

en-us	Add submaps
zh-cn	添加子图

en-us	Add to favourites
zh-cn	添加到常用

en-us	Add to host group
zh-cn	添加到主机群组

en-us	Add to host groups
zh-cn	添加到主机群组

en-us	Add widget
zh-cn	添加构件

en-us	Adjust widget refresh interval
zh-cn	调整构件刷新间隔

en-us	Admin
zh-cn	管理者

en-us	Administration
zh-cn	管理

en-us	Advanced labels
zh-cn	高级标签

en-us	AES
zh-cn	AES

en-us	affects only filtered data
zh-cn	只影响过滤后的数据

en-us	Age
zh-cn	持续时间

en-us	Age less than
zh-cn	持续时间小于

en-us	Age less than %s
zh-cn	持续时间小于%s

en-us	agent
zh-cn	agent代理程序

en-us	Agent
zh-cn	客户端

en-us	Agent availability check. Returns nothing - unavailable; 1 - available
zh-cn	客户端可达性检查。返回 nothing - 不可达；1 - 可达

en-us	Agent encryption
zh-cn	agent 加密

en-us	Agent host name. Returns string
zh-cn	客户端主机名。返回字符串

en-us	Agent interfaces
zh-cn	agent代理程序的接口

en-us	Agent or SNMP or JMX or IPMI interface
zh-cn	agent代理程序或SNMP或JMX或IPMI的接口

en-us	a hexadecimal colour code (6 symbols) is expected
zh-cn	期望十六进制颜色代码（6个符号）

en-us	##### Alerting on service status change  It is now possible to receive automated alerts about service status changes, similar to the alerts about trigger status changes.  A new [service action](/manual/it_services/service_actions) functionality has been added, similar to other actions in Zabbix. Service actions may include steps for problem, recovery, and update operations related to services. It is possible to configure two types of actions: sending a message to the specified recipients and executing a remote command on Zabbix server. Similarly to trigger actions, service actions support problem [escalation](/manual/config/notifications/action/escalations) scenarios.  New message templates *Service*, *Service recovery*, and *Service update* have been added to [media types](/manual/config/notifications/media#common_parameters) and should be defined to enable correct sending of notifications for service actions.
zh-cn	##### 服务状态变化告警  现在可以接收有关服务状态更改的自动警报，类似于有关触发器状态更改的警报。  添加了一种新的 [服务动作](/manual/config/notifications/action) 类型，类似于 Zabbix 中的其他动作。服务可能动作包括与服务相关的问题、恢复和更新动作的步骤。可以配置两种类型的动作：向指定的收件人发送消息和在 Zabbix server 上执行远程命令。与触发动作类似，服务动作支持问题 [升级](/manual/config/notifications/action/escalations)场景。  新的消息模板 *Service*、*Service recovery* 和 *Service update* 已添加到 [媒体类型](/manual/config/notifications/media#common_parameters) 中，应该定义为能够正确发送服务动作的通知。

en-us	Alert message
zh-cn	告警消息

en-us	Alias
zh-cn	别名

en-us	Align map elements
zh-cn	对齐拓扑元素

en-us	all
zh-cn	所有

en-us	All
zh-cn	所有

en-us	All dashboards
zh-cn	添加仪表盘

en-us	All groups
zh-cn	所有组

en-us	All hosts
zh-cn	所有主机

en-us	All links should have "Name" and "URL" specified
zh-cn	所有的链接应含 特定的名称和URL

en-us	All maps
zh-cn	所有地图

en-us	all media
zh-cn	所有介质

en-us	Allowed hosts
zh-cn	允许的主机

en-us	Allow manual close
zh-cn	允许手动关闭

en-us	All problems
zh-cn	所有问题

en-us	All problems if tag values match
zh-cn	所有问题如果标签值匹配

en-us	All screens
zh-cn	所有 聚合图形

en-us	All slide shows
zh-cn	所有 IDE 展示

en-us	All tags
zh-cn	所有标签

en-us	All templates
zh-cn	所有模板

en-us	Alternatively, you can install it manually:
zh-cn	另外，您也可以手动安装:

en-us	an array is expected
zh-cn	请在阵列中指定

en-us	an array or a character string is expected
zh-cn	预设一个数组或一个字符串

en-us	And
zh-cn	和（同时满足）

en-us	AND
zh-cn	与

en-us	And/Or
zh-cn	与/或（默认）

en-us	an empty string is expected
zh-cn	请指定一个空字符串

en-us	an even number of hexadecimal characters is expected
zh-cn	预设会出现偶数个十六进制字符

en-us	an explicit time is expected
zh-cn	需要一个明确的时间

en-us	a number is expected
zh-cn	预先设定的数字

en-us	a number is too large
zh-cn	数字过大

en-us	a numeric value is expected
zh-cn	一个数值预计

en-us	Any
zh-cn	任何

en-us	Any character string included
zh-cn	包括任何字符串

en-us	Application
zh-cn	应用集

en-us	Application "%1$s" already exists.
zh-cn	应用集 "%1$s" 已存在.

en-us	Application added
zh-cn	应用集已添加

en-us	Application deleted
zh-cn	分类已删除

en-us	Application error.
zh-cn	应用集 错误.

en-us	Application prototypes
zh-cn	应用集原型

en-us	Applications
zh-cn	应用集

en-us	Application updated
zh-cn	应用集已更新

en-us	Application with applicationid "%1$s" does not exist.
zh-cn	应用程序ID "%1$s" 不存在。

en-us	Application with ID "%1$s" is not available on "%2$s".
zh-cn	ID为 "%1$s"的应用集不在 "%2$s" 之中.

en-us	Apply
zh-cn	应用

en-us	Apply permissions and tag filters to all subgroups
zh-cn	应用权限和标签过滤器到所有分组

en-us	Approaching
zh-cn	接近中

en-us	Apr
zh-cn	四月

en-us	April
zh-cn	四月

en-us	Area size
zh-cn	区域大小

en-us	Area type
zh-cn	区域类型

en-us	Are you sure you want perform this action?
zh-cn	您确定要执行这个动作吗?

en-us	Are you sure you want to delete
zh-cn	您确定要删除吗

en-us	Are you sure, you want to leave this page?
zh-cn	你是否确定要离开这个页面？

en-us	Arithmetic
zh-cn	算法

en-us	as Blue
zh-cn	成蓝

en-us	ascending
zh-cn	上一层

en-us	as Green
zh-cn	成绿

en-us	As is
zh-cn	不变

en-us	As plain text
zh-cn	纯文字

en-us	as Red
zh-cn	成红

en-us	Asset tag
zh-cn	资产标签

en-us	At %1$s:%2$s %3$s of every week
zh-cn	每周 %1$s:%2$s %3$s 每 %4$s 周 %1$s:%2$s %3$s

en-us	At %1$s:%2$s every day
zh-cn	每天 %1$s:%2$s每 %3$s 天 %1$s:%2$s

en-us	At %1$s:%2$s on %3$s %4$s of every %5$s
zh-cn	在 %1$s:%2$s 的 %3$s %4$s 的每个 %5$s

en-us	At %1$s:%2$s on day %3$s of every %4$s
zh-cn	在 %1$s:%2$s 的天 %3$s 的每个 %4$s

en-us	At (hour:minute)
zh-cn	于(时:分)

en-us	a time is expected
zh-cn	a 预计时间

en-us	a time period is expected
zh-cn	预设时间段

en-us	a time range is expected
zh-cn	预计时间范围

en-us	a time unit is expected
zh-cn	预设时间单位

en-us	At least one host group or host must be selected.
zh-cn	至少选择一个主机群组或主机。

en-us	At least one interface must exist.
zh-cn	至少存在一个接口。

en-us	At least one maintenance period must be created.
zh-cn	必须创建至少一个维护期间.

en-us	At least one of MySQL, PostgreSQL, Oracle or IBM DB2 should be supported.
zh-cn	至少要支持Mysql、PostgreSQL、Oracle或者IBMDB2其中一个。

en-us	At least one operation must exist.
zh-cn	必须至少设置一个执行内容。

en-us	At least one operation or recovery operation must exist.
zh-cn	至少需要设置一个恢复操作或者操作.

en-us	At least one operation, recovery operation or update operation must exist.
zh-cn	必须设置恢复时的至少一个执行内容或执行内容或更新时的执行内容。

en-us	at least one override option must be specified
zh-cn	至少选定一个覆盖选项

en-us	At least one update operation is mandatory
zh-cn	必须至少设置一个更新内容

en-us	At least one update operation or message must exist.
zh-cn	至少需要一个更新内容或消息。

en-us	At least one user or user group must be selected.
zh-cn	您必须至少选择一个用户或用户组。

en-us	Attempt interval
zh-cn	尝试间隔

en-us	Attempts
zh-cn	尝试次数

en-us	Audit
zh-cn	审计

en-us	Audit data storage period
zh-cn	审计数据存储时间

en-us	Audit data storage period "%1$s".
zh-cn	审计数据存储期 "%1$s" 。

en-us	Audit log
zh-cn	审计日志

en-us	Aug
zh-cn	八月

en-us	August
zh-cn	八月

en-us	a user macro is expected
zh-cn	预设用户宏

en-us	Authentication
zh-cn	认证

en-us	Authentication algorithm
zh-cn	认证算法

en-us	Authentication failed: %1$s.
zh-cn	验证失败: %1$s

en-us	Authentication method
zh-cn	认证方法

en-us	Authentication method changed
zh-cn	身份验证已经变更

en-us	Authentication passphrase
zh-cn	验证口令

en-us	Authentication protocol
zh-cn	验证协议

en-us	Authentication settings updated
zh-cn	验证设置已更新

en-us	Auto
zh-cn	自动

en-us	Auto-login
zh-cn	自动登录

en-us	Auto-login and auto-logout options cannot be enabled together.
zh-cn	自动登录和自动注销功能不能同时使用。

en-us	Auto-logout
zh-cn	自动注销

en-us	Automatic
zh-cn	自动地

en-us	Automatic icon mapping
zh-cn	自动的图标映射

en-us	Automatic icon selection
zh-cn	自动的图标选择

en-us	auto-registered host
zh-cn	自动被注册的主机

en-us	auto registration
zh-cn	自动注册

en-us	Auto registration
zh-cn	自动注册

en-us	Auto-registration data storage period
zh-cn	自动数据存储日期

en-us	Auto-registration event and alert data storage period
zh-cn	自动注册时间和警报数据保存时间

en-us	Auto-registration event and alert data storage period "%1$s".
zh-cn	自动注册事件和报警数据存储期 "%1$s" 。

en-us	Availability
zh-cn	可用性

en-us	Availability report
zh-cn	可用性报表

en-us	Available
zh-cn	可用

en-us	Average
zh-cn	一般严重

en-us	avg
zh-cn	平均

en-us	avg() - Average value of a period T
zh-cn	avg() - 周期 T 内的平均值

en-us	Axes
zh-cn	坐标轴

en-us	Back
zh-cn	返回

en-us	Background
zh-cn	背景

en-us	Background colour
zh-cn	背景色

en-us	Background image
zh-cn	背景图片

en-us	band() - Bitwise AND of last (most recent) T value and mask
zh-cn	band() - 将最近的 T 值和掩码进行按位与运算

en-us	Base colour
zh-cn	基色

en-us	Base DN
zh-cn	基于 DN

en-us	Basic
zh-cn	基础的

en-us	Bind DN
zh-cn	绑定 DN

en-us	Bind password
zh-cn	绑定密码

en-us	blinking
zh-cn	闪烁

en-us	Blinking
zh-cn	闪烁中

en-us	Blocked
zh-cn	锁定的

en-us	Blue
zh-cn	蓝

en-us	Body
zh-cn	内容

en-us	Body and headers
zh-cn	body 和 headers

en-us	Bold line
zh-cn	粗线

en-us	Boolean to decimal
zh-cn	布尔值到十进制

en-us	Border
zh-cn	边

en-us	Border colour
zh-cn	边框颜色

en-us	Border type
zh-cn	边框类型

en-us	Border width
zh-cn	边框宽度

en-us	both username and password should be either present or empty
zh-cn	用户名和密码都应该存在或为空

en-us	Bottom
zh-cn	底部

en-us	Bring forward
zh-cn	向上一层

en-us	Bring to front
zh-cn	移到上一层

en-us	Bulgarian (bg_BG)
zh-cn	保加利亚语 (bg_BG)

en-us	By host
zh-cn	按主机

en-us	By trigger template
zh-cn	按触发器模板

en-us	calculated
zh-cn	计算的

en-us	Calculated
zh-cn	可计算的

en-us	Calculate SLA, acceptable SLA (in %)
zh-cn	计算SLA, 可接受的SAL(%计)

en-us	Calendar
zh-cn	日历

en-us	Callback
zh-cn	回调

en-us	Canada (136 characters)
zh-cn	加拿大 (136 字节)

en-us	Cancel
zh-cn	取消

en-us	Cannot add action
zh-cn	无法添加操作

en-us	Cannot add action condition
zh-cn	不能添加动作条件

en-us	Cannot add a discovered application "%1$s" to a web scenario.
zh-cn	不能添加一个已发现的应用集 "%1$s" 到 web 场景。

en-us	Cannot add a non-numeric item "%1$s" to graph "%2$s".
zh-cn	不能添加一个非数字监控项 "%1$s" 到图表 "%2$s".

en-us	Cannot add a non-numeric item "%1$s" to graph prototype "%2$s".
zh-cn	不可以添加一个非数值型的监控项目 "%1$s"到数据图模板"%2$s".

en-us	Cannot add application
zh-cn	无法添加应用集

en-us	Cannot add correlation
zh-cn	无法添加关联

en-us	Cannot add correlation condition
zh-cn	无法添加关联条件

en-us	Cannot add dependency from a host to a template.
zh-cn	无法添加自主机到模板的依赖

en-us	Cannot add dependency from trigger "%1$s:%2$s" to non existing trigger "%3$s:%4$s".
zh-cn	无法自触发器"%1$s:%2$s" 添加依赖到不存在的触发器"%3$s:%4$s".

en-us	Cannot add discovery rule
zh-cn	无法添加自动自动发现的规则

en-us	Cannot add graph
zh-cn	无法添加图表

en-us	Cannot add graph prototype
zh-cn	无法添加图形原型

en-us	Cannot add group
zh-cn	无法添加群组

en-us	Cannot add host
zh-cn	无法添加主机

en-us	Cannot add host prototype
zh-cn	无法添加主机原型

en-us	Cannot add image
zh-cn	无法添加图片

en-us	Cannot add item
zh-cn	无法添加监控项

en-us	Cannot add item "%1$s" from "%2$s" to application "%3$s" from "%4$s".
zh-cn	无法添加监控项目"%1$s"从"%2$s"到分类 "%3$s" 从"%4$s".

en-us	Cannot add item prototype
zh-cn	不能添加监控项原型

en-us	Cannot add items.
zh-cn	不能添加监控项.

en-us	Cannot add maintenance
zh-cn	无法添加维护

en-us	Cannot add map element of the map "%1$s" due to circular reference.
zh-cn	由于循环引用所以无法添加拓扑元素到拓扑图 "%1$s"。

en-us	Cannot add media type
zh-cn	无法添加报警媒介类型

en-us	Cannot add more than one item with type "Graph sum" on graph "%1$s".
zh-cn	无法添加超过一个 "图形总计" 类型的监控项于图形 "%1$s"上.

en-us	Cannot add more than one item with type "Graph sum" on graph prototype "%1$s".
zh-cn	不可以在数据图模板"%1$s"上添加超过一个"Graph sum"类型的监控项目.

en-us	Cannot add network map
zh-cn	无法添加网络拓扑图

en-us	Cannot add new application "%1$s".
zh-cn	不能添加新的应用 "%1$s".

en-us	Cannot add proxy
zh-cn	无法添加agent代理程序

en-us	Cannot add regular expression
zh-cn	无法添加正则表达式

en-us	Cannot add screen
zh-cn	无法添加聚合图形

en-us	Cannot add script
zh-cn	无法添加脚本

en-us	Cannot add service
zh-cn	无法添加服务

en-us	Cannot add slide show
zh-cn	无法添加幻灯片演示

en-us	Cannot add submaps. Max depth reached.
zh-cn	无法添加子图，已经是最大的深度了。

en-us	Cannot add template
zh-cn	无法添加模板

en-us	Cannot add trigger
zh-cn	无法添加触发器

en-us	Cannot add trigger prototype
zh-cn	无法添加触发器模板

en-us	Cannot add user
zh-cn	无法添加用户

en-us	Cannot add user. Both passwords must be equal.
zh-cn	无法添加用户. 两次输入的密码必须一致。

en-us	Cannot add value map
zh-cn	无法添加值映射

en-us	Cannot add web scenario
zh-cn	不能添加web场景

en-us	Cannot add widgets in kiosk mode
zh-cn	在 kiosk 模式下无法添加 widgets

en-us	cannot be changed
zh-cn	不能变更

en-us	cannot be empty
zh-cn	不能为空

en-us	Can not be removed
zh-cn	无法被删除

en-us	Cannot bind anonymously to LDAP server.
zh-cn	无法绑定到匿名 LDAP 服务器。

en-us	Cannot bind to LDAP server.
zh-cn	无法绑定到 LDAP 服务器。

en-us	Cannot clear history
zh-cn	无法清除历史

en-us	Cannot clone graph prototypes.
zh-cn	无法克隆图形原型

en-us	Cannot clone host prototypes.
zh-cn	无法克隆主机原型。

en-us	Cannot clone item prototypes.
zh-cn	无法克隆监控项原型

en-us	Cannot clone trigger prototypes.
zh-cn	无法克隆触发器原型

en-us	Cannot close problem: %1$s.
zh-cn	无法关闭问题: %1$s.

en-us	Cannot connect to LDAP server.
zh-cn	无法连接到 LDAP 服务器。

en-us	Cannot connect to the database.
zh-cn	不能连接到数据库。

en-us	cannot convert to JSON, result value too long
zh-cn	无法转换到 JSON，结果值太长

en-us	Cannot copy graph
zh-cn	无法复制图表

en-us	Cannot copy item
zh-cn	无法复制监控项

en-us	Cannot copy trigger
zh-cn	无法复制触发器

en-us	Cannot copy trigger "%1$s:%2$s", because it has multiple hosts in the expression.
zh-cn	无法复制触发器 "%1$s:%2$s", 因为在其表达式中有多个主机.

en-us	Cannot create a host prototype on a discovered host "%1$s".
zh-cn	在自动发现的主机"%1$s"上不能创建主机模板

en-us	Cannot create another database connection.
zh-cn	无法创建其他的数据库连接.

en-us	Cannot create circular dependencies.
zh-cn	不能创建环形的依赖关系。

en-us	Cannot create dependency on trigger itself.
zh-cn	不能创建触发器本身的依赖.

en-us	Cannot create dependency on trigger prototype itself.
zh-cn	无法创建触发器原形的依赖。

en-us	Cannot create discovery rule
zh-cn	无法创建自动发现规则

en-us	Cannot create icon map
zh-cn	无法创建图标映射

en-us	Cannot create new application, web scenario is already assigned to application.
zh-cn	无法创建新的应用集, web 场景已分配给应用集.

en-us	Cannot create the configuration file.
zh-cn	无法创建配置文件。

en-us	Cannot create widget: %1$s.
zh-cn	不能创建构件: %1$s 。

en-us	Cannot delete action
zh-cn	无法删除动作

en-us	Cannot delete application
zh-cn	无法删除分类

en-us	Cannot delete correlation
zh-cn	无法删除关联

en-us	Cannot delete correlation
zh-cn	无法删除关联

en-us	Cannot delete dashboard
zh-cn	无法删除仪表盘

en-us	Cannot delete dependency
zh-cn	无法删除依赖关系

en-us	Cannot delete discovered application "%1$s".
zh-cn	不能删除已发现的应用集 "%1$s".

en-us	Cannot delete discovery rule
zh-cn	无法删除自动发现规则

en-us	Cannot delete discovery rule
zh-cn	无法删除自动发现规则

en-us	Cannot delete discovery rules
zh-cn	无法删除自动发现规则

en-us	Cannot delete graph
zh-cn	无法删除图形

en-us	Cannot delete graph prototype
zh-cn	无法删除图表原型

en-us	Cannot delete graph prototypes
zh-cn	无法删除数据图模板

en-us	Cannot delete graphs
zh-cn	无法删除图形

en-us	Cannot delete group
zh-cn	无法删除组

en-us	Cannot delete host
zh-cn	无法删除主机

en-us	Cannot delete host because maintenance "%1$s" must contain at least one host or host group.
zh-cn	无法删除主机因为维护 "%1$s" 必须包含至少一个主机或一个主机群组。无法删除所选主机因为维护 "%1$s" 必须包含至少一个主机或一个主机群组。

en-us	Cannot delete host group because maintenance "%1$s" must contain at least one host or host group.
zh-cn	无法删除主机群组因为维护 "%1$s" 必须包含至少一个主机或一个主机群组。无法删除所选主机群组因为维护 "%1$s" 必须包含至少一个主机或一个主机群组。

en-us	Cannot delete host prototype.
zh-cn	无法删除主机原型。

en-us	Cannot delete host prototypes
zh-cn	无法删除主机原型

en-us	Cannot delete icon map
zh-cn	无法删除图标映射

en-us	Cannot delete image
zh-cn	无法删除图片

en-us	Cannot delete inventory.
zh-cn	无法删除资产纪录.

en-us	Cannot delete item
zh-cn	无法删除监控项

en-us	Cannot delete item prototype
zh-cn	无法删除监控项目模板

en-us	Cannot delete item prototypes
zh-cn	无法删除监控项目模板

en-us	Cannot delete items
zh-cn	无法删除监控项

en-us	Cannot delete maintenance
zh-cn	无法删除维护

en-us	Cannot delete media type
zh-cn	无法删除示警媒介类型

en-us	Cannot delete network map
zh-cn	无法删除网络拓扑图

en-us	Cannot delete proxy
zh-cn	无法删除agent代理程序

en-us	Cannot delete regular expression
zh-cn	无法删除正则表达式 

en-us	Cannot delete screen
zh-cn	无法删除聚合图形

en-us	Cannot delete script
zh-cn	无法删除脚本

en-us	Cannot delete scripts. Script "%1$s" is used in action operation "%2$s".
zh-cn	无法删除脚本. 脚本 "%1$s" 用于动作操作 "%2$s"。

en-us	Cannot delete selected actions
zh-cn	无法删除所选的动作

en-us	Cannot delete selected correlations
zh-cn	无法删除选择的关联项

en-us	Cannot delete service
zh-cn	无法删除服务

en-us	Cannot delete service
zh-cn	无法删除服务

en-us	Cannot delete slide show
zh-cn	无法删除幻灯片演示

en-us	Cannot delete template
zh-cn	无法删除模板

en-us	Cannot delete templated application.
zh-cn	无法删除模板的应用集.

en-us	Cannot delete templated graph.
zh-cn	无法删除模板的图表。

en-us	Cannot delete templated graph prototype.
zh-cn	无法删除模板的图表原型。

en-us	Cannot delete templated host prototype.
zh-cn	无法删除模板的主机原型。

en-us	Cannot delete templated item.
zh-cn	无法删除模板的监控项.

en-us	Cannot delete templated item prototype.
zh-cn	无法删除模板的监控项原型。

en-us	Cannot delete templated items.
zh-cn	无法删除模板监控项.

en-us	Cannot delete templated trigger "%1$s:%2$s".
zh-cn	无法删除模板的触发器 "%1$s:%2$s".

en-us	Cannot delete templated trigger prototype "%1$s:%2$s".
zh-cn	无法删除模板的触发器原型 "%1$s:%2$s"。

en-us	Cannot delete templated web scenario "%1$s".
zh-cn	无法删除模板的 web 场景 "%1$s".

en-us	Cannot delete trigger
zh-cn	无法删除触发器

en-us	Cannot delete trigger prototype
zh-cn	无法删除触发器原型

en-us	Cannot delete trigger prototypes
zh-cn	无法删除触发器原型

en-us	Cannot delete triggers
zh-cn	无法删除触发器

en-us	Cannot delete user
zh-cn	无法删除用户

en-us	Cannot delete value map
zh-cn	无法删除值对应

en-us	Cannot delete web scenario
zh-cn	无法删除 web 场景

en-us	Cannot delete Zabbix internal user "%1$s", try disabling that user.
zh-cn	无法删除Zabbix内部用户 "%1$s", 试试停用这个用户.

en-us	Cannot disable action
zh-cn	无法禁用动作

en-us	Cannot disable correlation
zh-cn	无法停用关联项

en-us	Cannot disable discovery rule
zh-cn	无法禁用自动发现规则

en-us	Cannot disable host
zh-cn	无法禁用主机

en-us	Cannot disable item
zh-cn	无法禁监控项目

en-us	Cannot disable media type
zh-cn	无法禁用消息介质类型

en-us	Cannot disable trigger
zh-cn	无法禁用触发器

en-us	Cannot disable user group
zh-cn	无法禁用用户组

en-us	Cannot disable web scenario
zh-cn	无法禁用 web 场景

en-us	Cannot display item queue.
zh-cn	无法显示监控项队列.

en-us	Cannot display more than one item with type "Graph sum".
zh-cn	不可以显示超过一个 "Graph sum"类型的监控项目

en-us	Cannot enable action
zh-cn	无法启用动作

en-us	Cannot enable correlation
zh-cn	无法启用关联项

en-us	Cannot enable discovery rule
zh-cn	无法启用自动发现规则

en-us	Cannot enable host
zh-cn	无法启用主机

en-us	Cannot enable item
zh-cn	无法启用监控项目

en-us	Cannot enable media type
zh-cn	无法启用消息介质类型

en-us	Cannot enable trigger
zh-cn	无法启用触发器

en-us	Cannot enable user group
zh-cn	无法启用用户组

en-us	Cannot enable web scenario
zh-cn	无法启用Web场景

en-us	Cannot execute script
zh-cn	无法执行脚本

en-us	Cannot expand macros.
zh-cn	无法扩展宏.

en-us	Cannot find background image "%1$s" used in map "%2$s".
zh-cn	无法找到用在聚合图形 "%2$s" 中的群组 "%1$s".

en-us	Cannot find graph "%1$s" used in screen "%2$s".
zh-cn	无法找到图表 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find group "%1$s" used in map "%2$s".
zh-cn	无法找到群组 "%1$s" 用于地图 "%2$s".

en-us	Cannot find group "%1$s" used in screen "%2$s".
zh-cn	无法找到群组 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find host "%1$s" used in map "%2$s".
zh-cn	无法找到主机 "%1$s" 用于地图 "%2$s".

en-us	Cannot find host "%1$s" used in screen "%2$s".
zh-cn	无法找到主机 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find host group "%1$s" for host prototype "%2$s" of discovery rule "%3$s" on "%4$s".
zh-cn	在 "%4$s"上无法针对自动发现规则 "%3$s"上的"%2$s"主机模板找到主机组 "%1$s"

en-us	Cannot find host interface on "%1$s" for item key "%2$s".
zh-cn	在 "%1$s" 找不到用于监控项 key"%2$s" 的主机接口.

en-us	Cannot find icon "%1$s" used in map "%2$s".
zh-cn	无法找到图标 "%1$s" 用于地图 "%2$s".

en-us	Cannot find icon map "%1$s" used in map "%2$s".
zh-cn	无法找到地图图标 "%1$s" 用于地图 "%2$s".

en-us	Cannot find item "%1$s" on "%2$s" used as the Y axis MAX value for graph "%3$s".
zh-cn	无法为数据图"%3$s"在"%2$s"上找到可以作为最大Y值的监控项目 "%1$s".

en-us	Cannot find item "%1$s" on "%2$s" used as the Y axis MAX value for graph prototype "%3$s" of discovery rule "%4$s" on "%5$s".
zh-cn	无法在"%2$s"上为"%5$s"上的自动发现规则"%4$s"上的数据图模板"%3$s"找到可以作为最大Y值的监控项目"%1$s".

en-us	Cannot find item "%1$s" on "%2$s" used as the Y axis MIN value for graph "%3$s".
zh-cn	无法为数据图 "%3$s"在"%2$s"上可以作为最小值的监控项目"%1$s"

en-us	Cannot find item "%1$s" on "%2$s" used as the Y axis MIN value for graph prototype "%3$s" of discovery rule "%4$s" on "%5$s".
zh-cn	无法在"%2$s"上为"%5$s"上的自动发现规则"%4$s"上的数据图模板"%3$s"找到可以作为最小Y值的监控项目"%1$s"

en-us	Cannot find item "%1$s" on "%2$s" used in graph "%3$s".
zh-cn	无法在"%2$s"上找到被数据图"%3$s"引用的监控项目"%1$s".

en-us	Cannot find item "%1$s" on "%2$s" used in graph prototype "%3$s" of discovery rule "%4$s" on "%5$s".
zh-cn	在 "%5$s"中无法找到被自动发现规则"%4$s"上的数据图模板 "%3$s"在"%2$s"上所引用的监控项目"%1$s".

en-us	Cannot find item "%1$s" used in screen "%2$s".
zh-cn	无法找到监控项 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find map "%1$s" used in map "%2$s".
zh-cn	无法找到地图 "%1$s" 用于地图 "%2$s".

en-us	Cannot find map "%1$s" used in screen "%2$s".
zh-cn	无法找到地图 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find screen "%1$s" used in screen "%2$s".
zh-cn	无法找到屏幕 "%1$s" 用于聚合图形 "%2$s".

en-us	Cannot find template "%1$s" for host prototype "%2$s" of discovery rule "%3$s" on "%4$s".
zh-cn	无法在"%4$s"上为自动发现规则 "%3$s"上的主机模板"%2$s"找模板"%1$s"

en-us	Cannot find trigger "%1$s" used in map "%2$s".
zh-cn	无法找到触发器 "%1$s" 用于地图 "%2$s".

en-us	Cannot find value map "%1$s" used for item "%2$s" on "%3$s".
zh-cn	无法在 "%3$s"上找到由监控项目"%2$s" 所引用的数据映射"%1$s".

en-us	Cannot find value map "%1$s" used for item prototype "%2$s" of discovery rule "%3$s" on "%4$s".
zh-cn	无法在"%4$s"上找到由自动发现规则 "%3$s"上的 "%2$s"监控项目模板所引用的数据映射 "%1$s".

en-us	Cannot format tree.
zh-cn	无法形成树状格式

en-us	Cannot format Tree. Check logic structure in service links.
zh-cn	无法形成树状格式。检查服务链接的逻辑结构。

en-us	Cannot have empty visible template name.
zh-cn	模板的显示名称不得为空.

en-us	Cannot import screen "%1$s": subscreen "%2$s" does not exist.
zh-cn	无法导入聚合图形 "%1$s":子聚合图形"%2$s"不存在.

en-us	Cannot import template "%1$s", linked template "%2$s" does not exist.
zh-cn	无法导入模板 "%1$s",被关联的模板"%2$s"不存在.

en-us	Cannot include JS file "%s".
zh-cn	导入JS文件失败"%s".

en-us	Cannot include view file "%s".
zh-cn	不能包含视图文件 "%s".

en-us	Cannot insert trigger expression
zh-cn	不能插入触发器表达式

en-us	Cannot link template
zh-cn	无法链接模板

en-us	Cannot link template.
zh-cn	无法链接到模板。

en-us	Cannot logout.
zh-cn	不能登出

en-us	Cannot mass update host name.
zh-cn	不能大量更新主机名称.

en-us	Cannot mass update template name.
zh-cn	无法批量更新模板名称.

en-us	Cannot mass update visible host name.
zh-cn	不能大量更新可见主机名称

en-us	Cannot mass update visible template name.
zh-cn	无法批量更新模板的显示名称

en-us	Cannot pass duplicate template IDs for the linkage: %s.
zh-cn	不能传递重复的模板IDs给链接: %s.

en-us	Cannot perform delete statement on table "%1$s" without where condition.
zh-cn	不能完成没有where条件的删除描述式在表 "%1$s" 上.

en-us	cannot perform Scroll API request, data could be truncated
zh-cn	无法执行 Scroll API 请求，数据可能会被截断

en-us	Cannot perform update statement on table "%1$s" without values.
zh-cn	不能完成没有值的更新表达式料表 "%1$s" 上.

en-us	Cannot perform update statement on table "%1$s" without where condition.
zh-cn	不能完成没有条件的更新描述式在表 "%1$s" 上.

en-us	Cannot process applications from different hosts or templates.
zh-cn	无法在不同的主机或模板上执行分类

en-us	Cannot read JSON: %1$s.
zh-cn	无法读取JSON：%1$s 。

en-us	Cannot read the response, check connection with the Zabbix server "%1$s".
zh-cn	不能读取响应, 检查与Zabbix服务器 "%1$s" 的连接.

en-us	Cannot read XML: %1$s.
zh-cn	无法读取XML： %1$s 。

en-us	Cannot rename guest user.
zh-cn	无法重新命名访客用户.

en-us	Cannot save discovery rule without checks.
zh-cn	无法储存未检验的自动发现规则

en-us	Cannot save widget "%1$s".
zh-cn	无法保存小构件 "%1$s" 。

en-us	Cannot send command, check connection with Zabbix server "%1$s".
zh-cn	无法发送命令, 检查于Zabbix 服务器 "%1$s" 的连接.

en-us	Cannot send request
zh-cn	无法发送请求

en-us	Cannot send request: %1$s.
zh-cn	%1$s 请求无法发送。

en-us	Cannot set "%1$s" for action "%2$s".
zh-cn	在动作 "%2$s" 中无法设置 "%1$s" 

en-us	Cannot set "%1$s" for graph "%2$s".
zh-cn	在图形 "%2$s" 中无法设置 "%1$s"

en-us	Cannot set "%1$s" for graph prototype "%2$s".
zh-cn	在模板 "%2$s" 中无法设置 "%1$s"

en-us	Cannot set "%1$s" for item "%2$s".
zh-cn	无法设置 "%1$s" 为监控项 "%2$s".

en-us	Cannot set "%1$s" for template screen "%2$s".
zh-cn	不能设置"%1$s"在模板聚合图形"%2$s"中。

en-us	Cannot set inventory fields for disabled inventory.
zh-cn	无法设置审计字段为已经禁止的审计.

en-us	Cannot set resource ID for screen element.
zh-cn	无法设置聚合图形元素的资源ID.

en-us	Cannot set "templateid" field for application prototype in item prototype "%1$s".
zh-cn	不能设置 "templateid" 设置到项目原形 "%1$s" 。

en-us	Cannot set "templateid" for screen "%1$s".
zh-cn	无法设置 "模板序列号" 为聚合图形 "%1$s".

en-us	Cannot switch host for interface.
zh-cn	无法切换接口主机.

en-us	Cannot unblock users
zh-cn	无法解锁用户

en-us	Cannot unlink and clear applications.
zh-cn	无法断开和清除应用程序.

en-us	Cannot unlink and clear discovery rules
zh-cn	无法断开和清除探索规则

en-us	Cannot unlink and clear Web scenarios.
zh-cn	无法断开和清除 Web 场景.

en-us	Cannot unlink template
zh-cn	无法断开与模板的连接

en-us	Cannot unlink template.
zh-cn	无法断开与模板的连接。

en-us	Cannot unlink trigger "%s", it has items from template that is left linked to host.
zh-cn	不能断开与触发器"%s" 的连接, 它仍含有链接到主机的模板的监控项.

en-us	Cannot update "%1$s" for action "%2$s".
zh-cn	不能对动作"%2$s"更新"%1$s".

en-us	Cannot update "%1$s" for graph "%2$s".
zh-cn	图形 "%2$s" 无法更新 "%1$s"

en-us	Cannot update "%1$s" for graph prototype "%2$s".
zh-cn	图形模板 "%2$s" 无法更新 "%1$s" 

en-us	Cannot update "%1$s" for item "%2$s".
zh-cn	无法更新 "%1$s" 为监控项 "%2$s".

en-us	Cannot update "%1$s" for templated trigger "%2$s".
zh-cn	触发器模板 "%2$s" 无法更新 "%1$s"

en-us	Cannot update "%1$s" for templated trigger prototype "%2$s".
zh-cn	触发器原型 "%2$s" 无法更新到模板 "%1$s"。

en-us	Cannot update "%2$s" for a discovered host "%1$s".
zh-cn	无法更新 "%2$s"在发现的主机"%1$s"。

en-us	Cannot update "%2$s" for a discovered item "%1$s".
zh-cn	无法更新 "%2$s"在发现的监控项 "%1$s"。

en-us	Cannot update "%2$s" for a discovered trigger "%1$s".
zh-cn	无法更新 "%2$s" 在发现的触发器"%1$s"。

en-us	Cannot update action
zh-cn	无法更新动作

en-us	Cannot update a discovered graph.
zh-cn	无法更新一个被自动发现的数据图

en-us	Cannot update a discovered host group.
zh-cn	无法更新一个被自动发现的主机组.

en-us	Cannot update application
zh-cn	无法更新应用集

en-us	Cannot update a templated web scenario "%1$s": %2$s.
zh-cn	无法更新模板web场景 "%1$s": %2$s 。

en-us	Cannot update authentication
zh-cn	无法更新验证信息

en-us	Cannot update configuration
zh-cn	无法更新配置

en-us	Cannot update correlation
zh-cn	无法更新关联

en-us	Cannot update debug mode
zh-cn	无法更新调试模式

en-us	Cannot update description
zh-cn	无法更描述

en-us	Cannot update discovered application "%1$s".
zh-cn	无法更新发现的应用"%1$s"。

en-us	Cannot update discovery rule
zh-cn	无法更新自动发现规则

en-us	Cannot update event
zh-cn	无法更新事件

en-us	Cannot update frontend access
zh-cn	无法更新前端访问

en-us	Cannot update graph
zh-cn	无法更新图形

en-us	Cannot update graph prototype
zh-cn	无法更新数据图模板

en-us	Cannot update group
zh-cn	无法更新群组

en-us	Cannot update groups for discovered host "%1$s".
zh-cn	对于被自动发现的主机"%1$s"无法更新其主机组

en-us	Cannot update host
zh-cn	无法更新主机

en-us	Cannot update host encryption settings. Connection settings for both directions should be specified.
zh-cn	无法更新主机的加密设置，配置两端的设置规则不正确。

en-us	Cannot update host prototype
zh-cn	无法更新主机模板

en-us	Cannot update hosts
zh-cn	无法更新主机

en-us	Cannot update icon map
zh-cn	无法更新图标映射

en-us	Cannot update image
zh-cn	无法更新图片

en-us	Cannot update "imagetype" for image "%1$s".
zh-cn	无法对图片"%1$s"更新"图片类型".

en-us	Cannot update interface for discovered host "%1$s".
zh-cn	对于自动发现的主机"%1$s"无法更新其接口.

en-us	Cannot update item
zh-cn	无法更新监控项

en-us	Cannot update item prototype
zh-cn	无法更新监控项目模板

en-us	Cannot update items
zh-cn	无法更新监控项

en-us	Cannot update macros
zh-cn	无法更新宏

en-us	Cannot update maintenance
zh-cn	无法更新维护

en-us	Cannot update media type
zh-cn	无法更新媒介型态

en-us	Cannot update network map
zh-cn	无法更新网络拓扑图

en-us	Cannot update proxy
zh-cn	无法更新agent代理程序

en-us	Cannot update proxy for discovered host "%1$s".
zh-cn	对于被自动发现的主机 "%1$s"无法更新其代理节点

en-us	Cannot update regular expression
zh-cn	无法更新正则表达式

en-us	Cannot update screen
zh-cn	无法更新聚合图形

en-us	Cannot update script
zh-cn	无法更新脚本

en-us	Cannot update service
zh-cn	无法更新服务

en-us	Cannot update slide show
zh-cn	无法更新幻灯片演示

en-us	Cannot update step for a templated web scenario "%1$s": %2$s.
zh-cn	无法更新模板化Web场景的步骤 "%1$s": %2$s。

en-us	Cannot update template
zh-cn	无法更新模板

en-us	Cannot update templated applications.
zh-cn	无法更新被模板化的应用程序.

en-us	Cannot update "templateid" for screen "%1$s".
zh-cn	无法更新 "模板序列号" 为聚合图形 "%1$s"。

en-us	Cannot update "templateid" for template screen "%1$s".
zh-cn	无法对聚合图形模板"%1$s"更新"模板ID"。

en-us	Cannot update templates on discovered host "%1$s".
zh-cn	对于被自动发现的主机 "%1$s"无法更新其模板

en-us	Cannot update trigger
zh-cn	无法更新触发器

en-us	Cannot update trigger "%1$s": %2$s.
zh-cn	无法更新触发器 "%1$s": %2$s 

en-us	Cannot update trigger prototype
zh-cn	无法更新触发器模板

en-us	Cannot update trigger prototype "%1$s": %2$s.
zh-cn	无法更新触发器模板 "%1$s": %2$s。

en-us	Cannot update trigger prototypes
zh-cn	无法更新触发器模板

en-us	Cannot update user
zh-cn	无法更新用户

en-us	Cannot update user. Both passwords must be equal.
zh-cn	无法更新用户。两次输入的密码必须一致。

en-us	Cannot update value map
zh-cn	无法更新值映射

en-us	Cannot update web scenario
zh-cn	无法更新 web 场景

en-us	Cannot validate discovery check: invalid request or connection to Zabbix server failed.
zh-cn	不可用的发现检查：请求不合法或连接到Zabbix服务器失败.

en-us	Case sensitive
zh-cn	区分大小写

en-us	Case sensitive login
zh-cn	登录区分大小写

en-us	Catalan (ca_ES)
zh-cn	加泰罗尼亚（ca_ES）

en-us	Catches all SNMP traps that match regex. If regexp is unspecified, catches any trap.
zh-cn	采集所有符合规则的 SNMP 信息，如果没有规则则会采集所有信息。

en-us	Catches all SNMP traps that were not caught by any of snmptrap[] items.
zh-cn	采集所有SNMP traps规则以外的snmptrap[]

en-us	Centre
zh-cn	居中

en-us	CERT
zh-cn	CERT

en-us	Certificate
zh-cn	证书

en-us	Change
zh-cn	更改

en-us	Change
zh-cn	更改

en-us	change() - Difference between last and previous value
zh-cn	change() - 最新值和前一个值的差异

en-us	Change password
zh-cn	修改密码

en-us	Change per second
zh-cn	每秒更改

en-us	Change severity
zh-cn	更改严重性

en-us	Character
zh-cn	字符

en-us	Character string included
zh-cn	字符串已包含

en-us	Character string not included
zh-cn	字符串未包含

en-us	Chassis
zh-cn	机壳

en-us	Chassis information. Returns string
zh-cn	机架信息。返回字符串

en-us	Check already exists.
zh-cn	检查已存在.

en-us	Check expression part starting from "%1$s".
zh-cn	检查开始于"%1$s"的表达式部份.

en-us	check expression starting from "%1$s"
zh-cn	检查表达式从"%1$s"开始

en-us	Check now
zh-cn	现在检查

en-us	Check of pre-requisites
zh-cn	必要条件检测

en-us	Checks
zh-cn	检查 

en-us	Checks if DNS service is up. Returns 0 - DNS is down (server did not respond or DNS resolution failed); 1 - DNS is up
zh-cn	检查 DNS 服务是否开启。返回 0 - DNS 服务关闭（服务未响应或DNS解析失败）；1 - DNS 服务开启

en-us	Checks if file exists. Returns 0 - not found; 1 - regular file or a link (symbolic or hard) to regular file exists
zh-cn	检查文件是否存在。返回 0 - 未找到文件；1 - 常规文件或链接（软/硬）存在

en-us	Checks if it is possible to make TCP connection to specified port. Returns 0 - cannot connect; 1 - can connect
zh-cn	检查是否能建立 TCP 连接到指定端口。返回 0 - 不能连接；1 - 可以连接

en-us	Checks if service is running and accepting TCP connections. Returns 0 - service is down; 1 - service is running
zh-cn	检查服务是否运行并接受 TCP 连接。返回 0 - 服务关闭；1 - 服务运行

en-us	Checks if service is running and responding to UDP requests. Returns 0 - service is down; 1 - service is running
zh-cn	检查服务是否运行并响应 UDP 请求。返回 0 - 服务关闭；1 - 服务运行

en-us	Checks if this TCP port is in LISTEN state. Returns 0 - it is not in LISTEN state; 1 - it is in LISTEN state
zh-cn	检查 TCP 端口 是否处于侦听状态。返回 0 - 未侦听；1 - 正在侦听

en-us	Checks if this UDP port is in LISTEN state. Returns 0 - it is not in LISTEN state; 1 - it is in LISTEN state
zh-cn	检查 UDP 端口 是否处于侦听状态。返回 0 - 未侦听；1 - 正在侦听

en-us	Checks performance of TCP service. Returns 0 - service is down; seconds - the number of seconds spent while connecting to the service
zh-cn	检查 TCP 服务的性能，当服务 down 时返回 0，否则返回连接服务花费的秒数

en-us	Checks performance of UDP service. Returns 0 - service is down; seconds - the number of seconds spent waiting for response from the service
zh-cn	检查 UDP 服务的性能，当服务 down 时返回 0，否则返回连接到服务花费的秒数

en-us	Checks should be unique.
zh-cn	检查必需是唯一的

en-us	Check the key, please. Default example was passed.
zh-cn	请检查键值。使用了默认的示例。

en-us	Check type
zh-cn	检查类型

en-us	Chinese (zh_CN)
zh-cn	中文 (zh_CN)

en-us	Chinese (zh_TW)
zh-cn	中文 (zh_TW)

en-us	#### Ciphersuites  Ciphersuites by default are configured internally during Zabbix startup and, before Zabbix 4.0.19, 4.4.7, are not user-configurable.  Since Zabbix 4.0.19, 4.4.7 also user-configured ciphersuites are supported for GnuTLS and OpenSSL. Users may [configure](#user-configured_ciphersuites) ciphersuites according to their security policies. Using this feature is optional (built-in default ciphersuites still work).  For crypto libraries compiled with default settings Zabbix built-in rules typically result in the following ciphersuites (in order from higher to lower priority):  |Library|Certificate ciphersuites|PSK ciphersuites| |-------|-------------------|-------------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA|
zh-cn	#### 密码套件  默认情况下，密码套件是在Zabbix启动期间内部配置的，在Zabbix 4.0.19和4.4.7之前是不能由用户配置的。  从Zabbix 4.0.19，4.4.7开始也支持GnuTLS和OpenSSL用户配置的密码套件。用户可以根据他们的安全策略[配置](#user-configured_ciphersuites)密码套件。使用这个特性是可选的(内置的默认密码套件仍然可以使用)。  对于使用默认设置编译的加密库，Zabbix内置规则通常会导致以下加密套件(按优先级由高到低的顺序):  |库|证书密码套件|PSK密码套件| |-------|------------------------|----------------| |*GnuTLS 3.1.18*|TLS\_ECDHE\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_RSA\_AES\_128\_CBC\_SHA1<br>TLS\_RSA\_AES\_128\_GCM\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA256<br>TLS\_RSA\_AES\_128\_CBC\_SHA1|TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_ECDHE\_PSK\_AES\_128\_CBC\_SHA1<br>TLS\_PSK\_AES\_128\_GCM\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA256<br>TLS\_PSK\_AES\_128\_CBC\_SHA1| |*OpenSSL 1.0.2c*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-SHA256<br>AES128-SHA|PSK-AES128-CBC-SHA| |*OpenSSL 1.1.0*|ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA<br>|ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA| |*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384<br>TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-RSA-AES128-GCM-SHA256<br>ECDHE-RSA-AES128-SHA256<br>ECDHE-RSA-AES128-SHA<br>AES128-GCM-SHA256<br>AES128-CCM8<br>AES128-CCM<br>AES128-SHA256<br>AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256<br>TLS\_AES\_128\_GCM\_SHA256<br>ECDHE-PSK-AES128-CBC-SHA256<br>ECDHE-PSK-AES128-CBC-SHA<br>PSK-AES128-GCM-SHA256<br>PSK-AES128-CCM8<br>PSK-AES128-CCM<br>PSK-AES128-CBC-SHA256<br>PSK-AES128-CBC-SHA|

en-us	circular item dependency is not allowed
zh-cn	不允许循环项依赖

en-us	Circular reference in screens: %1$s.
zh-cn	聚合图形 %1$s 存在环形引用。

en-us	Circular reference in templates: %1$s.
zh-cn	模板 %1$s 存在环形引用。

en-us	Circular template linkage is not allowed.
zh-cn	不允许环形模板链接.

en-us	Clear
zh-cn	清除

en-us	Clear history
zh-cn	清除历史

en-us	Clear history and trends
zh-cn	清除历史和趋势

en-us	Clear when unlinking
zh-cn	清除当无链接时

en-us	Clock
zh-cn	时钟

en-us	Clone
zh-cn	克隆

en-us	Close
zh-cn	关闭

en-us	Close expression constructor
zh-cn	关闭表达式构造器

en-us	Close new event
zh-cn	关闭新的事件

en-us	Close old events
zh-cn	关闭过去的事件

en-us	Close problem
zh-cn	关闭问题

en-us	CLOSING
zh-cn	关闭中

en-us	Collapse
zh-cn	宕机

en-us	colour
zh-cn	颜色

en-us	Colour
zh-cn	颜色

en-us	Colour "%1$s" is not correct: expecting hexadecimal colour code (6 symbols).
zh-cn	颜色 "%1$s" 是错误的: 期望十六进制的颜色代码(6 个符号).

en-us	Colour (OK)
zh-cn	颜色 (OK)

en-us	Column added
zh-cn	列已添加

en-us	Column deleted
zh-cn	列已删除

en-us	Columns
zh-cn	列数

en-us	Column span
zh-cn	列跨度

en-us	Combined result
zh-cn	合并的结果

en-us	Command
zh-cn	命令

en-us	Commands
zh-cn	命令

en-us	comma-separated list
zh-cn	以逗号分隔的列表

en-us	Commercial
zh-cn	商业的

en-us	Compact view
zh-cn	紧凑视图

en-us	Comparing several triggers with "and" is not allowed.
zh-cn	不能比较触发器之间的和。

en-us	Compression
zh-cn	压缩

en-us	Concurrent sessions
zh-cn	并发会话

en-us	Condition
zh-cn	条件

en-us	Condition "%2$s" is not used in formula "%3$s" for action "%1$s".
zh-cn	对于动作"%1$s"条件"%2$s"不可以应用于计算式"%3$s"中

en-us	Condition "%2$s" is not used in formula "%3$s" for correlation "%1$s".
zh-cn	在关联"%1$s"中，条件"%2$s"无法使用公式 "%3$s" 

en-us	Condition "%2$s" is not used in formula "%3$s" for discovery rule "%1$s".
zh-cn	对于自动发现规则"%1$s"条件"%2$s"不可以应用于计算式"%3$s"中

en-us	Condition "%2$s" used in formula "%3$s" for action "%1$s" is not defined.
zh-cn	对于动作"%1$s"应用于计算式 "%3$s"中的"%2$s"条件未被定义

en-us	Condition "%2$s" used in formula "%3$s" for correlation "%1$s" is not defined.
zh-cn	在关联项 "%1$s" 中 条件 "%2$s" 在表达式 "%3$s"没有被使用

en-us	Condition "%2$s" used in formula "%3$s" for discovery rule "%1$s" is not defined.
zh-cn	对于自动发现规则"%1$s"应用于计算表达式 "%3$s"中的条件 "%2$s"未被定义

en-us	Conditions
zh-cn	条件

en-us	Conditions duplicates for correlation "%1$s".
zh-cn	条件复制关联项 "%1$s"。

en-us	Configuration
zh-cn	配置

en-us	Configuration cache statistics. Cache - buffer (modes: pfree, total, used, free).
zh-cn	配置缓存统计.缓存—缓冲(模式：空闲的百分数，总计，已使用，未使用

en-us	Configuration file "%1$s" created.
zh-cn	配置文件 "%1$s" 已创建。

en-us	Configuration import
zh-cn	配置导入

en-us	Configuration of actions
zh-cn	动作的配置

en-us	Configuration of applications
zh-cn	应用集的配置

en-us	Configuration of authentication
zh-cn	配置身份验证

en-us	Configuration of discovery rules
zh-cn	配置发现规则

en-us	Configuration of graph prototypes
zh-cn	配置图形原型

en-us	Configuration of graphs
zh-cn	配置图标

en-us	Configuration of GUI
zh-cn	图形接口的配置

en-us	Configuration of host groups
zh-cn	配置主机群组

en-us	Configuration of host prototypes
zh-cn	配置主机原型

en-us	Configuration of hosts
zh-cn	配置主机

en-us	Configuration of housekeeping
zh-cn	管家设置

en-us	Configuration of icon mapping
zh-cn	配置图标映射

en-us	Configuration of images
zh-cn	配置图像

en-us	Configuration of item prototypes
zh-cn	配置监控项原型

en-us	Configuration of items
zh-cn	配置监控项

en-us	Configuration of macros
zh-cn	配置宏

en-us	Configuration of maintenance periods
zh-cn	配置维护时段

en-us	Configuration of media types
zh-cn	配置媒体类型

en-us	Configuration of network maps
zh-cn	配置网络地图

en-us	Configuration of proxies
zh-cn	配置代理

en-us	Configuration of regular expressions
zh-cn	配置正则表达式

en-us	Configuration of screens
zh-cn	配置聚合图形

en-us	Configuration of scripts
zh-cn	配置脚本

en-us	Configuration of services
zh-cn	配置服务

en-us	Configuration of slide shows
zh-cn	配置幻灯片显示

en-us	Configuration of templates
zh-cn	配置模板

en-us	Configuration of trigger displaying options
zh-cn	配置触发器显示选项

en-us	Configuration of trigger prototypes
zh-cn	配置触发器原型

en-us	Configuration of triggers
zh-cn	配置触发器

en-us	Configuration of trigger severities
zh-cn	配置触发器严重级别

en-us	Configuration of user groups
zh-cn	配置用户组

en-us	Configuration of users
zh-cn	配置用户

en-us	Configuration of value mapping
zh-cn	配置值映射

en-us	Configuration of web monitoring
zh-cn	配置 web 监控

en-us	Configuration of working time
zh-cn	配置工作时间

en-us	Configuration of Zabbix
zh-cn	Zabbix的配置

en-us	#### Configuration  To configure a maintenance period:  -   Go to: *Configuration → Maintenance* -   Click on *Create maintenance period* (or on the name of an existing     maintenance period) -   Enter maintenance parameters in the form  ![](../../assets/en/manual/maintenance/maintenance.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|Description| |-----|-------------------| |*Name*|Name of the maintenance period.| |*Maintenance type*|Two types of maintenance can be set:<br>**With data collection** - data will be collected by the server during maintenance, triggers will be processed<br>**No data collection** - data will not be collected by the server during maintenance| |*Active since*|The date and time when executing maintenance periods becomes active.<br>*Note*: Setting this time alone does not activate a maintenance period; for that go to the *Periods* tab.| |*Active till*|The date and time when executing maintenance periods stops being active.| |*Periods*|This block allows you to define the exact days and hours when the maintenance takes place. Clicking on ![](../../assets/en/manual/maintenance/add_link.png) opens a popup window with a flexible *Maintenance period* form where you can define maintenance schedule. See [Maintenance periods](#maintenance_periods) for a detailed description.| |*Host groups*|Select host groups that the maintenance will be activated for. The maintenance will be activated for all hosts from the specified host group(s). This field is auto-complete, so starting to type in it will display a dropdown of all available host groups.<br>Specifying a parent host group implicitly selects all nested host groups. Thus the maintenance will also be activated on hosts from nested groups.| |*Hosts*|Select hosts that the maintenance will be activated for. This field is auto-complete, so starting to type in it will display a dropdown of all available hosts.<br>| |*Tags*|If maintenance tags are specified, maintenance for the selected hosts will be activated, but only problems with matching tags will be suppressed (i.e. no actions will be taken).<br>In case of multiple tags, they are calculated as follows:<br>**And/Or** - all tags must correspond; however tags with the same tag name are calculated by the Or condition<br>**Or** - enough if one tag corresponds<br>There are two ways of matching the tag value:<br>**Contains** - case-sensitive substring match (tag value contains the entered string)<br>**Equals** - case-sensitive string match (tag value equals the entered string) <br> Tags can be specified only if *With data collection* mode is selected.| |*Description*|Description of maintenance period.|
zh-cn	#### 配置  配置维护期有以下操作步骤：  -   转到：*配置（Configuration） → 维护（Maintenance）* -   单击创建维护期（或现有维护期的名称） -   在表格中输入维护参数  ![](../../assets/en/manual/maintenance/maintenance.png)  所有必填字段都标有红色星号。  |参数|描述| |---------|-----------| |*名字（Name）*|维护期的名称。| |*维护类型（Maintenance type）*|可以设置两种维护方式：<br>**有数据采集（With data collection）** - 维护时服务器采集数据，处理触发器 <br>**无数据采集（No data collection）** - 维护时服务器不采集数据| |*启用自从（Active since）*|执行维护期的日期和时间变为活动状态。<br>*注意*：单独设置此时间不会激活维护期；为此，请转到*期间（Periods）*选项卡| |*启用直到（Active till）*|执行维护期停止活动的日期和时间。| |*时期（Periods）*|此块允许您定义进行维护的确切日期和时间。单击 ![](../../assets/en/manual/maintenance/add_link.png) 会打开一个弹窗，其中包含灵活的 * 维护期表单*，您可以在其中定义维护计划。有关详细说明，请参阅[维护期](#maintenance_periods)。| |*主机组（Host groups）*|选择将为其激活维护的主机组。将为指定主机组中的所有主机激活维护。此字段是自动完成的，因此开始输入它将显示所有可用主机组的下拉列表。<br>指定父主机组会隐式选择所有嵌套主机组。因此，维护也将在嵌套组的主机上激活。| |*主机（Hosts）*|选择将为其激活维护的主机。此字段是自动完成的，因此输入它将显示所有可用主机的下拉列表。<br>| |*标签（Tags）*|如果指定了维护标签，对选定主机的维护仍将被激活，但只有当它们的标签匹配时才会抑制问题（即不采取任何措施）。<br>如果有多个标签，则计算如下：<br>**And/Or** - 所有标签必须对应；但是标签名相同的标签由 Or 条件计算<br>**Or** - 一个标签对应即可<br>匹配标签值有两种方式：<br>**Contains** - 区分大小写的子字符串匹配（标签值包含输入的字符串）<br>**Equals** - 区分大小写字符串匹配（标签值等于输入的字符串）| |*描述（Description）*|维护期说明。|

en-us	Configuration updated
zh-cn	配置已更新

en-us	configure
zh-cn	配置

en-us	Configure DB connection
zh-cn	配置DB连接

en-us	Confirmation text
zh-cn	确认文字

en-us	Congratulations! You have successfully installed Zabbix frontend.
zh-cn	恩！不错zabbix前端已经配置好了！千山万水第一步！加油，少年！

en-us	Connected
zh-cn	已连接

en-us	#### Connection encryption management  Connections in Zabbix can use:  -   no encryption (default) -   [RSA certificate-based     encryption](/manual/encryption/using_certificates) -   [PSK-based encryption](/manual/encryption/using_pre_shared_keys)  There are two important parameters used to specify encryption between Zabbix components:  -   TLSConnect - specifies what encryption to use for outgoing     connections (unencrypted, PSK or certificate) -   TLSAccept - specifies what types of connections are allowed for     incoming connections (unencrypted, PSK or certificate). One or more     values can be specified.  `TLSConnect` is used in the configuration files for Zabbix proxy (in active mode, specifies only connections to server) and Zabbix agent (for active checks). In Zabbix frontend the TLSConnect equivalent is the *Connections to host* field in *Configuration → Hosts → <some host> → Encryption* tab and the *Connections to proxy* field in *Administration → Proxies → <some proxy> → Encryption* tab. If the configured encryption type for connection fails, no other encryption types will be tried.  `TLSAccept` is used in the configuration files for Zabbix proxy (in passive mode, specifies only connections from server) and Zabbix agent (for passive checks). In Zabbix frontend the TLSAccept equivalent is the *Connections from host* field in *Configuration → Hosts → <some host> → Encryption* tab and the *Connections from proxy* field in *Administration → Proxies → <some proxy> → Encryption* tab.  Normally you configure only one type of encryption for incoming encryptions. But you may want to switch the encryption type, e.g. from unencrypted to certificate-based with minimum downtime and rollback possibility. To achieve this:  -   Set `TLSAccept=unencrypted,cert` in the agent configuration file and     restart Zabbix agent -   Test connection with zabbix\_get to the agent using certificate. If     it works, you can reconfigure encryption for that agent in Zabbix     frontend in the *Configuration → Hosts → <some host> →     Encryption* tab by setting *Connections to host* to "Certificate". -   When server configuration cache gets updated (and proxy     configuration is updated if the host is monitored by proxy) then     connections to that agent will be encrypted -   If everything works as expected you can set `TLSAccept=cert` in the     agent configuration file and restart Zabbix agent. Now the agent     will be accepting only encrypted certificate-based connections.     Unencrypted and PSK-based connections will be rejected.  In a similar way it works on server and proxy. If in Zabbix frontend in host configuration *Connections from host* is set to "Certificate" then only certificate-based encrypted connections will be accepted from the agent (active checks) and zabbix\_sender (trapper items).  Most likely you will configure incoming and outgoing connections to use the same encryption type or no encryption at all. But technically it is possible to configure it asymmetrically, e.g. certificate-based encryption for incoming and PSK-based for outgoing connections.  Encryption configuration for each host is displayed in the Zabbix frontend, in *Configuration → Hosts* in the *Agent encryption* column. For example:  |Example|Connections to host|Allowed connections from host|Rejected connections from host| |-------|-------------------|-------------------|-------------------| |![none\_none.png](../../assets/en/manual/encryption/none_none.png)|Unencrypted|Unencrypted|Encrypted, certificate and PSK-based encrypted| |![cert\_cert.png](../../assets/en/manual/encryption/cert_cert.png)|Encrypted, certificate-based|Encrypted, certificate-based|Unencrypted and PSK-based encrypted| |![psk\_psk.png](../../assets/en/manual/encryption/psk_psk.png)|Encrypted, PSK-based|Encrypted, PSK-based|Unencrypted and certificate-based encrypted| |![psk\_none\_psk.png](../../assets/en/manual/encryption/psk_none_psk.png)|Encrypted, PSK-based|Unencrypted and PSK-based encrypted|Certificate-based encrypted| |![cert\_all.png](../../assets/en/manual/encryption/cert_all.png)|Encrypted, certificate-based|Unencrypted, PSK or certificate-based encrypted|\-|  ::: noteimportant Connections are unencrypted by default. Encryption must be configured for each host and proxy individually. :::
zh-cn	 ####  连接加密管理  Zabbix中的连接可以使用：  -   不加密 (默认) -   [基于RSA证书的加密](/manual/encryption/using_certificates) -   [基于PSK基础加密](/manual/encryption/using_pre_shared_keys)  有两个重要的参数用于指定之间的加密Zabbix组件:  -   TLSConnect -指定对传出连接使用何种加密(未加密、PSK或证书) -   TLSAccept - 指定允许传入连接的类型(未加密的，PSK或证书)。 可以指定一个或多个值。  `TLSConnect` 在Zabbix proxy(在主动模式下，仅指定到server的连接)和Zabbix agent(在主动检查中)的配置文件中使用。在Zabbix前端TLSConnect等效的是*配置→主机→<一些主机>→加密*标签中的*连接到主机*字段和*管理→Proxy代理→<一些proxy代理>→加密*标签中的*连接到proxy*字段。如果为连接配置的加密类型失败，则不会尝试其他加密类型。  `TLSAccept` 在Zabbix proxy(被动模式，仅指定来自server的连接)和Zabbix agent(被动检查)的配置文件中使用。在Zabbix前端TLSAccept等价的是*配置→主机→<一些主机>→加密*标签中的*主机连接*字段和*管理→proxy代理→<一些proxy代理>→加密*标签中的*proxy连接*字段。  通常您只为传入加密配置一种类型的加密。 但您可能希望切换加密类型，例如，从未加密切换到基于证书的加密，并尽可能减少停机时间和回滚可能性。 为实现这一目标:  -   设置 `TLSAccept=unencrypted,cert` 在agent配置文件中设置，重启Zabbix agent -   使用证书测试zabbix\_get到agent的连接。如果它能工作，你可以在Zabbix前端的*Configuration→Hosts→<some host>→encryption *选项卡中通过将*Connections to host*设置为“Certificate”来重新配置该agent的加密。 -   当server配置缓存被更新时(如果主机被proxy监视，则proxy配置被更新)，那么到该proxy的连接将被加密 -   如果一切正常，您可以在agent配置文件中设置' TLSAccept=cert '，并重启Zabbix agent。现在agent将只接受加密的基于证书的连接。 未加密的和基于psk的连接将被拒绝。  以类似的方式，它在server和proxy上工作。 如果在Zabbix前端主机配置*来自主机的连接*设置为“证书”，那么只有基于证书的加密连接将被接受从agent(主动检查)和Zabbix\_sender(trapper监控项)。  最可能的情况是将传入和传出连接配置为使用相同的加密类型或完全不加密。 但在技术上，可以不对称地配置它，例如，对传入连接进行基于证书的加密，对传出连接进行基于psk的加密。  Zabbix前端“*Agent加密*”列的“*配置→主机*”中显示各主机的加密配置信息。 例如:  |例子|连接到主机|允许连接的主机|拒绝连接的主机| |-------|-------------------|-----------------------------|------------------------------| |![none\_none.png](../../assets/en/manual/encryption/none_none.png)|非加密的|非加密的|加密，证书和psk加密| |![cert\_cert.png](../../assets/en/manual/encryption/cert_cert.png)|加密的,基于证书|加密的, 基于证书|加密的基于PSK| |![psk\_psk.png](../../assets/en/manual/encryption/psk_psk.png)|加密的, 基于PSK|加密的, 基于PSK|非加密的基于证书加密的| |![psk\_none\_psk.png](../../assets/en/manual/encryption/psk_none_psk.png)|加密的, 基于PSK|非加密和基于PSK加密|基于证书加密| |![cert\_all.png](../../assets/en/manual/encryption/cert_all.png)|加密, 证书加密|未加密, PSK或者or基于证书加密|\-|  :: noteimportant 默认情况下，连接是不加密的。如果使用加密那么必须分别为每个主机和proxy配置加密。 :::

en-us	Connections
zh-cn	链接

en-us	Connection security
zh-cn	安全链接

en-us	Connections from host
zh-cn	从主机连接

en-us	Connections from proxy
zh-cn	从代理连接

en-us	Connections to host
zh-cn	连接主机

en-us	Connections to proxy
zh-cn	连接代理

en-us	Connection timeout of %1$s seconds exceeded when connecting to Zabbix server "%2$s".
zh-cn	连接超时 %1$s 秒超出当连接Zabbix 服务器 "%2$s".

en-us	Connection to Zabbix server "%s" failed. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Incorrect DNS server configuration. 
zh-cn	连接到Zabbix主机 "%s" 失败. 可能的原因是: 1. 错误的 IP/DNS 设于 "zabbix.conf.php"; 2. 错误的 DNS 主机配置. 

en-us	Connection to Zabbix server "%s" refused. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. 
zh-cn	连接到Zabbix主机 "%s" 被拒绝。可能的原因是: 1. "zabbix.conf.php" 中错误的 IP/DNS 设置； 2. 安全环境 (例如, SELinux) 阻断了连接； 3. Zabbix 主机的服务未运行； 4. 防火墙阻断了 TCP 连接。 

en-us	Connection to Zabbix server "%s" timed out. Possible reasons: 1. Incorrect server IP/DNS in the "zabbix.conf.php"; 2. Firewall is blocking TCP connection. 
zh-cn	连接到 Zabbix 主机 "%s" 超时。可能的原因是： 1. "zabbix.conf.php" 中错误的 IP/DNS 设置； 2. 防火牆阻断了TCP连接。 

en-us	Connect to
zh-cn	连接到

en-us	Constructor
zh-cn	构造函数

en-us	Contact
zh-cn	联系

en-us	contains
zh-cn	包含

en-us	Contains
zh-cn	包含

en-us	Content controls
zh-cn	内容控制

en-us	Content menu
zh-cn	内容菜单

en-us	Context name
zh-cn	上下文名称

en-us	Contract number
zh-cn	合同号码

en-us	Convert to JSON
zh-cn	转换到 JSON

en-us	Coordinates
zh-cn	座标

en-us	Copy
zh-cn	复制

en-us	Correlation
zh-cn	相关性

en-us	Correlation "%1$s" already exists.
zh-cn	关联项 "%1$s" 已经存在

en-us	Correlation added
zh-cn	关联项添加

en-us	Correlation deleted
zh-cn	删除关联项

en-us	Correlation deleted
zh-cn	删除关联项

en-us	Correlation disabled
zh-cn	禁用关联项

en-us	Correlation enabled
zh-cn	启用关联项

en-us	Correlation is missing parameters: %1$s
zh-cn	%1$s找不到关联项参数

en-us	Correlation name cannot be empty.
zh-cn	关联项名字不能为空。

en-us	Correlation rule
zh-cn	关联规则

en-us	Correlation updated
zh-cn	关联项已更新

en-us	Could not save image!
zh-cn	不能储存图片!

en-us	Count
zh-cn	计数

en-us	count() - Number of successfully retrieved values V (which fulfill operator O) for period T
zh-cn	count() - 对于周期 T，成功检索的值 V（其满足运算符 O）的数量

en-us	Count of context switches. Returns integer
zh-cn	上下文的数量进行切换。它返回一个整数值。

en-us	Count of directory entries, recursively. Returns integer
zh-cn	目录递归的条目数量。返回整数

en-us	Count of matched lines in log file monitoring. Returns integer
zh-cn	监控日志文件行数统计。返回 整数

en-us	Count of matched lines in log file monitoring with log rotation support. Returns integer
zh-cn	日志文件监视中匹配行的计数与日志轮换支持。 返回整型

en-us	CPU information. Returns string or integer
zh-cn	CPU 信息。返回字符串或整数

en-us	CPU load. Returns float
zh-cn	CPU 负载。返回浮点数

en-us	CPU utilisation percentage. Returns float
zh-cn	CPU 使用率。返回浮点数

en-us	Create action
zh-cn	创建动作

en-us	Create application
zh-cn	创建应用集

en-us	Create application (select host first)
zh-cn	创建应用程序 (先选择主机)

en-us	Create background
zh-cn	创建背景

en-us	Create correlation
zh-cn	创建关联项

en-us	Create dashboard
zh-cn	创建仪表盘

en-us	Create dependent item
zh-cn	创建仪表盘依赖项

en-us	Create disabled
zh-cn	禁止创建

en-us	Create discovery rule
zh-cn	创建发现规则

en-us	Create enabled
zh-cn	启用新的

en-us	Create graph
zh-cn	创建图形

en-us	Create graph prototype
zh-cn	创建图形原型

en-us	Create graph (select host first)
zh-cn	创建图形(先选择主机)

en-us	Create host
zh-cn	创建主机

en-us	Create host group
zh-cn	创建主机群组

en-us	Create host prototype
zh-cn	创建主机模板

en-us	Create hosts from selected prototypes as disabled?
zh-cn	您是否要从所选原型中禁用主机并创建它？

en-us	Create hosts from selected prototypes as enabled?
zh-cn	您是否要在启用所选原型的情况下创建主机？

en-us	Create icon
zh-cn	创建图标

en-us	Create icon map
zh-cn	创建图标映射

en-us	Create item
zh-cn	创建监控项

en-us	Create item prototype
zh-cn	创建监控项原型

en-us	Create item (select host first)
zh-cn	创建监控项(先选择主机)

en-us	Create items from selected prototypes as disabled?
zh-cn	您想通过使所选原型中的禁用监控项来创建项目吗？

en-us	Create items from selected prototypes as enabled?
zh-cn	您想通过使所选原型中的启用项目来创建项目吗？

en-us	Create maintenance period
zh-cn	创建维护期间

en-us	Create map
zh-cn	创建拓扑图

en-us	Create media type
zh-cn	创建媒体类型

en-us	Create new
zh-cn	创建新的

en-us	Create proxy
zh-cn	创建代理

en-us	Create screen
zh-cn	创建聚合图形

en-us	Create script
zh-cn	创建脚本

en-us	Create slide show
zh-cn	创建幻灯片播放

en-us	Create template
zh-cn	创建模板

en-us	Create trigger
zh-cn	创建触发器

en-us	Create trigger prototype
zh-cn	创建触发器原型

en-us	Create trigger (select host first)
zh-cn	创建触发器(先选择主机)

en-us	Create triggers from selected prototypes as disabled?
zh-cn	您是否要禁用所选原型的触发器并创建它？

en-us	Create triggers from selected prototypes as enabled?
zh-cn	您是否要启用所选原型的触发器并创建它？

en-us	Create user
zh-cn	创建用户

en-us	Create user group
zh-cn	创建用户群组

en-us	Create value map
zh-cn	创建值映射

en-us	Create web scenario
zh-cn	创建 Web 场景

en-us	Create web scenario (select host first)
zh-cn	创建 Web 场景（首先选择主机）

en-us	Critical
zh-cn	严重

en-us	Current host
zh-cn	当前主机

en-us	Current value
zh-cn	当前值

en-us	Custom
zh-cn	习惯

en-us	Custom expression
zh-cn	自定义表达式

en-us	Custom graphs
zh-cn	自定义图表

en-us	Custom intervals
zh-cn	自定义时间间隔

en-us	Custom label
zh-cn	自定义标签

en-us	Custom label for map "%2$s" elements of type "%1$s" may not be empty.
zh-cn	自定义标签地图 "%2$s" 类型元素 "%1$s" 不能为空.

en-us	Custom multiplier
zh-cn	自定义倍数

en-us	Custom screens
zh-cn	自定义聚合图形

en-us	Custom script
zh-cn	自定义脚本

en-us	Custom severity names affect all locales and require manual translation!
zh-cn	自定义的严重性的名称影响所有的语系而必须手动翻译!

en-us	Custom size
zh-cn	自定义大小

en-us	Custom slides
zh-cn	自定义幻灯片

en-us	Czech (cs_CZ)
zh-cn	捷克(cs_CZ)

en-us	d
zh-cn	d

en-us	Daily
zh-cn	每日

en-us	Dark
zh-cn	暗色

en-us	Dashboard
zh-cn	仪表板

en-us	Dashboard "%1$s" already exists.
zh-cn	仪表盘 "%1$s" 已经存在。

en-us	Dashboard "%1$s" cell X - %2$s Y - %3$s is already taken.
zh-cn	仪表板 "%1$s" 单元格X - %2$s Y - %3$s 已被占用。

en-us	Dashboard "%1$s" widget in cell X - %2$s Y - %3$s is out of bounds.
zh-cn	单元格X - %2$s Y - %3$s 控制台 "%1$s" 的小部件超出范围。

en-us	Dashboard created
zh-cn	仪表盘创建成功。

en-us	Dashboard deleted
zh-cn	仪表板已删除

en-us	Dashboard properties
zh-cn	仪表板属性

en-us	Dashboards
zh-cn	仪表盘

en-us	Dashboard sharing
zh-cn	共享仪表盘

en-us	Dashboard updated
zh-cn	更新仪表盘

en-us	Dashed line
zh-cn	虚线

en-us	Data
zh-cn	数据

en-us	Database host
zh-cn	数据库主机

en-us	Database monitor
zh-cn	数据库监控

en-us	Database name
zh-cn	数据库名称

en-us	Database password
zh-cn	数据库密码

en-us	Database port
zh-cn	数据库端口

en-us	Database schema
zh-cn	数据库概要

en-us	Database server
zh-cn	数据库服务器

en-us	Database type
zh-cn	数据库类型

en-us	Database user
zh-cn	数据库用户

en-us	Data from %1$s. Generated in %2$s sec.
zh-cn	数据来自 %1$s. 产生于 %2$s 秒.

en-us	Data is not properly encoded.
zh-cn	数据不正确的编码。

en-us	Data overview
zh-cn	数据概览

en-us	Data set
zh-cn	数据设置

en-us	Data storage period
zh-cn	数据存储期

en-us	Date
zh-cn	日期

en-us	date() - Current date
zh-cn	date() - 当前日期

en-us	Date HW decommissioned
zh-cn	硬件退役日期

en-us	Date HW installed
zh-cn	硬件安装日期

en-us	Date HW maintenance expires
zh-cn	硬件维修过期日期

en-us	Date HW purchased
zh-cn	硬件购买日期

en-us	Day
zh-cn	日

en-us	Day before yesterday
zh-cn	前天

en-us	Day of month
zh-cn	月中第几日

en-us	dayofmonth() - Day of month
zh-cn	dayofmonth() - 当前是本月的第几天

en-us	Day of week
zh-cn	星期几

en-us	dayofweek() - Day of week
zh-cn	dayofweek() - 当前是本周的第几天

en-us	days
zh-cn	日

en-us	Days
zh-cn	天数

en-us	%d device
zh-cn	%d个设备

en-us	DD.MM.YY
zh-cn	DD.MM.YY

en-us	Debug
zh-cn	调试

en-us	Debug mode
zh-cn	调试模式

en-us	Debug mode updated
zh-cn	调试模式已更新

en-us	Dec
zh-cn	十二

en-us	December
zh-cn	十二

en-us	default
zh-cn	默认的

en-us	Default
zh-cn	默认

en-us	Default authentication
zh-cn	默认认证方式

en-us	Default delay
zh-cn	默认延迟

en-us	#### Default global regular expressions  Zabbix comes with several global regular expression in its default dataset.  |Name|Expression|Matches| |------|----------|-------| |*File systems for discovery*|`^(btrfs\|ext2\|ext3\|ext4\|jfs\|reiser\|xfs\|ffs\|ufs\|jfs\|jfs2\|vxfs\|hfs\|refs\|apfs\|ntfs\|fat32\|zfs)$`|"btrfs" or "ext2" or "ext3" or "ext4" or "jfs" or "reiser" or "xfs" or "ffs" or "ufs" or "jfs" or "jfs2" or "vxfs" or "hfs" or "refs" or "apfs" or "ntfs" or "fat32" or "zfs"| |*Network interfaces for discovery*|`^Software Loopback Interface`|Strings starting with "Software Loopback Interface".| |<|`^lo$`|"lo"| |<|`^(In)?[Ll]oop[Bb]ack[0-9._]*$`|Strings that optionally start with "In", then have "L" or "l", then "oop", then "B" or "b", then "ack", which can be optionally followed by any number of digits, dots or underscores.| |<|`^NULL[0-9.]*$`|Strings starting with "NULL" optionally followed by any number of digits or dots.| |<|`^[Ll]o[0-9.]*$`|Strings starting with "Lo" or "lo" and optionally followed by any number of digits or dots.| |<|`^[Ss]ystem$`|"System" or "system"| |<|`^Nu[0-9.]*$`|Strings starting with "Nu" optionally followed by any number of digits or dots.| |*Storage devices for SNMP discovery*|`^(Physical memory\|Virtual memory\|Memory buffers\|Cached memory\|Swap space)$`|"Physical memory" or "Virtual memory" or "Memory buffers" or "Cached memory" or "Swap space"| |*Windows service names for discovery*|`^(MMCSS\|gupdate\|SysmonLog\|clr_optimization_v2.0.50727_32\|clr_optimization_v4.0.30319_32)$`|"MMCSS" or "gupdate" or "SysmonLog" or strings like "clr\_optimization\_v2.0.50727\_32" and "clr\_optimization\_v4.0.30319\_32" where instead of dots you can put any character except newline.| |*Windows service startup states for discovery*|`^(automatic\|automatic delayed)$`|"automatic" or "automatic delayed"|
zh-cn	#### 默认全局正则表达式  Zabbix在其默认数据集中提供了几个全局正则表达式。  |名字|表达式|匹配结果| |----|----------|-------| |*用于发现的文件系统*|`^(btrfs\|ext2\|ext3\|ext4\|jfs\|reiser\|xfs\|ffs\|ufs\|jfs\|jfs2\|vxfs\|hfs\|refs\|apfs\|ntfs\|fat32\|zfs)$`|"btrfs" 或 "ext2" 或 "ext3" 或 "ext4" 或 "jfs" 或 "reiser" 或 "xfs" 或 "ffs" 或 "ufs" 或 "jfs" 或 "jfs2" 或 "vxfs" 或 "hfs" 或 "refs" 或 "apfs" 或 "ntfs" 或 "fat32" 或 "zfs"| |*用于发现的网络接口*|`^Software Loopback Interface`|以 "Software Loopback Interface（软件环回接口）" 开头的字符串。| |<|`^lo$`|"lo"| |<|`^(In)?[Ll]oop[Bb]ack[0-9._]*$`|以 "In" 为开头，接着是 "L" 或 "l"，然后是 "oop"，然后 "B" 或 "b"，再然后 "ack" 组合的字符串。可以选择后跟任意数量的数字、点或下划线。| |<|`^NULL[0-9.]*$`|以 "NULL" 开头的后可选地跟任意数量的数字或点的字符串。| |<|`^[Ll]o[0-9.]*$`|以 "Lo" 或 "lo" 开头的后跟任意数量的数字或点的字符串。| |<|`^[Ss]ystem$`|匹配 "System" 或 "system"。| |<|`^Nu[0-9.]*$`|以 "Nu" 开头的后可选地跟任意数量的数字或点的字符串。| |*用于 SNMP 发现的存储设备*|`^(Physical memory\|Virtual memory\|Memory buffers\|Cached memory\|Swap space)$`|"Physical memory" 或 "Virtual memory" 或 "Memory buffers" 或 "Cached memory" 或 "Swap space"。| |*用于发现的 Windows 服务名称*|`^(MMCSS\|gupdate\|SysmonLog\|clr_optimization_v2.0.50727_32\|clr_optimization_v4.0.30319_32)$`|"MMCSS" 或 "gupdate" 或 "SysmonLog" 或类似于 "clr\_optimization\_v2.0.50727\_32" 和 "clr\_optimization\_v4.0.30319\_32" 的除了换行符之外可以放置​​任何字符代替点的字符串。| |*用于发现的 Windows 服务启动状态*|`^(automatic\|automatic delayed)$`|"automatic（自动）" 或 "automatic delayed（自动延迟）"。|

en-us	Default host inventory mode
zh-cn	默认主机资产记录模式

en-us	Default login form
zh-cn	默认登录表格

en-us	Default media type
zh-cn	默认媒介类型

en-us	Default message
zh-cn	消息内容

en-us	Default operation step duration
zh-cn	默认操作步骤持续时间

en-us	Default subject
zh-cn	默认标题

en-us	Default theme
zh-cn	默认主题

en-us	Default theme "%1$s".
zh-cn	默认主题 "%1$s".

en-us	#### Default user roles  By default, Zabbix is configured with four user roles, which have a pre-defined set of permissions:  -   Admin role -   Guest role -   Super admin role -   User role  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  Default *Super admin role* cannot be modified or deleted, because at least one Super admin user with unlimited privileges must exist in Zabbix.  :::  Zabbix users with type Super admins and proper permissions can modify or delete existing roles or create new custom roles.  To create a new role, click on the *Create user role* button at the top right corner. To update an existing role, press on the role name to open the configuration form.  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Available permission options along with default permission sets for pre-configured user roles in Zabbix are described below.  |Parameter|Description|Default user roles|<|<|<| |---------|-----------|------------------|-|-|-| | | |Super admin role|Admin role|User role|Guest role| |Name|Role visible name.|Super admin role|Admin role|User role|Guest role| |User type|Selected user type determines the list of available permissions.<br>Upon selecting a user type, all available permissions for this user type are granted by default.<br>Uncheck the checkbox(es) to revoke certain permissions for the user role.<br>Checkboxes for permissions not available for this user type are grayed out.|Super admin|Admin|User|User| |Access to UI elements|<|<|<|<|<| |*Monitoring*|<|<|<|<|<| |Dashboard|Enable/disable access to a specific Monitoring menu section and underlying pages.|Yes|Yes|Yes|Yes| |Problems|^|^|^|^|^| |Hosts|^|^|^|^|^| |Latest data|^|^|^|^|^| |Maps|^|^|^|^|^| |Discovery|^|^|^|No|No| |*Services*|<|<|<|<|<| |Services|Enable/disable access to a specific Services menu section and underlying pages.|Yes|Yes|Yes|Yes| |Service actions|^|^|^|No|No| |SLA|^|^|^|^|^| |SLA report|^|^|^|Yes|Yes| |*Inventory*|<|<|<|<|<| |Overview|Enable/disable access to a specific Inventory menu section and underlying pages.|Yes|Yes|Yes|Yes| |Hosts|^|^|^|^|^| |*Reports*|<|<|<|<|<| |System information|Enable/disable access to a specific Reports menu section and underlying pages.|Yes|No|No|No| |Availability report|^|^|Yes|Yes|Yes| |Triggers top 100|^|^|^|^|^| |Audit|^|^|No|No|No| |Action log|^|^|^|^|^| |Notifications|^|^|Yes|^|^| |Scheduled reports|^|^|^|^|^| |*Configuration*|<|<|<|<|<| |Host groups|Enable/disable access to a specific *Configuration* menu section and underlying pages.|Yes|Yes|No|No| |Templates|^|^|^|^|^| |Hosts|^|^|^|^|^| |Maintenance|^|^|^|^|^| |Actions|^|^|^|^|^| |Event correlation|^|^|No|^|^| |Discovery|^|^|Yes|^|^| |*Administration*|<|<|<|<|<| |General|Enable/disable access to a specific *Administration* menu section and underlying pages.|Yes|No|No|No| |Proxies|^|^|^|^|^| |Authentication|^|^|^|^|^| |User groups|^|^|^|^|^| |User roles|^|^|^|^|^| |Users|^|^|^|^|^| |Media types|^|^|^|^|^| |Scripts|^|^|^|^|^| |Queue|^|^|^|^|^| |*Default access to new UI elements*|Enable/disable access to the custom UI elements. Modules, if present, will be listed below.|Yes|Yes|Yes|Yes| |Access to services|<|<|<|<|<| |Read-write access to services|Select read-write access to services:<br>**None** - no access at all<br>**All** - access to all services is read-write<br>**Service list** - select services for read-write access<br><br>The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.|All|All|None|None| |Read-write access to services with tag|Specify tag name and, optionally, value to additionally grant read-write access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-write access to services* parameter.<br>The read-write access, if granted, takes precedence over the read-only access settings and is dynamically inherited by the child services.|^|^|^|^| |Read-only access to services|Select read-only access to services:<br>**None** - no access at all<br>**All** - access to all services is read-only<br>**Service list** - select services for read-only access<br><br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|All|All| |Read-only access to services with tag|Specify tag name and, optionally, value to additionally grant read-only access to services matching the tag.<br>This option is available if 'Service list' is selected in the *Read-only access to services* parameter.<br>The read-only access does not take precedence over the read-write access and is dynamically inherited by the child services.|^|^|^|^| |Access to modules|<|<|<|<|<| |<Module name>|Allow/deny access to a specific module. Only enabled modules are shown in this section. It is not possible to grant or restrict access to a module that is currently disabled.|Yes|Yes|Yes|Yes| |*Default access to new modules*|Enable/disable access to modules that may be added in the future.|^|^|^|^| |Access to API|<|<|<|<|<| |*Enabled*|Enable/disable access to API.|Yes|Yes|Yes|No| |*API methods*|Select *Allow list* to allow only specified API methods or *Deny list* to restrict only specified API methods.<br><br>In the search field, start typing the method name, then select the method from the auto-complete list.<br>You can also press the Select button and select methods from the full list available for this user type. Note, that if certain action from the Access to actions block is unchecked, users will not be able to use API methods related to this action.<br><br>Wildcards are supported. Examples: `dashboard.*` (all methods of 'dashboard.' API service) `*` (any method), `*.export` (methods with '.export' name from all API services).<br><br>If no methods have been specified the Allow/Deny list rule will be ignored.|^|^|^|^| |Access to actions|<|<|<|<|<| |Create and edit dashboards|Clearing this checkbox will also revoke the rights to use `.create`, `.update` and `.delete` API methods for the corresponding elements.|Yes|Yes|Yes|No| |Create and edit maps|^|^|^|^|^| |Create and edit maintenance|^|^|^|No|^| |Add problem comments|Clearing this checkbox will also revoke the rights to perform corresponding action via `event.acknowledge` API method.|^|^|Yes|^| |Change severity|^|^|^|^|^| |Acknowledge problems|^|^|^|^|^| |Close problems|^|^|^|^|^| |Execute scripts|Clearing this checkbox will also revoke the rights to use the `script.execute` API method.|^|^|^|^| |Manage API tokens|Clearing this checkbox will also revoke the rights to use all `token.` API methods.|^|^|^|^| |Manage scheduled reports|Clearing this checkbox will also revoke the rights to use all `report.` API methods.|^|^|No|^| |Manage SLA|Enable/disable the rights to manage [SLA](/manual/web_interface/frontend_sections/services/sla).|^|^|^|^| |Default access to new actions|Enable/disable access to new actions.|^|^|Yes|^|  Notes:  -   Each user may have only one role assigned. -   If an element is restricted, users will not be able to access it     even by entering a direct URL to this element into the browser. -   Users of type *User* or *Admin* cannot change their own role     settings. -   Users of type *Super admin* can modify settings of their own role     (not available for the default *Super admin role*), but not the user     type. -   Users of all levels cannot change their own user type.  See also:  -   [Configuring a user](/manual/config/users_and_usergroups/user)
zh-cn	#### 默认用户角色  默认情况下，Zabbix 配置了四个用户角色，它们具有一组预定义的权限：  - · 管理员角色 - · 嘉宾角色 - · 超级管理员角色 - · 用户角色  ![](../../../../../assets/en/manual/web_interface/user_roles0.png){width="600"}  ::: noteclassic  默认 *超级管理员角色* 不能修改或删除，因为 Zabbix 中必须至少存在一个具有无限权限的超级管理员。 :::  具有超级管理员类型和适当权限的 Zabbix 用户可以修改或删除现有角色或创建新的自定义角色。  要创建新角色，请单击右上角的*创建用户角色*按钮。要更新现有角色，请按角色名称以打开配置表单。  ![](../../../../../assets/en/manual/web_interface/user_role.png)  Zabbix 中预先存在的用户角色的可用权限选项以及默认权限集如下所述。  |参数|说明|默认用户角色|<|<|<| |---------|-----------|------|-|-|-| | | |超级管理员角色|管理员角色|用户角色|访客角色| |名称|角色可见名称。|超级管理员角色|管理员角色|用户角色|访客角色| |用户类型|选定的用户类型决定了可用权限的列表。<br>选择用户类型后，默认情况下会授予此用户类型的所有可用权限。<br>取消选中该复选框可撤消该用户的某些权限用户角色。<br>此用户类型不可用的权限复选框呈灰色显示。|超级管理员|管理员|用户|用户| |访问 UI 元素|<|<|<|<|<| |*监控*|<|<|<|<|<| |仪表板|启用/禁用对特定监控菜单部分和基础页面的访问。|是|是|是|是| |问题|^|^|^|^|^| |主机|^|^|^|^|^| |最新数据|^|^|^|^|^| |地图|^|^|^|^|^| |发现|^|^|^|否|否| |*服务*|<|<|<|<|<| |服务|启用/禁用对特定服务菜单部分和基础页面的访问。|是|是|是|是| |服务行动|^|^|^|^|^| |SLA|^|^|^|^|^| |SLA 报告|^|^|^|^|^| |*资产管理*|<|<|<|<|<| |概览|启用/禁用对特定库存菜单部分和基础页面的访问。|是|是|是|是| |主机|^|^|^|^|^| |*报告*|<|<|<|<|<| |系统信息|启用/禁用对特定报告菜单部分和基础页面的访问。|是|否|否|否| |可用性报告|^|^|是|是|是| |触发前 100 名|^|^|^|^|^| |审核|^|^|否|否|否| |动作日志|^|^|^|^|^| |通知|^|^|是|^|^| |预定报告|^|^|^|^|^| |*配置*|<|<|<|<|<| |主机组|启用/禁用对特定*配置*菜单部分和基础页面的访问。|是|是|否|否| |模板|^|^|^|^|^| |主机|^|^|^|^|^| |维护|^|^|^|^|^| |动作|^|^|^|^|^| |事件关联|^|^|否|^|^| |发现|^|^|是|^|^| |*管理*|<|<|<|<|<| |常规|启用/禁用对特定*管理*菜单部分和基础页面的访问。|是|否|否|否| |proxies|^|^|^|^|^| |认证|^|^|^|^|^| |用户组|^|^|^|^|^| |用户角色|^|^|^|^|^| |用户|^|^|^|^|^| |媒介类型|^|^|^|^|^| |脚本|^|^|^|^|^| |队列|^|^|^|^|^| |*对新 UI 元素的默认访问*|启用/禁用对自定义 UI 元素的访问。模块，如果存在，将在下面列出。|是|是|是|是| |访问服务|<|<|<|<|<| |对服务的读写访问权限|选择对服务的读写访问权限：<br>**无** - 完全没有访问权限<br>**全部** - 对所有服务的访问权限为读写权限<br>* *服务列表** - 为读写访问选择服务<br><br>读写访问优先于只读访问，并由子服务动态继承。|是|是|否|否| |使用标签对服务进行读写访问|指定标签名称和可选的值，以额外授予对匹配标签的服务的读写访问权限。<br>如果在 *Read- 中选择了“服务列表”，则此选项可用对 services* 参数的写访问。<br>读写访问优先于只读访问，并由子服务动态继承。|^|^|^|^| |对服务的只读访问权限|选择对服务的只读访问权限：<br>**无** - 根本没有访问权限<br>**全部** - 对所有服务的访问权限都是只读的<br>* *服务列表** - 选择服务进行只读访问<br><br>只读访问不优先于读写访问，由子服务动态继承。|^|^|^| ^| |对带有标签的服务的只读访问权限|指定标签名称和（可选）值以额外授予对匹配标签的服务的只读访问权限。<br>如果在 *Read- 中选择了“服务列表”，则此选项可用仅访问 services* 参数。<br>只读访问不优先于读写访问，由子服务动态继承。|^|^|^|^| |访问模块|<|<|<|<|<| |<模块名称>|允许/拒绝对特定模块的访问。本节仅显示启用的模块。无法授予或限制对当前禁用的模块的访问权限。|是|是|是|是| |*对新模块的默认访问*|启用/禁用对将来可能添加的模块的访问。|^|^|^|^| |访问API|<|<|<|<|<| |*启用*|启用/禁用对 API 的访问。|是|是|是|否| |*API 方法*|选择*允许列表* 仅允许指定的 API 方法或选择*拒绝列表* 仅限制指定的 API 方法。<br><br>在搜索字段中，开始输入方法名称，然后选择方法从自动完成列表中。<br>您还可以按“选择”按钮并从可用于此用户类型的完整列表中选择方法。请注意，如果未选中“访问操作”块中的某些操作，用户将无法使用与该操作相关的 API 方法。<br><br>支持通配符。示例：`dashboard.*`（'dashboard.' API 服务的所有方法）`*`（任何方法）、`*.export`（来自所有 API 服务的具有 '.export' 名称的方法）。<br><br >如果没有指定方法，允许/拒绝列表规则将被忽略。|^|^|^|^| |访问操作|<|<|<|<|<| |创建和编辑仪表板|清除此复选框还将撤销对相应元素使用 `.create`、`.update` 和 `.delete` API 方法的权限。|是|是|是|否| |创建和编辑地图|^|^|^|^|^| |创建和编辑维护|^|^|^|否|^| |添加问题评论|清除此复选框还将撤销通过`event.acknowledge` API方法执行相应操作的权限。|^|^|是|^| |更改严重性|^|^|^|^|^| |确认问题|^|^|^|^|^| |关闭问题|^|^|^|^|^| |执行脚本|清除此复选框也将撤销使用 `script.execute` API 方法的权限。|^|^|^|^| |管理 API 令牌|清除此复选框还将撤销使用所有 `token.` API 方法的权利。|^|^|^|^| |管理预定报告|清除此复选框还将撤销使用所有“报告”API 方法的权利。|^|^|否|^| |管理 SLA|启用/禁用管理 [SLA](/manual/web_interface/frontend_sections/services/sla) 的权限。|^|^|^|^| |默认访问新操作|启用/禁用访问新操作。|^|^|是|^|  备注：  - · 每个用户只能分配一个角色。 - · 如果某个元素受到限制，即使在浏览器中输入指向该元素的直接 URL，用户也无法访问它。 - · *User* 或*Admin* 类型的用户不能更改他们自己的角色设置。 - · *超级管理员*类型的用户可以修改他们自己角色的设置（不适用于默认的*超级管理员角色*），但不能修改用户类型。 - · 各级用户不能更改自己的用户类型。  参阅：  - · [配置用户](/manual/config/users_and_usergroups/user)

en-us	Delay
zh-cn	延迟

en-us	Delayed by
zh-cn	被延迟由于

en-us	Delete
zh-cn	删除

en-us	Delete all elements that are not present in the XML file?
zh-cn	删除XML文件中不存在的元素吗？

en-us	Delete and clear
zh-cn	删除并清除

en-us	Delete and clear selected templates? (Warning: all linked hosts will be cleared!)
zh-cn	删除并清除所选的模板? (警告: 所有链接的主机将被清除!)

en-us	Delete and clear template? (Warning: all linked hosts will be cleared!)
zh-cn	删除并清除模板? (警告: 所有链接的主机将被清除!)

en-us	Delete application?
zh-cn	删除应用集?

en-us	Delete current action?
zh-cn	删除目前的动作?

en-us	Delete current correlation?
zh-cn	删除当前的关联项？

en-us	Deleted
zh-cn	已删除

en-us	Delete dashboard?
zh-cn	你确定要删除仪表盘？

en-us	Deleted: Host "%1$s".
zh-cn	已删除: 主机 "%1$s".

en-us	Deleted: Host prototype "%1$s" on "%2$s".
zh-cn	已删除：主机原型 "%1$s" 于 "%2$s"。

en-us	Delete discovery rule?
zh-cn	删除发现规则?

en-us	Deleted: Template "%1$s".
zh-cn	已删除: 模板 "%1$s".

en-us	Delete expression?
zh-cn	删除表达式?

en-us	Delete graph?
zh-cn	删除图形?

en-us	Delete graph prototype?
zh-cn	删除数据图模板？

en-us	Delete history of selected items?
zh-cn	删除所选监控项的历史数据?

en-us	Delete history of selected web scenarios?
zh-cn	删除所选的 web 场景历史？

en-us	Delete icon map?
zh-cn	删除图标映射?

en-us	Delete item?
zh-cn	删除监控项?

en-us	Delete item prototype?
zh-cn	删除监控项目模板?

en-us	Delete links between selected elements?
zh-cn	删除所选组件间的连接?

en-us	Delete maintenance period?
zh-cn	删除维修期间?

en-us	Delete media type?
zh-cn	删除媒体值？

en-us	Delete missing
zh-cn	删除失败

en-us	Delete proxy?
zh-cn	删除代理?

en-us	Delete regular expression?
zh-cn	删除正则表达式?

en-us	Delete screen?
zh-cn	删除聚合图形?

en-us	Delete script?
zh-cn	删除脚本?

en-us	Delete selected actions?
zh-cn	删除所选的动作?

en-us	Delete selected applications?
zh-cn	删除所选的应用集?

en-us	Delete selected correlations?
zh-cn	删除选择的关联项？

en-us	Delete selected dashboards?
zh-cn	删除所有的仪表盘？（危险）

en-us	Delete selected discovery rules?
zh-cn	删除所选的发现规则?

en-us	Delete selected elements?
zh-cn	删除所选的元素?

en-us	Delete selected graph prototypes?
zh-cn	删除所选定的数据图模板?

en-us	Delete selected graphs?
zh-cn	删除所选的图表?

en-us	Delete selected group?
zh-cn	删除所选的群组?

en-us	Delete selected groups?
zh-cn	删除所选的群组?

en-us	Delete selected host?
zh-cn	删除所选的主机?

en-us	Delete selected host groups?
zh-cn	删除所选的主机群组?

en-us	Delete selected host prototype?
zh-cn	删除所选定的主机模板?

en-us	Delete selected host prototypes?
zh-cn	删除所选定的主机模板?

en-us	Delete selected hosts?
zh-cn	删除所选的主机?

en-us	Delete selected image?
zh-cn	删除所选的图像?

en-us	Delete selected item prototypes?
zh-cn	删除所选定的监控项目模板?

en-us	Delete selected items?
zh-cn	删除所选的监控项?

en-us	Delete selected maintenance periods?
zh-cn	删除所选的维修期间?

en-us	Delete selected map?
zh-cn	删除选择的拓扑图？

en-us	Delete selected maps?
zh-cn	删除所选的地图?

en-us	Delete selected media types?
zh-cn	删除所选的报警媒体类型?

en-us	Delete selected proxies?
zh-cn	删除所选的代理?

en-us	Delete selected regular expressions?
zh-cn	删除所选的正则表达式?

en-us	Delete selected screens?
zh-cn	删除所选的聚合图形？

en-us	Delete selected scripts?
zh-cn	删除所选的脚本?

en-us	Delete selected shapes?
zh-cn	删除所选形状？

en-us	Delete selected slide shows?
zh-cn	删除所选的幻灯片展示?

en-us	Delete selected templates?
zh-cn	删除所选的模板?

en-us	Delete selected trigger prototypes?
zh-cn	删除所选的触发器原型？

en-us	Delete selected triggers?
zh-cn	删除所选的触发器?

en-us	Delete selected user?
zh-cn	删除所选的用户?

en-us	Delete selected users?
zh-cn	删除所选的用户?

en-us	Delete selected value mapping?
zh-cn	删除所选的值映射?

en-us	Delete selected value mapping? It is used for %d item!
zh-cn	删除所选的值映射? 它用于 %d 监控项!

en-us	Delete selected value maps?
zh-cn	删除所选的值映射？

en-us	Delete selected web scenarios?
zh-cn	删除所选的 web 场景？

en-us	Delete service "%1$s"?
zh-cn	删除服务 "%1$s"？

en-us	Delete slide show?
zh-cn	删除幻灯片演示?

en-us	Delete template?
zh-cn	删除模板?

en-us	Delete trigger?
zh-cn	删除触发器?

en-us	Delete trigger prototype?
zh-cn	删除触发器原型？

en-us	Delete web scenario?
zh-cn	删除 web 场景？

en-us	Delimiter
zh-cn	分隔符

en-us	delta() - Difference between MAX and MIN value of a period T
zh-cn	delta() - 周期 T 内的 MAX 和 MIN 值之间的差异

en-us	Deny
zh-cn	拒绝

en-us	Dependencies
zh-cn	依赖关系

en-us	Dependent
zh-cn	依赖

en-us	Dependent item
zh-cn	相关项目

en-us	Depends on
zh-cn	依赖于

en-us	Deployment status
zh-cn	部署状态

en-us	DES
zh-cn	DES

en-us	descending
zh-cn	降

en-us	Description
zh-cn	描述

en-us	Description updated
zh-cn	描述已经更新

en-us	Details
zh-cn	细节

en-us	Details of web scenario
zh-cn	网络方案详细信息

en-us	Device
zh-cn	设备

en-us	Device interrupts. Returns integer
zh-cn	设备的中断数。返回整数

en-us	Device uniqueness criteria
zh-cn	设备唯一性准则

en-us	diff() - Difference between last and preceding values (1 - true, 0 - false)
zh-cn	diff() - 最后一个值和前一个值之间的差异（1 - true，0 - false）

en-us	Dimension (cols x rows)
zh-cn	图表规格 (列 x 行)

en-us	directory or script name cannot be empty
zh-cn	目录或脚本名称不能为空

en-us	Directory size (in bytes). Returns integer
zh-cn	目录大小（bytes）。返回整数

en-us	Disable
zh-cn	禁用

en-us	Disabled
zh-cn	停用的

en-us	DISABLED
zh-cn	禁用

en-us	Disable debug mode
zh-cn	禁用调试模式

en-us	Disable debug mode in selected groups?
zh-cn	停用所选群组的调试模式?

en-us	Disable host
zh-cn	停用主机

en-us	Disable host?
zh-cn	停用主机?

en-us	Disable hosts
zh-cn	禁用主机

en-us	Disable hosts in the selected host groups?
zh-cn	停用所选的主机群组中的主机?

en-us	Disable hosts monitored by selected proxies?
zh-cn	停用所选的agent代理程序所监测的主机?

en-us	Disable selected actions?
zh-cn	停用所选的动作?

en-us	Disable selected applications?
zh-cn	停用所选的应用集?

en-us	Disable selected correlations?
zh-cn	禁用选择的关联项？

en-us	Disable selected discovery rules?
zh-cn	停用所选的自动发现规则?

en-us	Disable selected groups?
zh-cn	停用所选的群组?

en-us	Disable selected hosts?
zh-cn	停用所选的主机?

en-us	Disable selected items?
zh-cn	停用所选的监控项?

en-us	Disable selected media types?
zh-cn	停用所选的报警媒介类型?

en-us	Disable selected triggers?
zh-cn	停用所选的触发器?

en-us	Disable selected web scenarios?
zh-cn	禁用所选定的web场景？

en-us	Disaster
zh-cn	灾难

en-us	Discovered
zh-cn	已发现的

en-us	Discovered by
zh-cn	被发现的

en-us	Discovered device
zh-cn	已发现的设备

en-us	discovered host
zh-cn	被发现的主机

en-us	Discovered items
zh-cn	已发现的监控项

en-us	discovered service
zh-cn	被发现的服务

en-us	discovery
zh-cn	发现

en-us	Discovery
zh-cn	自动发现

en-us	Discovery by proxy
zh-cn	由agent代理程序自动发现

en-us	Discovery check
zh-cn	自动发现检查

en-us	Discovery check error
zh-cn	发现检查错误

en-us	Discovery checks
zh-cn	自动发现检查

en-us	Discovery list
zh-cn	自动发现清单

en-us	Discovery object
zh-cn	自动发现物件

en-us	Discovery rule
zh-cn	自动发现规则

en-us	Discovery rule "%1$s" already exists.
zh-cn	发现规则"%1$s"已存在

en-us	Discovery rule "%1$s" already exists on "%2$s".
zh-cn	发现规则"%1$s"已存在于 "%2$s".

en-us	Discovery rule "%1$s" already exists on "%2$s", inherited from another template.
zh-cn	自动发现规则 "%1$s" 已存在于 "%2$s", 继承自其它的模板.

en-us	Discovery rule "%1$s" is used in "%2$s" action.
zh-cn	发现规则 "%1$s" 已经在动作 "%2$s" 中使用。

en-us	Discovery rule created
zh-cn	自动发现规则已创建

en-us	Discovery rule deleted
zh-cn	自动发现规则已删除

en-us	Discovery rule deleted
zh-cn	自动发现规则已删除

en-us	Discovery rule disabled
zh-cn	发现规则已禁用

en-us	Discovery rule enabled
zh-cn	发现规则已经启用

en-us	discovery rule is disabled
zh-cn	发现规则被禁用

en-us	Discovery rules
zh-cn	自动发现规则

en-us	Discovery rules deleted
zh-cn	自动发现规则已删除

en-us	Discovery rule updated
zh-cn	自动发现规则已更新

en-us	Discovery status
zh-cn	自动发现状态

en-us	Disk read statistics. Returns integer with type in sectors, operations, bytes; float with type in sps, ops, bps
zh-cn	磁盘读取数据。类型是sectors, operations, bytes;返回整数，类型是 sps, ops, bps则返回浮点。

en-us	Disk space in bytes or in percentage from total. Returns integer for bytes; float for percentage
zh-cn	磁盘容量。如果返回的是字节则是整数，如果返回的是百分比则是浮点。

en-us	Disk write statistics. Returns integer with type in sectors, operations, bytes; float with type in sps, ops, bps
zh-cn	磁盘写入数据。类型是sectors, operations, bytes;返回整数，类型是 sps, ops, bps则返回浮点。

en-us	Display graph
zh-cn	显示数据图

en-us	Displaying %1$s of %2$s found
zh-cn	显示 已自动发现的 %2$s中的%1$s

en-us	Displaying %1$s to %2$s of %3$s found
zh-cn	在 %3$s 中打印 %1$s 到 %2$s 

en-us	Displaying options
zh-cn	显示选项

en-us	Display OK triggers for
zh-cn	显示OK触发器予

en-us	Display problems
zh-cn	显示问题

en-us	Display stacked graph
zh-cn	显示堆叠数据图

en-us	d.M
zh-cn	d.M

en-us	DNS
zh-cn	DNS

en-us	DNS name
zh-cn	DNS名称

en-us	does not contain
zh-cn	不含

en-us	does not equal
zh-cn	不等于

en-us	does not match
zh-cn	不匹配

en-us	Do not calculate
zh-cn	不要计算

en-us	Dot
zh-cn	点

en-us	Down
zh-cn	下

en-us	Down
zh-cn	下

en-us	Download the configuration file
zh-cn	下载配置文件

en-us	Downtime
zh-cn	断线时间

en-us	Do you wish to replace the conditional expression?
zh-cn	您想要替换条件式表达式吗?

en-us	Draw
zh-cn	绘制

en-us	Draw style
zh-cn	绘图风格

en-us	Dropdown first entry
zh-cn	下拉的第一个输入项

en-us	Dropdown first entry "%1$s".
zh-cn	下拉的第一个输入项 "%1$s".

en-us	Dropdown remember selected "%1$s".
zh-cn	下拉记住所选的 "%1$s".

en-us	Duplicate "%1$s" value "%2$s" for correlation.
zh-cn	在关联项中复制"%1$s"的值 "%2$s"

en-us	Duplicate "%1$s" value "%2$s" for correlation "%3$s".
zh-cn	复制关联项 "%3$s" 中 "%1$s" 的值 "%2$s" 。

en-us	Duplicate dependencies in trigger "%1$s".
zh-cn	重复依赖关系在触发器 "%1$s" 中.

en-us	Duplicate dependencies in trigger prototype "%1$s".
zh-cn	触发器的原形依赖复制"%1$s"。

en-us	Duplicate "description" value "%1$s" for media type.
zh-cn	%1$s 媒体类型说明值重复。

en-us	Duplicate host. Host with the same host name "%s" already exists in data.
zh-cn	重复的主机. 有相同主机名称 "%s" 的主机已存于数据中.

en-us	Duplicate host. Host with the same visible name "%s" already exists in data.
zh-cn	重复的主机. 有相同主机可视名称"%s"的主机已存于数据中.

en-us	Duplicate "name" value "%1$s" for application prototype in item prototype "%2$s".
zh-cn	"%2$s"与"%1$s"的名字有冲突。

en-us	Duplicate "name" value "%1$s" for map.
zh-cn	拓扑图 %1$s 名字重复。

en-us	Duplicate "name" value "%1$s" for screen.
zh-cn	复制聚合图形的"name"值"%1$s"

en-us	Duplicate severity name "%s".
zh-cn	重复的严重性名称"%s".

en-us	Duplicate userid "%1$s" in users for map "%2$s".
zh-cn	用户ID "%1$s" 与 "%2$s" 冲突

en-us	Duplicate userid "%1$s" in users for screen "%2$s".
zh-cn	用户ID "%1$s" 聚合图形的用户 "%2$s" 冲突

en-us	Duplicate usrgrpid "%1$s" in user groups for map "%2$s".
zh-cn	用户组ID "%1$s" 与 "%2$s" 冲突

en-us	Duplicate usrgrpid "%1$s" in user groups for screen "%2$s".
zh-cn	用户组ID "%1$s" 与 "%2$s" 聚合图形用户组冲突。

en-us	Duration
zh-cn	持续时间

en-us	Dutch (nl_NL)
zh-cn	荷兰(nl_NL)

en-us	Dynamic item
zh-cn	动态监控项

en-us	Dynamic items
zh-cn	动态监控项

en-us	Each URL should have a unique name. Please make sure there is only one URL named
zh-cn	每个URL必须是唯一的. 请确保只有一个被命名的 URL.

en-us	Edit
zh-cn	编辑

en-us	Edit dashboard
zh-cn	编辑仪表盘

en-us	Edit map
zh-cn	编辑拓扑图

en-us	Edit screen
zh-cn	编辑聚合图形

en-us	Edit slide show
zh-cn	编辑幻灯片

en-us	Edit tree element
zh-cn	编辑树元素

en-us	Edit trigger
zh-cn	编辑触发器

en-us	Edit widget
zh-cn	编辑构件

en-us	Effective value
zh-cn	可用值

en-us	Elasticsearch error: %1$s.
zh-cn	Elasticsearch 错误：%1$s。

en-us	Elasticsearch url is not set for type: %1$s.
zh-cn	未设置下一个类型的Elasticsearch网址：%1$s。

en-us	Element
zh-cn	组件

en-us	Element name
zh-cn	组件名称

en-us	Ellipse
zh-cn	椭圆

en-us	Email
zh-cn	电子邮件

en-us	Empty
zh-cn	空

en-us	Empty action condition.
zh-cn	空的动作条件。

en-us	Empty application prototype name in item prototype "%1$s".
zh-cn	该项目的原型应用名称为 "%1$s" 里面是空的。

en-us	Empty colour.
zh-cn	空的颜色。

en-us	Empty correlation ID.
zh-cn	空的关联ID。

en-us	Empty filter condition formula ID for action "%1$s".
zh-cn	针对动作"%1$s"的过滤器条件表达式ID为空

en-us	Empty filter condition formula ID for discovery rule "%1$s".
zh-cn	针对自动发现规则 "%1$s"的过滤器条件表达式ID为空

en-us	Empty filter condition macro for discovery rule "%1$s".
zh-cn	针对自动发现规则 "%1$s"的过滤器条件宏变量为空

en-us	Empty input parameter.
zh-cn	空的输入参数.

en-us	Empty input parameters.
zh-cn	所输入的参数为空.

en-us	Empty map ID.
zh-cn	空的拓扑图ID。

en-us	Empty media type ID.
zh-cn	空的媒介类型ID。

en-us	Empty name.
zh-cn	空名字

en-us	Empty parameters
zh-cn	空参数

en-us	Empty screen ID.
zh-cn	空白聚合图形ID。

en-us	Empty screen ID for screen.
zh-cn	聚合图形的ID号为空

en-us	Empty screen ID for template screen.
zh-cn	聚合图形模板的聚合图形ID号为空

en-us	Empty SSL certificate file for web scenario "%1$s".
zh-cn	场景"%1$s"配置了空的SSL证书文件

en-us	Empty SSL key file for web scenario "%1$s".
zh-cn	场景"%1$s"配置了空的SSL证书文件

en-us	Enable
zh-cn	启用

en-us	Enable confirmation
zh-cn	启用确认

en-us	Enabled
zh-cn	已启用

en-us	Enable debug mode
zh-cn	启用调试模式

en-us	Enable debug mode in selected groups?
zh-cn	于所选的群组中启用调试模式?

en-us	Enable host
zh-cn	启用主机

en-us	Enable host?
zh-cn	启用主机?

en-us	Enable hosts
zh-cn	启用主机

en-us	Enable hosts monitored by selected proxies?
zh-cn	启用受所选的agent代理程序所监测的主机?

en-us	Enable HTTP authentication
zh-cn	开启 HTTP 验证

en-us	Enable internal housekeeping
zh-cn	开启内部管家

en-us	Enable LDAP authentication
zh-cn	开启 LDAP 验证

en-us	Enable selected actions?
zh-cn	启用所选的动作?

en-us	Enable selected applications?
zh-cn	启用所选的应用集

en-us	Enable selected correlations?
zh-cn	开启选择的关联项？

en-us	Enable selected discovery rules?
zh-cn	启用所选的自动发现规则?

en-us	Enable selected groups?
zh-cn	启用所选的群组?

en-us	Enable selected hosts?
zh-cn	启用所选的主机?

en-us	Enable selected items?
zh-cn	启用所选的监控项？

en-us	Enable selected media types?
zh-cn	启用所选的报警媒介类型?

en-us	Enable selected triggers?
zh-cn	启用所选的触发器?

en-us	Enable selected web scenarios?
zh-cn	启用所选定的web场景?

en-us	Enable trapping
zh-cn	启用trapping

en-us	Encryption
zh-cn	加密

en-us	English (en_GB)
zh-cn	英语 (en_GB)

en-us	English (en_US)
zh-cn	英语(en_US)

en-us	equals
zh-cn	等于

en-us	Equals
zh-cn	等于

en-us	Error
zh-cn	错误

en-us	Error: %1$s
zh-cn	错误: %1$s

en-us	Error in search request for table "%1$s".
zh-cn	查找表请求出现 "%1$s"的错误.

en-us	Error message
zh-cn	错误信息

en-us	esc_step_from and esc_step_to must be set together.
zh-cn	esc_step_from和esc_step_to必须一起设定.

en-us	Event
zh-cn	事件

en-us	Event acknowledged
zh-cn	事件已确认

en-us	Event correlation
zh-cn	关联项事件

en-us	Event correlation rules
zh-cn	关联项事件规则

en-us	Event details
zh-cn	事件细节

en-us	Event generation
zh-cn	事件生成

en-us	Event ID
zh-cn	事件ID

en-us	Event list [previous 20]
zh-cn	事件清单[前 20]

en-us	Event log monitoring. Returns log
zh-cn	事件日志监控。返回日志

en-us	Events and alerts
zh-cn	事件和报警

en-us	Event source
zh-cn	事件源

en-us	Event tag pair
zh-cn	事件标签对

en-us	Event type
zh-cn	事件类型

en-us	Event updated
zh-cn	事件更新

en-us	Every day(s)
zh-cn	每日

en-us	Every week(s)
zh-cn	每周

en-us	Exclude
zh-cn	除外

en-us	Exclude host groups
zh-cn	排除主机组

en-us	Execute
zh-cn	执行

en-us	Executed
zh-cn	已执行

en-us	Executed script
zh-cn	已执行的脚本

en-us	Execute on
zh-cn	执行在

en-us	Execute SQL error [%1$s] in [%2$s].
zh-cn	执行SQL错误[%1$s]于[%2$s].

en-us	Execute WMI query and return the first selected object. Returns integer, float, string or text (depending on the request)
zh-cn	执行 WMI 查询返回第一个对象。返回整形、浮点、字符串或者文本内容

en-us	Execution confirmation
zh-cn	执行确认

en-us	Expand
zh-cn	扩展

en-us	Expand macros
zh-cn	展开宏

en-us	Expand single problem
zh-cn	展开单一问题

en-us	Expired
zh-cn	过期的

en-us	Exploded
zh-cn	爆发的

en-us	Export
zh-cn	导出

en-us	Export to CSV
zh-cn	导出到CSV

en-us	Expression
zh-cn	表达式

en-us	Expression cannot be empty
zh-cn	表达式不能为空白

en-us	Expression constructor
zh-cn	表达式构造器

en-us	expression is empty
zh-cn	表达式为空

en-us	Expressions
zh-cn	表达式

en-us	Expression syntax error.
zh-cn	表达式语法错误。

en-us	Expression type
zh-cn	表达式类型

en-us	Expression Variable Elements
zh-cn	表达式变量组成

en-us	External check
zh-cn	外部检查

en-us	 ##### External plugin loader Previously, plugins could only be compiled into Zabbix agent 2, which required recompiling the agent every time you need to change the set of available plugins. Now, with the addition of the external plugin loader, plugins don't have to be integrated into the agent 2 directly and can be added as separate external add-ons (loadable plugins), thus making the creation process of additional plugins for gathering new monitoring metrics easier.
zh-cn	##### 外部插件加载器  以前，插件只能编译到 Zabbix agent 2 中，每次需要更改可用插件集时都需要重新编译 agent。现在，通过添加外部插件加载器，插件不必直接集成到 agent 2 中，并且可以作为单独的外部插件添加，从而使用于收集新监控指标的附加插件的创建过程更加容易。

en-us	Ez Texting
zh-cn	Ez简讯

en-us	F
zh-cn	F

en-us	Fail
zh-cn	失败

en-us	Failed
zh-cn	已失败

en-us	Failed to create dashboard
zh-cn	创建仪表盘失败

en-us	failed to parse JSON
zh-cn	无法解析 JSON

en-us	Failed to parse URL.
zh-cn	无法解析URL。

en-us	Failed to update dashboard
zh-cn	更新仪表盘失败

en-us	Failed to update template.
zh-cn	更新模板失败

en-us	Failure Audit
zh-cn	失败审计

en-us	FALSE
zh-cn	假

en-us	Fatal error, please report to the Zabbix team
zh-cn	呦吼~中奖了。你发现了一个致命的zabbix错误。来我们的社区把问题跟我们说下吧。我们很乐意帮你解决。

en-us	Favourite graphs
zh-cn	常用的图形

en-us	Favourite maps
zh-cn	常用的拓扑图

en-us	Favourite screens
zh-cn	常用的聚合图形

en-us	Feb
zh-cn	二月

en-us	February
zh-cn	二月

en-us	Field
zh-cn	栏位

en-us	Field "%1$s" cannot be set to NULL.
zh-cn	字段 "%1$s"不能被设置为空

en-us	Field "%1$s" is mandatory.
zh-cn	选项"%1$s"为必填项

en-us	Field "%1$s" is missing a value for map "%2$s".
zh-cn	字段 "%1$s" 缺少拓扑图 "%2$s" 的值。

en-us	Field "%1$s" is missing a value for media type "%2$s".
zh-cn	字段 "%1$s" 缺少媒体类型 "%2$s" 的值。

en-us	Field "%1$s" is missing a value for screen "%2$s".
zh-cn	字段 "%1$s" 缺少聚合图形 "%2$s" 的值。

en-us	Field "%1$s" is not correct: %2$s
zh-cn	字段 "%1$s" 设置错误: %2$s

en-us	Field "%1$s" is not integer.
zh-cn	字段 "%1$s" 不是整数

en-us	Field "%1$s" is not string.
zh-cn	字段 "%1$s"不是字符串

en-us	Field "%1$s" is required for media type "%2$s".
zh-cn	字段 "%1$s" 需要媒体类型 "%2$s".

en-us	Field "%1$s" must be missing.
zh-cn	字段"%1$s"不可以填写

en-us	Field "host" is mandatory.
zh-cn	字段"host"为必填项.

en-us	File checksum, calculated by the UNIX cksum algorithm. Returns integer
zh-cn	文件效验，unix标准算法。返回整数

en-us	File format is unsupported.
zh-cn	Only super admins can create groups

en-us	File is too big, max upload size is %1$s bytes.
zh-cn	文件太大, 最大的上传大小是 %1$s 个字节.

en-us	File provided to a view does not exist. Tried to find "%s".
zh-cn	提供给视图的文件不存在. 试着查找"%s".

en-us	File size (in bytes). Returns integer
zh-cn	文件大小（单位bytes）。返回整数

en-us	File time information. Returns integer (Unix timestamp)
zh-cn	文件事件信息，返回的是时间戳 整数

en-us	Fill
zh-cn	填

en-us	Filled region
zh-cn	填满的区域

en-us	Filter
zh-cn	过滤器

en-us	Filters
zh-cn	过滤器

en-us	Find string in a file. Returns 0 - match not found; 1 - found
zh-cn	查找文件中的字符串，如果有则返回1，没有则返回0。

en-us	Find string in a file. Returns the line containing the matched string, or as specified by the optional output parameter
zh-cn	查找文件中的字符串，返回内容是被匹配内容的整行字符串，或者其他可选参数

en-us	Find string on a web page. Returns the matched string, or as specified by the optional output parameter
zh-cn	查找网页中的字符串，返回内容是被匹配内容的整行字符串，或者其他可选参数

en-us	Finish
zh-cn	完成

en-us	Finnish (fi_FI)
zh-cn	芬兰语 (fi_FI)

en-us	first
zh-cn	第一

en-us	First
zh-cn	首

en-us	first parameter is expected
zh-cn	第一个参数是预设的

en-us	Fit
zh-cn	适合

en-us	Fit to map
zh-cn	调整至符合拓扑图

en-us	Fixed
zh-cn	固定的

en-us	Flexible
zh-cn	灵活

en-us	Follow redirects
zh-cn	跟随跳转

en-us	Font
zh-cn	字体

en-us	Font colour
zh-cn	字体颜色

en-us	Font size
zh-cn	字体大小

en-us	forecast() - Forecast for next t seconds based on period T
zh-cn	forecast() - 基于周期 T 预测下一个 t 秒

en-us	For guest, password must be empty
zh-cn	访客的密码必须为空

en-us	Form data
zh-cn	表格资料

en-us	Formula
zh-cn	公式

en-us	fourth
zh-cn	第四

en-us	French (fr_FR)
zh-cn	法语 (fr_FR)

en-us	Fri
zh-cn	周五

en-us	Friday
zh-cn	周五

en-us	From
zh-cn	自从

en-us	Frontend access
zh-cn	前端访问

en-us	Frontend access updated
zh-cn	前端访问已更新

en-us	Frontend messaging
zh-cn	前端信息中

en-us	##### Frontend  The minimum supported screen width for Zabbix frontend is 1200px.  |Software|Version|Comments| |--------|-------|--------| |*Apache*|1.3.12 or later| | |*PHP*|7.2.5 or later|PHP 8.0 is not supported.| |PHP extensions:|<|<| |*gd*|2.0.28 or later|PHP GD extension must support PNG images (*--with-png-dir*), JPEG (*--with-jpeg-dir*) images and FreeType 2 (*--with-freetype-dir*).| |*bcmath*| |php-bcmath (*--enable-bcmath*)| |*ctype*| |php-ctype (*--enable-ctype*)| |*libXML*|2.6.15 or later|php-xml, if provided as a separate package by the distributor.| |*xmlreader*| |php-xmlreader, if provided as a separate package by the distributor.| |*xmlwriter*| |php-xmlwriter, if provided as a separate package by the distributor.| |*session*| |php-session, if provided as a separate package by the distributor.| |*sockets*| |php-net-socket (*--enable-sockets*). Required for user script support.| |*mbstring*| |php-mbstring (*--enable-mbstring*)| |*gettext*| |php-gettext (*--with-gettext*). Required for translations to work.| |*ldap*| |php-ldap. Required only if LDAP authentication is used in the frontend.| |*openssl*| |php-openssl. Required only if SAML authentication is used in the frontend.| |*mysqli*| |Required if MySQL is used as Zabbix backend database.| |*oci8*| |Required if Oracle is used as Zabbix backend database.| |*pgsql*| |Required if PostgreSQL is used as Zabbix backend database.|  ::: noteclassic Zabbix may work on previous versions of Apache, MySQL, Oracle, and PostgreSQL as well. :::  ::: noteimportant For other fonts than the default DejaVu, PHP function [imagerotate](http://php.net/manual/en/function.imagerotate.php) might be required. If it is missing, these fonts might be rendered incorrectly when a graph is displayed. This function is only available if PHP is compiled with bundled GD, which is not the case in Debian and other distributions. :::
zh-cn	##### 前端  Zabbix 前端支持的最小屏幕宽度为 1200px。  |软件|版本|备注| |--------|--------|--------| |*Apache*|1.3.12 或更高版本|<| |*PHP*|7.2.5 或更高版本|不支持 PHP 8.0。| |PHP 扩展：|<|<| |*gd*|2.0.28 或更高版本|PHP GD 扩展必须支持 PNG (*--with-png-dir*)、JPEG (*--with-jpeg-dir*) 和 FreeType 2 (*--with-freetype-dir*)。| |*bcmath*|<|php-bcmath (*--enable-bcmath*)| |*ctype*|<|php-ctype (*--enable-ctype*)| |*libXML*|2.6.15 或更高版本|php-xml，如果由分发者作为单独的包提供。| |*xmlreader*|<|php-xmlreader，如果由分发者作为单独的包提供。| |*xmlwriter*|<|php-xmlwriter，如果由分发者作为单独的包提供。| |*session*|<|php-session，如果由分发者作为单独的包提供。| |*sockets*|<|php-net-socket (*--enable-sockets*)。需要用户脚本支持。| |*mbstring*|<|php-mbstring (*--enable-mbstring*)| |*gettext*|<|php-gettext (*--with-gettext*)。Required for translations to work.| |*ldap*|<|php-ldap.仅当在前端使用 LDAP 身份验证时才需要。| |*openssl*|<|php-openssl.仅当在前端使用 SAML 身份验证时才需要。| |*mysqli*|<|如果 MySQL 用作 Zabbix 后端数据库，则需要。| |*oci8*|<|如果使用 Oracle 作为 Zabbix 后端数据库，则需要。| |*pgsql*|<|如果使用 PostgreSQL 作为 Zabbix 后端数据库，则需要。|  ::: noteclassic Zabbix 也许可以在以前的Apache、MySQL、Oracle 和 PostgreSQL 版本上运行。 :::  ::: noteimportant 如果需要使用默认 DejaVu 以外的字体, 可能会需要 PHP 的 [imagerotate](http://php.net/manual/en/function.imagerotate.php) 函数。如果缺少，在 Zabbix 前端查看图形时可能会显示异常。该函数只有在使用捆绑的 GD 库编译 PHP 时才可用。在 Debian 和某些发行版本中，这个问题不存在。 :::

en-us	FTP
zh-cn	FTP

en-us	Full
zh-cn	填满

en-us	Full
zh-cn	填满

en-us	Full
zh-cn	填满

en-us	Full clone
zh-cn	全克隆

en-us	Fullscreen
zh-cn	全屏

en-us	Function
zh-cn	功能

en-us	fuzzytime() - Difference between item value (as timestamp) and Zabbix server timestamp is less than or equal to T seconds (1 - true, 0 - false)
zh-cn	fuzzytime() - 监控项值的时间戳和 Zabbix 服务器时间戳之间的差异小于或等于 T 秒（1 - true，0 - false）

en-us	General
zh-cn	一般

en-us	Generated in %s sec
zh-cn	产生于%s秒

en-us	Georgian (ka_GE)
zh-cn	格鲁吉亚（ka_GE）

en-us	German (de_DE)
zh-cn	德语 (de_DE)

en-us	Get content of web page. Returns web page source as text
zh-cn	获取网页。返回信息为网页源码或者TXT

en-us	Given expression is not a macro
zh-cn	此表达式不是宏

en-us	global housekeeping settings
zh-cn	全局管家设置

en-us	Global regular expression "%1$s" does not exist.
zh-cn	找不到全局正则表达式 "%1$s" 。

en-us	#### Global regular expressions  There is an advanced editor for creating and testing complex regular expressions in Zabbix frontend.  Once a regular expression has been created this way, it can be used in several places in the frontend by referring to its name, prefixed with @, for example, *\@mycustomregexp*.  To create a global regular expression:  -   Go to: *Administration → General* -   Select *Regular expressions* from the dropdown -   Click on *New regular expression*  The **Expressions** tab allows to set the regular expression name and add subexpressions.  ![](../../assets/en/manual/regular_expressions/global_regexp.png)  All mandatory input fields are marked with a red asterisk.  |Parameter|<|Description| |---------|-|---------------------------------------------------| |*Name*|<|Set the regular expression name. Any Unicode characters are allowed.| |*Expressions*|<|Click on *Add* in the Expressions block to add a new subexpression.| |<|*Expression type*|Select expression type:<br>**Character string included** - match the substring<br>**Any character string included** - match any substring from a delimited list. The delimited list includes a comma (,), a dot (.) or a forward slash (/).<br>**Character string not included** - match any string except the substring<br>**Result is TRUE** - match the regular expression<br>**Result is FALSE** - do not match the regular expression| |^|*Expression*|Enter substring/regular expression.| |*Delimiter*|<|A comma (,), a dot (.) or a forward slash (/) to separate text strings in a regular expression. This parameter is active only when "*Any character string included*" expression type is selected.| |*Case sensitive*|<|A checkbox to specify whether a regular expression is sensitive to capitalization of letters.|  A forward slash (/) in the expression is treated literally, rather than a delimiter. This way it is possible to save expressions containing a slash, without errors.  ::: noteimportant A custom regular expression name in Zabbix may contain commas, spaces, etc. In those cases where that may lead to misinterpretation when referencing (for example, a comma in the parameter of an item key) the whole reference may be put in quotes like this: *"\@My custom regexp for purpose1, purpose2"*.\ Regular expression names must not be quoted in other locations (for example, in LLD rule properties). :::  In the **Test** tab the regular expression and its subexpressions can be tested by providing a test string.  ![](../../assets/en/manual/regular_expressions/global_regexp_b.png)  Results show the status of each subexpression and total custom expression status.  Total custom expression status is defined as *Combined result*. If several sub expressions are defined Zabbix uses AND logical operator to calculate *Combined result*. It means that if at least one Result is False *Combined result* has also False status.
zh-cn	#### 全局正则表达式  Zabbix 前端有一个用于创建和测试复杂正则表达式的高级编辑器。  一旦以这种方式创建了正则表达式，就可以在前端的多个位置通过引用其名称（以 @ 为前缀）使用它，例如  *\@mycustomregexp*。  创建全局正则表达式：  -   点击 *Administration（管理） → General（一般）* -   从下拉列表中选择 *Regular expressions（正则表达式）*  -   点击 *New regular expression（新建正则表达式）*  **表达式** 选项卡允许设置正则表达式名称并添加子表达式。  ![](../../assets/en/manual/regular_expressions/global_regexp.png)  所有必填字段都标有红色星号。  |参数|<|描述| |---------|-|-----------| |*Name（名字）*|<|设置正则表达式名称。允许使用任何 Unicode 字符。| |*Expressions（表达式）*|<|单击表达式块中的 *Add（添加）* 以添加新的子表达式。| |<|*Expression type（表达式类型）*|选择表达式类型：<br>**Character string included（包含字符串）** - 匹配子字符串<br>**Any character string included（包含任何字符串）** - 匹配分隔列表中的任何子字符串。分隔列表包括逗号 （,）、点 （.）或正斜杠（/）。<br>**Character string not included（不包含字符串）** - 匹配除子字符串以外的任何字符串<br>**Result is TRUE（结果为 TRUE）** - 匹配正则表达式<br>**Result is FALSE（结果为 FALSE）** - 不匹配正则表达式| |^|*Expression（表达式）*|输入子字符串/正则表达式。| |*Delimiter（分隔符）*|<|逗号 (,)、点 (.) 或正斜杠 (/) 用于分隔正则表达式中的文本字符串。当选择“*包含任意字符串*”的表达式类型时，此参数才有效 。| |*Case sensitive（区分大小写）*|<|一个复选框，用于指定正则表达式对大小写字母的敏感性。|  表达式中的正斜杠 (/) 按字面意思处理，而不是分隔符。这样就可以保存包含斜杠的表达式而不会出错。  ::: noteimportant Zabbix 中的自定义正则表达式名称可能包含逗号、空格等。在那些可能导致引用时误解的情况下（例如，监控项键值参数中的逗号）整个引用可能会像这样放在引号中：*"\@My custom regexp for purpose1, purpose2"*。 正则表达式名称不得在其他位置引用（例如，在 LLD 规则属性中）。 :::  在 **测试** 选项卡中，可以通过提供测试字符串来测试正则表达式及其子表达式。  ![](../../assets/en/manual/regular_expressions/global_regexp_b.png)  结果显示每个子表达式的状态和总的自定义表达式状态。  总自定义表达式状态定义为*组合结果*。如果定义了多个子表达式，Zabbix 使用 AND 逻辑运算符计算 *组合结果* 。这意味着如果至少一个 Result 为 False，*组合结果* 也为 False 状态。

en-us	Global script
zh-cn	全局脚本

en-us	Global scripts
zh-cn	全局脚本

en-us	Global value
zh-cn	全局值

en-us	GMT%1$s
zh-cn	GMT %1$s

en-us	Go back to %1$s
zh-cn	返回 %1$s

en-us	Google Chrome
zh-cn	谷歌 Chrome

en-us	Go to
zh-cn	到

en-us	Go to dashboard
zh-cn	转到仪表板

en-us	Gradient line
zh-cn	梯度线

en-us	Graph
zh-cn	图形

en-us	Graph "%1$s" already exists on "%2$s".
zh-cn	图形"%1$s"已存在于"%2$s"中.

en-us	Graph "%1$s" already exists on "%2$s" (inherited from another template).
zh-cn	图形"%1$s"已存在于"%2$s"中 (继承自其它的模板).

en-us	Graph "%1$s" already exists on "%2$s" (items are not identical).
zh-cn	图形"%1$s"已存在于"%2$s"中 (项目不一致).

en-us	Graph "%1$s" cannot inherit. No required items on "%2$s".
zh-cn	图形"%1$s"不能继承. "%2$s"中并无所要的项目.

en-us	Graph "%1$s" cannot inherit. No required items on "%2$s" (Ymax value item).
zh-cn	图形"%1$s"不能继承. "%2$s"中并无所要的项目 (Ymax值项目).

en-us	Graph "%1$s" cannot inherit. No required items on "%2$s" (Ymin value item).
zh-cn	图形"%1$s"不能继承. "%2$s"中并无所要的项目 (Ymin值项目).

en-us	Graph "%1$s" does not exist on template "%2$s".
zh-cn	图形 "%1$s"不存在于模板"%2$s"中.

en-us	Graph "%1$s" with templated items cannot contain items from other hosts.
zh-cn	含模板项目的图形"%1$s"不能包含其它主机的项目.

en-us	Graph added
zh-cn	图形已添加

en-us	Graph (classic)
zh-cn	图表（经典）

en-us	Graph copied
zh-cn	图表复制

en-us	Graph deleted
zh-cn	图形已删除

en-us	Graph element
zh-cn	图形组件

en-us	Graph prototype
zh-cn	图形原型

en-us	Graph prototype "%1$s" contains item prototypes from multiple discovery rules.
zh-cn	数据图模板 "%1$s" 包含来自多个自动发现规则上的监控项目模板

en-us	Graph prototype "%1$s" must have at least one item prototype.
zh-cn	数据图模板"%1$s"必须要有至少一个监控项目模板

en-us	Graph prototype "%1$s" with templated items cannot contain items from other hosts.
zh-cn	含模板项目的图形原型"%1$s"不能包含其它主机的项目.

en-us	Graph prototype added
zh-cn	数据图模板已添加

en-us	Graph prototype deleted
zh-cn	数据图模板已删除

en-us	Graph prototype not found.
zh-cn	数据图模板没有找到

en-us	Graph prototypes
zh-cn	图形原型

en-us	Graph prototypes deleted
zh-cn	数据图模板已经删除

en-us	Graph prototype updated
zh-cn	数据图模板已更新

en-us	Graph prototype with ID "%1$s" is not available.
zh-cn	ID为 "%1$s" 的聚合图形不可用。

en-us	Graphs
zh-cn	图形

en-us	Graphs deleted
zh-cn	图形已删除

en-us	Graph sum
zh-cn	图形总数

en-us	Graph type
zh-cn	图形类别

en-us	Graph updated
zh-cn	图形已更新

en-us	Graph with ID "%1$s" is not available.
zh-cn	ID为 "%1$s" 的图表不可用。

en-us	Graph with name "%1$s" already exists in graphs or graph prototypes.
zh-cn	图表名称 "%1$s" 已经存在在图表或者图表原型.

en-us	Graph with same name but other type exist.
zh-cn	同名但不同类型的图形已存在.

en-us	Greek (el_GR)
zh-cn	希腊(el_GR)

en-us	Grid
zh-cn	网格

en-us	Group
zh-cn	群组

en-us	Group "%1$s" cannot be deleted, because it is used by a host prototype.
zh-cn	组"%1$s" 不可以被删除，因为它正在被主机模板使用

en-us	Group "%1$s" cannot be deleted, because it is used in a correlation condition.
zh-cn	"%1$s" 组因为他的关联条件无法删除。

en-us	Group "%1$s" does not exist.
zh-cn	群组 "%1$s" 不存在.

en-us	Group "%1$s" for host "%2$s" does not exist.
zh-cn	主机 "%2$s" 的群组 "%1$s" 不存在.

en-us	Group added
zh-cn	群组已添加

en-us	Group deleted
zh-cn	组已删除

en-us	Group for discovered hosts
zh-cn	自动发现到的主机的群组

en-us	Group for discovered hosts "%1$s".
zh-cn	应用于被自动发现主机 "%1$s"的主机组

en-us	Grouping by
zh-cn	群组化之于

en-us	Group name
zh-cn	组名

en-us	Group prototype cannot be based on a discovered host group "%1$s".
zh-cn	组模板不可以基于一个已经被自动发现的主机组"%1$s"

en-us	Group prototypes
zh-cn	组模板

en-us	Groups
zh-cn	群组

en-us	Group updated
zh-cn	群组已更新

en-us	GSM modem
zh-cn	GSM 调制解调器

en-us	GUI
zh-cn	界面设置

en-us	GUI access disabled.
zh-cn	图形化界面已经被禁用。

en-us	h
zh-cn	h

en-us	Hardware
zh-cn	硬件

en-us	Hardware (Full details)
zh-cn	硬件(全细节)

en-us	Hardware sensor reading. Returns float
zh-cn	硬件传感器读数。返回浮点型

en-us	Headers
zh-cn	头

en-us	Hebrew (he_IL)
zh-cn	希伯来语（he_IL）

en-us	Height
zh-cn	高

en-us	Help
zh-cn	帮助

en-us	Hexadecimal to decimal
zh-cn	十六进制到十进制

en-us	hh
zh-cn	hh

en-us	hh.mm
zh-cn	hh.mm

en-us	H:i
zh-cn	H:i

en-us	Hidden
zh-cn	隐藏的

en-us	Hide debug
zh-cn	隐藏调试

en-us	Hide groups without problems
zh-cn	隐藏组没有问题

en-us	Hide selected
zh-cn	隐藏所选的

en-us	Hierarchy
zh-cn	阶

en-us	Hierarchy
zh-cn	阶

en-us	Hierarchy
zh-cn	阶

en-us	High
zh-cn	严重

en-us	High-contrast dark
zh-cn	高对比度暗色

en-us	High-contrast light
zh-cn	高对比度亮色

en-us	Highlight whole row
zh-cn	高亮整行

en-us	H:i:s
zh-cn	H:i:s

en-us	History
zh-cn	历史记录

en-us	History cleared
zh-cn	历史已清除

en-us	History clearing can take a long time. Continue?
zh-cn	历史清除可能会很久。继续吗?

en-us	History data selection
zh-cn	选择历史数据

en-us	History data storage period
zh-cn	历史数据存储时间

en-us	History data storage period "%1$s".
zh-cn	历史数据存储期 "%1$s"。

en-us	History of events
zh-cn	事件历史

en-us	History storage period
zh-cn	历史数据保留时长

en-us	Horizontal
zh-cn	横向

en-us	Horizontal align
zh-cn	横向对齐

en-us	host
zh-cn	主机

en-us	Host
zh-cn	主机

en-us	Host "%1$s" already exists.
zh-cn	主机 "%1$s" 已存在.

en-us	Host "%1$s" cannot be without host group.
zh-cn	主机 "%1$s" 没有设置主机组

en-us	Host "%1$s" is monitored with proxy "%2$s".
zh-cn	主机"%1$s"是以agent代理程序"%2$s"来监控的.

en-us	Host access
zh-cn	主机存取

en-us	Host added
zh-cn	已添加主机

en-us	Host (ascending)
zh-cn	主机(升序)

en-us	Host cannot have more than one default interface of the same type.
zh-cn	主机不能有超过一个同类型的默认接口.

en-us	Host count
zh-cn	主机计数

en-us	Host deleted
zh-cn	主机已删除

en-us	Host disabled
zh-cn	主机已被禁用

en-us	Host enabled
zh-cn	主机已启用

en-us	host group
zh-cn	主机群组

en-us	Host group
zh-cn	主机群组

en-us	Host group "%1$s" already exists.
zh-cn	主机群组 "%1$s" 已存在.

en-us	Host group "%1$s" cannot be deleted, because it is used in a global script.
zh-cn	主机群组“%1$s”不能被删除，因为它被用于全局脚本

en-us	Host group "%1$s" is internal and can not be deleted.
zh-cn	主机群组 "%1$s" 为内建的且不能被删除

en-us	Host group elements
zh-cn	主机群组组件

en-us	Host group issues
zh-cn	主机群组问题

en-us	Host group label type
zh-cn	主机群组标签类型

en-us	Host groups
zh-cn	主机群组

en-us	Host group with ID "%1$s" is not available.
zh-cn	ID为 "%1$s" 主机组不可用。

en-us	hostid of dependent item and master item should match
zh-cn	依赖项目和主项目的hostid应该匹配

en-us	Host info
zh-cn	主机信息

en-us	Host interface
zh-cn	主机接口

en-us	Host inventory
zh-cn	主机资产记录

en-us	Host inventory overview
zh-cn	主机资产记录概览

en-us	Host IP
zh-cn	主机IP地址

en-us	host is not monitored
zh-cn	主机不受监控

en-us	Host issues
zh-cn	主机问题

en-us	"host:key" pair is expected
zh-cn	“主机：key值” 关键的预计

en-us	Host label type
zh-cn	主机标签类型

en-us	Host macros
zh-cn	主机宏

en-us	Host metadata
zh-cn	主机元数据

en-us	Host name
zh-cn	主机名称

en-us	Host networks
zh-cn	主机网络

en-us	host pattern
zh-cn	主机样式

en-us	Host prototype
zh-cn	原型主机

en-us	Host prototype "%1$s" already exists on "%2$s".
zh-cn	主机模板"%1$s"已存在于"%2$s"

en-us	Host prototype "%1$s" already exists on "%2$s", inherited from another template.
zh-cn	主机模板 "%1$s"已存在于"%2$s", 它继承自其它模板

en-us	Host prototype added
zh-cn	主机模板已添加

en-us	Host prototype deleted
zh-cn	主机模板已删除

en-us	Host prototypes
zh-cn	主机模板

en-us	Host prototypes deleted
zh-cn	主机模板已删除

en-us	Host prototype updated
zh-cn	主机模板已更新

en-us	Host prototype with host name "%1$s" already exists in discovery rule "%2$s".
zh-cn	主机名称为 "%1$s" 的主机模板已经存在于自动发现规则 "%2$s"中.

en-us	Host prototype with visible name "%1$s" already exists in discovery rule "%2$s".
zh-cn	显示名称为"%1$s"的主机模板已存在于自动发现规则"%2$s"中.

en-us	Host router
zh-cn	主机路由

en-us	Hosts
zh-cn	主机

en-us	Hosts and groups
zh-cn	主机和组

en-us	Host screens
zh-cn	主机聚合图形

en-us	Hosts location
zh-cn	主机位置

en-us	Host subnet mask
zh-cn	主机子网掩码

en-us	Hosts updated
zh-cn	主机已更新

en-us	Host time
zh-cn	主机时间

en-us	Host updated
zh-cn	主机已更新

en-us	Host update failed.
zh-cn	主机更新失败.

en-us	Host with ID "%1$s" is not available.
zh-cn	ID为 "%1$s" 的主机不可用

en-us	Host with the same name "%1$s" already exists.
zh-cn	主机名称为"%1$s"的主机已存在

en-us	Host with the same name "%s" already exists.
zh-cn	名称同样为 "%s" 的主机已存在.

en-us	Host with the same visible name "%1$s" already exists.
zh-cn	显示名称为"%1$s" 的主机已经存在

en-us	Host with the same visible name "%s" already exists.
zh-cn	可视名称同样为 "%s" 的主机已存在.

en-us	Hours
zh-cn	时

en-us	Housekeeping
zh-cn	管家

en-us	HTTP
zh-cn	HTTP

en-us	HTTP agent
zh-cn	HTTP 代理

en-us	HTTP authentication
zh-cn	HTTP认证

en-us	HTTP login form
zh-cn	HTTP 登录表格

en-us	HTTP proxy
zh-cn	HTTP 代理

en-us	HTTPS
zh-cn	HTTPS

en-us	HTTP settings
zh-cn	HTTP 设置

en-us	Hungarian (hu_HU)
zh-cn	匈牙利(hu_HU)

en-us	HW architecture
zh-cn	硬件架构

en-us	ICMP ping
zh-cn	ICMP ping

en-us	icon
zh-cn	图标

en-us	Icon
zh-cn	图标

en-us	Icon (default)
zh-cn	图标(默认)

en-us	Icon (disabled)
zh-cn	图标(停用的)

en-us	Icon highlight
zh-cn	图标高亮

en-us	Icon (maintenance)
zh-cn	图标(维修)

en-us	Icon map
zh-cn	图标映射

en-us	Icon map "%1$s" cannot be deleted. Used in map "%2$s".
zh-cn	图标映射"%1$s"无法被删除. 已用映射"%2$s"中.

en-us	Icon map created
zh-cn	图标映射已创建

en-us	Icon map deleted
zh-cn	图标映射已删除

en-us	Icon mapping
zh-cn	图标映射

en-us	Icon map "%s" already exists.
zh-cn	图标映射"%s"已存在.

en-us	Icon map updated
zh-cn	图标映射已更新

en-us	Icon (problem)
zh-cn	图标(问题)

en-us	Icons
zh-cn	图标

en-us	Icon with ID "%1$s" is not available.
zh-cn	ID为 "%1$s" 的图标不可用。

en-us	ID
zh-cn	ID

en-us	Identification of the system. Returns string
zh-cn	识别系统。返回 字符串

en-us	If you think this message is wrong, please consult your administrators about getting the necessary permissions.
zh-cn	假如您认为这个信息是错的, 请咨询您的管理员关于如何取得需要的权限.

en-us	image
zh-cn	图片

en-us	Image
zh-cn	图片

en-us	Image "%1$s" already exists.
zh-cn	图片"%1$s"已经存在

en-us	Image added
zh-cn	图片已添加

en-us	Image deleted
zh-cn	图片已删除

en-us	Image label type
zh-cn	图片标签类型

en-us	Image load error [%1$s] in [%2$s].
zh-cn	图片加载错误[%1$s] in [%2$s]

en-us	Images
zh-cn	图片

en-us	Images for all maps will be updated!
zh-cn	所有拓扑图都将被更新!

en-us	Image updated
zh-cn	图片已更新

en-us	IMAP
zh-cn	IMAP

en-us	Immediately
zh-cn	立即地

en-us	Import
zh-cn	导入

en-us	Imported successfully
zh-cn	已成功导入

en-us	Import failed
zh-cn	导入失败

en-us	Import file
zh-cn	导入文件

en-us	Impossible to filter by inventory field "%s", which does not exist.
zh-cn	不可能以不存在的资产纪录栏位"%s"来过滤.

en-us	in
zh-cn	在

en-us	Inaccessible graph
zh-cn	不能访问的图表

en-us	Inaccessible group
zh-cn	不能访问的组

en-us	Inaccessible host
zh-cn	无法访问的主机

en-us	Inaccessible item
zh-cn	无法访问的项

en-us	Inaccessible maintenance
zh-cn	无法访问的维护

en-us	Inaccessible map
zh-cn	无法访问的拓扑图

en-us	Inaccessible template
zh-cn	无法访问的模板

en-us	Inaccessible trigger
zh-cn	无法访问的触发器

en-us	Inaccessible user
zh-cn	用户无法访问

en-us	Include
zh-cn	包含

en-us	Include subgroups
zh-cn	包括子组

en-us	including subgroups
zh-cn	包括子组