Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-8725

MAX accepted value of DebugLevel changed to 5 instead of 4 for server, proxy and agent.

(1) let's update daemon configuration files to reflect this change

glebs.ivanovskis RESOLVED in r54429

asaveljevs r54429 adds the following for agent and server, respectively:

#	5 - extended debugging (Currently, same as level 4)
#	extended debuging for web and VMware monitoring

It might not be a good idea to describe the current usage of LOG_LEVEL_TRACE, because it is likely to change and, when one introduces LOG_LEVEL_TRACE into the code, he has to always remember to update the configuration file, too, which is error prone.

Note that since ZBXNEXT-679 trace logging is used in authenticated SMTP (not mentioned in the DebugLevel comment for server) and in ZBXNEXT-1263 it will be used by low-level TLS calls.

There is also a typo in the word "debuging". REOPENED.

glebs.ivanovskis RESOLVED in r54430
LOG_LEVEL_TRACE is now described in a more general manner for all daemons:

#	5 - extended debugging (produces even more information)

wiper CLOSED

(2) Following places in documentation should be updated.

https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_server
https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_proxy
https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_agentd
https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_agentd_win
Should state the following: "5 - extended debugging (produces even more information)".
Commentary "(can be set only using runtime control options)" should be removed.

https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_agentd
https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_agentd_win
Colon needed after "Specifies debug level". Also applicable to documentation for earlier versions.

https://www.zabbix.com/documentation/2.4/manual/appendix/config/zabbix_agentd_win
DebugLevel=5 ability should be documented.

glebs.ivanovskis RESOLVED
Changes reflected in What's New section as well
https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew300?&#default_configuration_file_improvements

wiper It's not default configuration file improvement, as we haven't changed default DebugLevel. I think it should be listed in Miscellaneous improvements.
REOPENED

glebs.ivanovskis In What's new section moved description to a separate subsection under Daemon improvements section:
https://www.zabbix.com/documentation/3.0/manual/introduction/whatsnew300
Added description to Upgrade notes:
https://www.zabbix.com/documentation/3.0/manual/installation/upgrade_notes_300
RESOLVED

wiper In upgrade notes we should list changes that could affect the operation of already running installations. So I removed the section about DebugLevel to 5.
Personally I would also change the header 'Setting DebugLevel=5 in daemon configuration file' in what's new to something like 'Increased maximum allowed DebugLevel in configuration files', but I'm far from being the best judge on this.

CLOSED

<richlv> spotted a few more places :

• https://www.zabbix.com/documentation/3.0/manual/vm_monitoring#extended_monitoring
• https://www.zabbix.com/documentation/3.0/manual/web_monitoring#extended_monitoring

REOPENED

glebs.ivanovskis Thank you for being eagle-eyed! Fixed wording there as well, please review.
RESOLVED

<richlv> more like accidentally stumbling on it
vmware page now refers both to server & proxy config sections, while web monitoring - to server only. probably worth referring to proxy in the webmon page, too

glebs.ivanovskis I was erroneously thinking that web monitoring is performed by server only, my bad. Now fixed.

<richlv> looks great, thank you

CLOSED

Successfully tested

Fixed in pre-2.5.0 (trunk) r54858.