Agents Administration - Tests
 

Default Parameters for MongoCallsTest

This test monitors queries/calls to the tables in MongoDB, and rapidly alerts administrators to failed table operations. Additionally, the test also points to the type of table operations that experienced maximum failures - is it create table? alter table? drop table? rename table? compact table? salvage table? truncate table? or verify table?

This page depicts the default parameters that need to be configured for the MongoCallsTest test.

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, specify the host for which the test is to be configured.

  • The test connects to a specific Mongo database to run API commands and pull metrics of interest. Specify the name of this database in the DATABASE NAME text box. The default value of this parameter is admin.

  • 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 and confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • 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.

  • 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.

  • 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.

  • 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.

  • Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.