Setting up Generic MongoDB

After you have selected Generic MongoDB as the Source for creating the Pipeline, provide the following connection settings and data replication details in the Configure Your Source page:

  • Pipeline Name: A unique name for the Pipeline.

  • Database Host: IP address or hostname of the database you want to access. If you are trying to connect to a replica set, provide a comma-separated list of all IPs/DNS names in the replica set. For example,,, Hevo always connects to a secondary instance.

    If you have a sharded configuration, provide the MongoDB Router address. Read MongoDB for more information on MongoDB configurations.

    Note: If you do not have this information, reach out to your MongoDB Administrator.

  • Database User: The authenticated user that can read the collections in your database.

    Note: It is recommended that only Read-Only permissions be provided to the user.

  • Database Password: The password for the database user.

  • Database Port: The port on which your MongoDB server is listening for connections (default is 27017).

  • Auth DB Name: The database that stores the user’s information. The user name and password entered in the preceding steps are validated against this database. For example, admin.

    Note: As a good practice, you can keep the information of all your users, including their access privileges, in the admin database, which is created by default in MongoDB.

  • Provide the following Connection Settings:

    • Connect through SSH: Enable this toggle option to connect to Hevo using an SSH tunnel, instead of directly connecting your MongoDB database host to Hevo. This provides an additional level of security to your MongoDB database by not exposing your MongoDB setup to the public. Read Connecting Through SSH.

      If this option is disabled, you must whitelist Hevo’s IP addresses, as listed here, in the MongoDB settings to allow Hevo to connect to your MongoDB host. Read about Whitelisting IP Addresses in MongoDB.

    • Use SSL: Enable this toggle option if you have enabled SSL at the MongoDB server end.

  • Provide the following Advance Settings:

    • Load All Databases: If enabled, Hevo fetches data from all your databases on the selected host. If disabled, provide the Database Name to fetch data from.

      Note: You can separate multiple database names with a comma.

    • Merge Collections: If enabled, collections with the same name across different databases are merged into a single Destination table. If disabled, separate tables are created, prefixed with the respective database name. See Example - Merge Collections Feature.

    • Load Historical Data: If disabled, Hevo loads only the data that was written in your database after the time of creation of the Pipeline. If enabled, the entire table data is fetched during the first run of the Pipeline.

Last updated on 25 Aug 2020