Zabbix 2.0 Manual
DOS compatibility mode by entering c. Proceeding with it disabled will damage the partition. Then delete the existing partition and create new one with desired size. In majority of cases you will accept and directly attached to the current template. Delete the template; entities of the template (items, triggers, etc) remain with the linked hosts. Delete the template and all its entities from linked hosts should be handled by the user. The log rotation should first rename the old file and only later delete it so that no traps are lost: 1. Zabbix opens the trap file at the last known location and goes0 码力 | 791 页 | 9.66 MB | 1 年前3Zabbix 2.4 Manual
there since they are still on the original template. For this situation, Zabbix 2.4 offers a new Delete missing option for deleting resources that are not in the imported XML file. This option is implemented removed from Template App Zabbix Server. In order to fix it, either manually delete the item or import the new template and mark Delete missing option for items. Case-sensitive MySQL database A case-sensitive DOS compatibility mode by entering c. Proceeding with it disabled will damage the partition. Then delete the existing partition and create new one with desired size. In majority of cases you will accept0 码力 | 910 页 | 10.81 MB | 1 年前3Zabbix 2.2 Manual
comparison and the condition and the result is displayed correctly. • Instead of checkboxes and Delete button, Remove links for each entry are used Maintenance period configuration form has been redesigned redesigned, including a more compact layout and Remove links instead of check- boxes and a Delete selected link. Most forms will now auto-focus on the first field. The list of actions will now display rules and can be used to manage host prototypes. It comes with the standard get, create, update, delete, isreadable and iswritable methods. ** Changes to the get method ”output” parameter ** The ”output”0 码力 | 918 页 | 11.28 MB | 1 年前3Zabbix 3.2 Manual
Check-boxes are enabled to apply mass operations to them. Thus it is possible to enable/disable/delete them. Items created by low-level discovery before 3.2.0. Items created by low-level discovery in not be deleted until the related problem record is removed. Additionally, the housekeeper now will delete problems first and events after, to avoid potential problems with stale events or problem records status. From now on, if housekeeping of events is enabled then deleting an item/trigger will also delete events and problems generated by that item/trigger. If housekeeping of events is disabled then only0 码力 | 1012 页 | 12.11 MB | 1 年前3Zabbix 3.4 Manual
They can see and clone a dashboard if they have at least READ rights to it; • They can edit and delete dashboard only if they have READ/WRITE rights to it; • They cannot change the dashboard owner. not be deleted until the related problem record is removed. Additionally, the housekeeper now will delete problems first and events after, to avoid potential problems with stale events or problem records Note that you may also use ’update’ instead of ’upgrade’ in these commands. While ’upgrade’ will delete obsolete packages, ’update’ will preserve them. 2 Debian/Ubuntu Overview Make sure to read general0 码力 | 1136 页 | 15.03 MB | 1 年前3Zabbix 3.0 Manual
list can be deleted using the Remove link, rather than having to mark check-boxes and then click on Delete selected. Check-boxes have been removed. 5.20 Daemon improvements 5.20.1 Forced housekeeper execution mapping A value map API has been implemented. It comes with the standard get, create, update and delete methods. 5.25.3 Trends A trend API has been implemented. It comes with the standard get method make small changes in files located in the build\win32\project directory: * In ''Makefile_tls'' delete ''/DHAVE_OPENSSL_WITH_PSK''. i.e. find65 CFLAGS = $(CFLAGS) /DHAVE_OPENSSL /DHAVE_OPEN
0 码力 | 1074 页 | 12.04 MB | 1 年前3Zabbix 1.8 Manual
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 delete() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 delete() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 delete() . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 485 页 | 9.28 MB | 1 年前3Zabbix 4.0 Manual
Templates you can import them manually into Zabbix. If templates with the same names already exist, the Delete missing options should be checked when importing to achieve a clean import. This way the old items template linkage During host or template import it is now possible to update template linkage using the Delete missing option. If using this option any template linkage that does not also exist in the import it is recommended that you delete the CMake cache before attempting to repeat the CMake build process. In the CMake GUI, the cache can be deleted by selecting ”File > Delete Cache”. 14. The build directory0 码力 | 1365 页 | 16.69 MB | 1 年前3Zabbix 4.2 Manual
it is recommended that you delete the CMake cache before attempting to repeat the CMake build process. In the CMake GUI, the cache can be deleted by selecting ”File > Delete Cache”. 14. The build directory make small changes in files located in the build\win32\project directory: * In ''Makefile_tls'' delete ''/DHAVE_OPENSSL_WITH_PSK''. i.e. findCFLAGS = $(CFLAGS) /DHAVE_OPENSSL /DHAVE_OPENSSL_WITH_PSK
and Note that you may also use ’update’ instead of ’upgrade’ in these commands. While ’upgrade’ will delete obsolete packages, ’update’ will preserve them. Adding Jabber notifications support to Zabbix server0 码力 | 1270 页 | 15.64 MB | 1 年前3Zabbix 6.2 Manual
the Configuration → Templates section. If a template with the same name already exists, check the Delete missing option before importing to achieve a clean import. This way the items that have been excluded to the UUID of the imported entity. In another improvement, when removing template linkage (the Delete missing option for template linkage) through the imported template or host, the inherited entities are missing in the import file and the Delete missing option for the specific entity is marked. Due to this change, the warning message when marking the Delete missing option for template linkage will0 码力 | 1689 页 | 22.82 MB | 1 年前3
共 26 条
- 1
- 2
- 3