mtools is a collection of helper scripts to parse, filter, and visualize MongoDB log files (mongod, mongos). mtools also includes mlaunch, a utility to quickly set up complex MongoDB test environments on a local machine, and mtransfer, a tool for transferring databases between MongoDB instances.

The following tools are in the mtools collection:

mlogfilter

slices log files by time, merges log files, filters slow queries, finds table scans, shortens log lines, filters by other attributes, convert to JSON

mloginfo

returns info about log file, like start and end time, version, binary, special sections like restarts, connections, distinct view (requires numpy)

mplotqueries

visualize log files with different types of plots (requires matplotlib)

mlaunch

a script to quickly spin up local test environments, including replica sets and sharded systems (requires pymongo, psutil, packaging)

mtransfer

an experimental script to transfer databases between MongoDB instances by copying WiredTiger data files (requires pymongo and wiredtiger)

For more information, see the mtools documentation.

The mtools collection is written in Python, and most of the tools only use the standard packages shipped with Python. The tools are currently tested with Python 3.8, 3.9, 3.10, and 3.11.

Some of the tools have additional dependencies, which are listed under the specific tool's section. See the installation instructions for more information.

The mtools suite is only tested with actively supported <https://www.mongodb.com/support-policy/lifecycles> (non End-of-Life) versions of the MongoDB server. As of September 2023, that includes MongoDB 4.4 or newer.

See Changes to mtools for a list of changes from previous versions of mtools.

If you'd like to contribute to mtools, please read the contributor page for instructions.

This software is not supported by MongoDB, Inc. under any of their commercial support subscriptions or otherwise. Any usage of mtools is at your own risk. Bug reports, feature requests and questions can be posted in the Issues section on GitHub.