For graphs with many items added, legend could grow pretty huge, and there might be other reasons why somebody might want to hide the legend. Starting with Zabbix 2.0.0, that is possible for custom graphs 21 Warning when a too large file is attempted to be uploaded Previously it was not easy to debug why some upload failed if it exceeded PHP option max_upload_filesize limit. Now Zabbix shows a warning NOTSUPPORTED (on 2.0.11 it caused NOTSUPPORTED). * Zabbix agent log file can be helpful to find out why a ''log[]'' or ''logrt[]'' item became NOTSUPPORTED. Zabbix can monitor its agent log file except when

list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data /var/lib/zabbix --no-create-home zabbix Attention: Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e back the database changes so users will be forced to upgrade PHP using 3rd party packages. This is why Zabbix server is also deprecated on RHEL 6. If you still want to use Zabbix frontend on RHEL 6 and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 1 Why use Proxy? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . notification of predefined events • high-level (business) view of monitored resources • audit log 1.3 Why use Zabbix? 7 • Open Source solution • highly efficient agents for UNIX and WIN32 based platforms in-memory optimisations. 7.2.4 Other server improvements • Processes now provide more information on why they terminate. This should help greatly with Zabbix daemon debugging. • Reduced amount of memory

list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data /var/lib/zabbix --no-create-home zabbix 56 Attention: Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e selectbox. Note: All access permissions are assigned to host groups, not individual hosts. That is why a host must belong to at least one group. IP address • Enter the IP address of the host. Note that

messages were suppressed, it was not always easy for users to understand what generated those events and why. Acknowledgement information of the original event was also lost. In the new version, the old mechanism list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data selectbox. Note: All access permissions are assigned to host groups, not individual hosts. That is why a host must belong to at least one group. 76 IP address • Enter the IP address of the host. Note

problem/events tables is now larger. Note that for internal events the name contains an error message why an object changed its state; upon recovery no name is used. For discovery and auto-registration events list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data /var/lib/zabbix --no-create-home zabbix Attention: Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e

• Disabled input fields previously were not distinguished much, which could create confusion as to why they were not available for editing. Now these fields are distinguished with a grey background, for ** More details about unsupported agent items ** Zabbix agents now provide detailed information on why items become not supported, instead of the generic ”Not supported by Zabbix Agent”. This was achieved frontend, when rolling the mouse over the error icon, you may expect to see more specific messages about why an item went unsuported. ... A single message before Zabbix 2.4.0. More informative messages in Zabbix

allow to return the number of interest residing in the target file at the end of lines 3-5. The reason why Zabbix will return only the number is because output here is defined by \1 referring to the first log file but do not make the item NOTSUPPORTED. * Zabbix agent log file can be helpful to find out why a ''log[]'' or ''logrt[]'' item became NOTSUPPORTED. Zabbix can monitor its agent log file except when list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data

list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data /var/lib/zabbix --no-create-home zabbix Attention: Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e back the database changes so users will be forced to upgrade PHP using 3rd party packages. This is why Zabbix server is also deprecated on RHEL 6. If you still want to use Zabbix frontend on RHEL 6 and

list of the items which are active that is then stored in a cache within the Zabbix server. This is why it can take up to two minutes for any changes made in Zabbix frontend to show up in the latest data /var/lib/zabbix --no-create-home zabbix 54 Attention: Zabbix processes do not need a home directory, which is why we do not recommend creating it. However, if you are using some functionality that requires it (e back the database changes so users will be forced to upgrade PHP using 3rd party packages. This is why Zabbix server is also deprecated on RHEL 6. If you still want to use Zabbix frontend on RHEL 6 and