Control logging behavior of mongosh
It should be possible to control the logging behavior of mongosh, for example:
- verbosity
- what to log / log level
- retention time
- whether logging is enabled or not

-
Devon commented
we use mongosh as part of our application deployment process where we checkout release-specific artifacts from source code control, build a "work file (.js)" of all changes for the release, then execute that script by piping it into the mongosh. We are not able to retrieve commands or return results of the commands indicating success/failure. Instead, we see something like:
Atlas [mongos] test> myDB
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB>
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...More control over command capture and result verbosity is critical to determining success/failure of a deployment.