## Problem When an analyzer fails, it can be confusing why that has happened. Similarly, when a user is attempting to use one of our many documented configuration options, it can be confusing when the variable appears not to take effect. This can lead to an unsatisfying DIY support and debugging experience, and to inefficient interactions with GitLab Support or in `gitlab-org/gitlab` issues. Often, the first instruction is a request to enable debugging logs or otherwise collect more information. ## Proposal 1. Guide users to enable `debug` logging when we can. 1. Provide as much information as is feasible at each log level. 1. Provide important version and config info at the default level. 1. Provide complete version + config information at debug level or lower. ## Scope This proposal originated in Static Analysis for support of SAST analyzers, but these improvements should be usable in other analyzers too.