Log level for WSL 2 specific debug messages; aka turn of chatty memory compaction messages.

I cannot easily find important messages with a quick dmessage because it is spammed full of memory compaction messages.

A .wsl2config setting with a log level setting info, warning,error,debug or a more specific setting for this message would be nice.

Workaround

Add a filter in syslog logstash or whatever logging tool I use.

Context: Testing cloud solutions with Ansible, Molecule and Docker

I spin up several Debian 10 Docker images with Molecule to test Ansible deployment scripts.
All have systemd and syslog and more enabled, actually a full Debian in Docker, not a typical Docker image deploy.
I configure syslog-ng on all machines, configure Elastic's filebeat, logstash and Elasticsearch to create a central logging solution for a deployment. All machines log the memory compaction messages with syslog-ng. Now I need to filter these debug messages in my logstash pr syslog-ng. On real environments I would not see these specific messages.

Start by reviewing the proposed .wsl2config log-level setting and the WSL 2 memory compaction messages described in the issue. Determine how the messages could be assigned a configurable level or filtered, and consider the syslog-ng, Logstash, and Docker-based testing context; done means important messages are no longer obscured by this output.