Mongo Network Traffic Test

The workload of a MongoDB server is best revealed by the count of requests to it. The impact of this workload on the network throughput of a Mongo server must be assessed to understand whether/not enough network resources are available to handle the current and future workload. This is exactly what the Mongo Network Traffic test does! This test monitors the requests to a Mongo database server and reports the rate at which data is received and transmitted over the network by that server. In the process, the test indicates whether the server is rightly sized in terms of network resources or not.

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 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
Requests	Indicates the rate at which requests are processed by this server.	Requests/Sec
Data transmitted	Indicates the rate at which data is transmitted by the server.	MB/Sec	A high value is indicative of high bandwidth usage by the Mongo DB server.
Data received	Indicates the rate at which data is received by the server.	MB/Sec
DNS resolution operations	Indicates the number of DNS resolution operations which took longer than 1 second during the last measure period.	Number	A high value for this measure is a cause for concern.
SSL handshake operations	Indicates the number of SSL handshake operations which took longer than 1 second during the last measure period.	Number	A high value for this measure is a cause for concern.