Mongo Throughput Test

Periodically, administrators should measure the workload on the Mongo database server and evaluate the server's ability to handle the load, so that they can figure out whether the server's sized commensurate to its load or not. Administrators can perform this load analysis using the Mongo Throughput test.

This test tracks the load on the Mongo database server and reports what type of operations are contributing to the workload of the server. The test additionally reports the number of clients performing read and write operations on the server, so that you can figure out the count of clients that are generating the load on the MongoDB server. Capacity planning and clustering decisions can be taken based on insights provided by this test.

Target of the test : A MongoDB server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the Mongo database server being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port number at which the specified host listens.
Database Name	The test connects to a specific Mongo database to run API commands and pull metrics of interest. Specify the name of this database here. The default value of this parameter is admin.
Username and Password	The eG agent has to be configured with the credentials of a user who has the required privileges to monitor the target MongoDB instance, if the MongoDB instance is access control enabled. To know how to create such a user, refer to How to monitor access control enabled MongoDB database?. If the target MongoDB instance is not access control enabled, then, specify none against the Username and Password parameters.
Confirm Password	Confirm the password by retyping it here.
Authentication Mechanism	Typically, the MongoDB supports multiple authentication mechanisms that users can use to verify their identity. In environments where multiple authentication mechanisms are used, this test enables the users to select the authentication mechanism of their interest using this list box. By default, this is set to None. However, you can modify this settings as per the requirement.
SSL	By default, the SSL flag is set to No, indicating that the target MongoDB server is not SSL-enabled by default. To enable the test to connect to an SSL-enabled MongoDB server, set the SSL flag to Yes.
CA File	A certificate authority (CA) file contains root and intermediate certificates that are electronically signed to affirm that a public key belongs to the owner named in the certificate. If you are looking to monitor the certificates contained within a CA file, then provide the full path to this file in the CA File text box. For example, the location of this file may be: C:\cert\rootCA.pem. If you do not want to monitor the certificates in a CA file, set this parameter to none.
Certificate Key File	A Certificate Key File specifies the path on the server where your private key is stored. If you are looking to monitor the Certificate Key File, then provide the full path to this file in the Certificate Key File text box. For example, the location of this file may be: C:\cert\mongodb.pem. If you do not want to monitor the certificates in a CA file, set this parameter to none.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Insert operations	Indicates the rate at which insert operations are performed on the target server.	Inserts/Sec
Query operations	Indicates the rate at which query operations are performed on the target server.	Queries/Sec
Update operations	Indicates the rate at which update operations are performed on the target server.	Updates/Sec
Delete operations	Indicates the rate at which delete operations are performed on the target server.	Deletes/Sec
Get more operations	Indicates the rate at which get more operations are performed on the target server.	Getmores/Sec
Command operations	Indicates the rate at which command operations are performed on the target server.	Commands/Sec
Read requests	Indicates the rate at which read requests are received by the target server.	Requests/Sec	A consistent increase in the value of these measures could indicate a potential overload.
Write requests	Indicates the rate at which write requests are received by the target server.	Requests/Sec
Read operation queued clients	Indicates the number of the active client connections performing read operations.	Number	The value of these measures indicate how many clients are generating the load on the MongoDB server.
Write operation queued clients	Indicates the number of the active client connections performing write operations.	Number