Zabbix 1.8 Manualcurrent problems, and it was possible to display recent events for all the problems, limited by day count. In 1.8, this screen gained has been changed, providing new features like expanding individual triggers Clicking the icon opens the popup to allow copying of the message. 2.11.2 History strings saved by reference At the top of the frontend, there’s a breadcrumbs type history, showing recently accessed pages slows down frontend considerably. Zabbix 1.8 supports splitting long lists in multiple pages. Entry count per page is configurable in user’s profile. |<| |<| |-| |<| |<| |-| 2.11.4 Selected rows are highlighted0 码力 | 485 页 | 9.28 MB | 1 年前3
Zabbix 4.4 Manual. . . . . . . . . 785 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790 Appendix 1. Reference commentary . . . . . . . . . this period, instead of all values. The aggregation options are as follows: • min • max • avg • count • sum • first (first value displayed) • last (last value displayed) The most exciting use of data the tags of the respective host item. Additionally the expression tag of these triggers does not reference the host or item, but only the function ({last()}<>0 in the example):Host 0 码力 | 1393 页 | 16.55 MB | 1 年前3
Zabbix 6.4 Manual. . . . . . . . . 861 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866 Appendix 1. Reference commentary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795 22 Quick reference guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . possible to revert a symptom problem back to a cause problem. New {EVENT.CAUSE.*} macros allow to reference the cause event in the symptom event notifications, while {EVENT.SYMPTOMS} allows to retrieve a0 码力 | 1885 页 | 29.12 MB | 1 年前3
Zabbix 7.0 Manual. . . . . . . . . 873 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877 Appendix 1. Reference commentary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854 22 Quick reference guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the chosen period. The aggregated value can be displayed as: • minimum • maximum • average • count • sum • first • last These added features are useful for creating data comparison widgets. For0 码力 | 1949 页 | 31.91 MB | 1 年前3
Zabbix 6.2 Manual. . . . . . . . . 854 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859 Appendix 1. Reference commentary . . . . . . . . . Previously, host groups were used to organize both hosts and templates. Now this functionality has been split into template groups, which may contain templates only, and host groups, which may contain hosts only with zero inodes vfs.fs.get agent items are now capable of reporting file systems with the inode count equal to zero, which can be the case for file systems with dynamic inodes (e.g. btrfs). Additionally0 码力 | 1689 页 | 22.82 MB | 1 年前3
Zabbix 5.0 Manual. . . . . . . . . 904 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 Appendix 1. Reference commentary . . . . . . . . . unsupported by Zabbix agent2 Use the AllowKey/DenyKey parameters instead. Templates excluded from host count in System information report The number of hosts displayed in the System information report and widget displayed in a separate row. Modification time ignored in log, log.count items File modification time is now ignored in log and log.count items. Enhanced URL widget security The URL dashboard widget and0 码力 | 1561 页 | 28.27 MB | 1 年前3
Zabbix 5.4 Manual. . . . . . . . . 920 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925 Appendix 1. Reference commentary . . . . . . . . . item key, host group and tags • The new syntax supports other expressions as parameters • Item reference is now the first parameter of history functions (as host/item) • Changed syntax for expression parameter persistent_dir specifies a directory for storing a file with a state of log[], log.count[], logrt[] or logrt.count[] item. The state includes the log file name, size, position how far the log file was0 码力 | 1825 页 | 20.03 MB | 1 年前3
Zabbix 2.0 Manualmatch order, expression for matching (PCRE regular expression or Zabbix expression), icon and reference to an inventory field. Icon map can be assigned to a map in the map configuration form, and overridden specify different DNS server than localhost • Both items gained ability to specify timeout and retry count (not supported on Windows) • net.dns gained support for specifying DNS record type like A, CNAME cpu.load now accepts percpu as the first parameter - if specified, total load divided by online CPU count is returned (default is still all and returns normal load value) vm.memory.size now supports more0 码力 | 791 页 | 9.66 MB | 1 年前3
Zabbix 2.2 Manual. . . . . . . . . 416 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Appendix 1. Reference commentary . . . . . . . . . reading states of IPMI discrete sensors. A new function band() (bitwise AND) and an improved function count() can be used for testing state of bits of discrete sensors. 5.4 Loadable modules Loadable modules macro like {Cisco switch:ifAlias[{#SNMPINDEX}].last()} {HOST.HOST<1-9>} macro can be used to reference a host: {{HOST.HOST}:ifAlias[{#SNMPINDEX}].last()}. As the graph may contain items from several0 码力 | 918 页 | 11.28 MB | 1 年前3
Zabbix 4.2 Manual. . . . . . . . . 710 Method reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 Appendix 1. Reference commentary . . . . . . . . . discovery Separate processing for low-level discovery Processing low-level discovery rules has been split from data gathering processes into its own processing. See: Daemon improvements. Expected format Daemons Separate processing for low-level discovery Processing low-level discovery rules has been split from data gathering processes into its own processing, consisting of a config- urable number of low-level0 码力 | 1270 页 | 15.64 MB | 1 年前3
共 27 条
- 1
- 2
- 3













