MongoDB

Supported versions

NeoLoad supports MongoDB 2.2 to 3.4.

For 2.6 and later MongoDB versions, the equivalent YAML-based configuration is:

net:
 http:
  enabled: true
  RESTInterfaceEnabled: true

Do not use tabs, only spaces are accepted.

For more information, see:

Connection settings

MongoDB monitors allow monitoring MongoDB database servers. The counters are sorted by category: operations, memory, and so on.

Authentication enabled for 3.0.x to 3.4.x MongoDB versions

The authentication mechanism in 3.0.x to 3.4.x versions of MongoDB is SCRAM-SHA-1 by default.

The MongoDB REST interface does not support the SCRAM-SHA-1 authentication mechanism.

You must then create a user who is using the MONGODB-CR authentication mechanism (which is supported by the REST interface).

  1. Stop your running Mongo database and restart it with authentication disabled.
  2. Run a Mongo shell and change the authentication schema temporarily.

    > use admin;
    > var schema = db.system.version.findOne({"_id" : "authSchema"});
    > schema.currentVersion;
    5
    > schema.currentVersion = 3
    > db.system.version.save(schema);
  3. In your Mongo shell, create your user (which will be in MONGODB-CR):
    > use admin; // (If it is a new shell do not forget to create the user on the "admin" database)
    > db.createUser({user: "myUser",pwd: "myPassword",roles: ["root"]});

  4. Test your connection with this newly created user by restarting your Mongo database with authentication enabled:
  5. Now that it works, do not forget to rollback to the standard authentication schema:
    1. Stop your running Mongo database and restart it with authentication disabled.
    2. In a Mongo shell:
      > use admin;
      > var schema = db.system.version.findOne({"_id" : "authSchema"});
      > schema.currentVersion;
      3
      > schema.currentVersion = 5
      > db.system.version.save(schema);

    3. Restart your Mongo database with authentication enabled.

Create a MongoDB monitor

NeoLoad makes it possible to create a new monitor either using the monitored machine creation wizard, as described in Create and configure a monitored machine, or from an existing monitored machine, as described in Create and configure a monitor.

After defining the MongoDB monitor, the wizard displays the list of the databases to monitor.

Choosing a specific database automatically selects the default counters for this database.

Alerts can be set as described in Configure a counter alert threshold.

Available counters