[ZBX-5922] LogSlowQueries option enables only with DebugLevel=3 - should be documented Created: 2012 Nov 30  Updated: 2017 May 30  Resolved: 2013 Jul 26

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: 1.8.17, 2.0.5, 2.1.2

Type: Incident report Priority: Trivial
Reporter: Kodai Terashima Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: documentation, trivial
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

LogSlowQueries option in zabbix_server.log enables only with DebugLevel=3. This should be documented.



 Comments   
Comment by richlv [ 2012 Nov 30 ]

maybe it would be better to make it work with all debuglevels ? i don't see a reason why it would be silently ignored if some other parameter is set to a specific value

zalex_ua I support Rich, as we have this separate option (LogSlowQueries) which can be enabled/disabled by an user when required, then why it depends on some other things (DebugLevel) ?
But there could be an exception for DL=0 - no debug

Then it still should be documented in description for the LogSlowQueries.

kodai I also support Rich and Oleksiy!

Comment by Martins Valkovskis [ 2013 Feb 08 ]

Documented with the LogSlowQueries parameter as it currently is:

https://www.zabbix.com/documentation/1.8/manual/processes/zabbix_server
https://www.zabbix.com/documentation/1.8/manual/processes/zabbix_proxy
https://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_server
https://www.zabbix.com/documentation/2.0/manual/appendix/config/zabbix_proxy
https://www.zabbix.com/documentation/2.2/manual/appendix/config/zabbix_server
https://www.zabbix.com/documentation/2.2/manual/appendix/config/zabbix_proxy

sasha CLOSED

Comment by richlv [ 2013 Feb 15 ]

also added a note in server & proxy config files in 1.8, 2.0 & trunk - please, review

sasha reviewed and CLOSED

Comment by richlv [ 2013 Feb 15 ]

ZBXNEXT-1627 asks for this behaviour to be changed

Generated at Fri Mar 14 11:12:36 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.