Choose diagnostic and query logging levels ​

There are two separate choices when collecting Coordinator DB diagnostics. Server XML controls diagnostic file verbosity. Database settings control whether structured query events are recorded and which duration threshold they must meet.

For request history, inspect the current effective values first:

SELECT name, value
FROM system.settings
WHERE name IN ('log_queries', 'log_queries_min_query_duration_ms')
ORDER BY name;

If the investigation requires every request, enable logging with a zero threshold:

SET log_queries = 1;
SET log_queries_min_query_duration_ms = 0;

SET persists database defaults and requires autocommit with no active transactions in that database. Consider the intended duration of that change and restore the chosen operational values when the investigation ends.

For diagnostic files, edit logger.level in the existing configuration and restart. Accepted levels include debug and information; client commands that request a per-query trace stream are not part of the documented interface. Increasing diagnostic verbosity does not override disabled structured query logging, and enabling query history does not change file verbosity.

See logger settings, logging settings and query history.