Skip to main content
Compatible with Fusion version: 4.0.0 through 5.12.0
The MongoDB V1 connector works with MongoDB Atlas, MongoDB Community, or MongoDB Enterprise to crawl documents such as customer records, IoT logs, or session data from one or more collections, transforming any BSON documents into JSON for indexing. Cursor-based batching can be enabled for parallel processing to improve performance. The connector can also use MongoDB queries such as {"status": "active"} as filters to limit what data is ingested. You can combine MongoDB content with other sources like Confluence, Salesforce, or MySQL to unify search with Fusion.
ImportantV1 deprecation and removal noticeStarting in Fusion 5.12.0, all V1 connectors are deprecated. This means they are no longer being actively developed and will be removed in Fusion 5.13.0.The replacement for this connector is in active development at this time and will be released at a future date.If you are using this connector, you must migrate to the replacement connector or a supported alternative before upgrading to Fusion 5.13.0. We recommend migrating to the replacement connector as soon as possible to avoid any disruption to your workflows.
Connector flow On first connection, the MongoDB V1 connector performs a full crawl and saves a checkpoint. If Process oplog is not selected, when you restart the data source the connector performs a full recrawl. In this mode the connector does not support incremental recrawling, nor does it delete entries that are deleted from MongoDB.

​
Prerequisites

Perform these prerequisites to ensure the connector can reliably access, crawl, and index your data. Proper setup helps avoid configuration or permission errors, so use the following guidelines to keep your content available for discovery and search in Fusion. The user account must have read permissions for the database and collection and you need a MongoDB cluster or server instance with a valid MongoDB URI so Fusion can connect over the network. Before using the connector, test the connectivity for your database:
  • For Atlas use one of the following:
    • mongodb+srv:// USERNAME:PASSWORD@CLUSTER.mongodb.net
    • mongo "mongodb+srv://CLUSTER_NAME.mongodb.net/DATABASE_NAME" --username USERNAME --password PASSWORD
  • If exposing through a service or proxy, use mongo "mongodb://USERNAME:PASSWORD@HOST:PORT".
If using incremental crawling, ensure the following:
  • Your documents must include a timestamp or version field such as lastModified, updatedAt, or modifiedDate.
    • The format of the field should be ISO 8601 strings or BSON Date objects.
    • The field must be a top-level field or accessible through dot notation.

​
Authentication

Setting up the correct authentication according to your organization’s data governance policies helps keep sensitive data secure while allowing authorized indexing. The connector uses the MongoDB URI with embedded credentials or specified properties. The basic requirements are listed here with additional guidance in the instructions below. Atlas:
  • Create a user account in Database Access in the Atlas dashboard with role-based access such as read or readWrite.
  • Use a username and password plus SRV.
  • Ensure IP Whitelisting is configured to allow Fusion’s IP.
On-prem:
  • Use a username and password with role-based access such as read or readWrite.
TLS/SSL:
  • If secured connection certificates are required in your MongoDB deployment enable with the URI option ssl=true.

​
Create a MongoDB user account for Fusion

For MongoDB Atlas:
  1. Go to MongoDB and navigate to Database Access in your project.
  2. Click Add New Database User and set:
    1. Username and password.
    2. Database privileges for read or readWrite on your target database.
  3. Add Fusion’s IP under Network Access > IP Whitelist.
  4. Note the MongoDB URI under Connect > Drivers.
For self-hosted MongoDB, use mongo shell or your admin tool: 
use admin
db.createUser({
  user: "FUSION_USERNAME",
  pwd: "FUSION_PASSWORD",
  roles: [{ role: "read", db: "DATABASE" }]
})

​
Prepare the MongoDB URI with authentication credentials

If your password includes special characters, URL-encode the password:
  • Atlas (SRV URI): mongodb+srv://FUSION_USERNAME:FUSION@CLUSTER.mongodb.net/DATABASE_NAME
  • Self-hosted: mongodb://FUSION_USERNAME:FUSION@localhost:27017/DATABASE_NAME
If using TLS/SSL with replica set options, you can append the options to the URI for security and cluster support:
  • mongodb://USERNAME:PASSWORD@HOST:27017/?authSource=admin&ssl=true
For SRV use mongodb+srv://USERNAME:PASSWORD@CLUSTER.mongodb.net/?retryWrites=true&w=majority. To verify access with your credentials, use mongo CLI or a database GUI:
  • mongo "mongodb+srv://USERNAME:FUSION@CLUSTER.mongodb.net/DATABASE_NAME"

​
Common authentication issues

  • authentication failed: The wrong username, password, and/or role was used, so verify the credentials are accurate.
  • IP not allowed in Atlas: The IP is not whitelisted. Add the Fusion server IP.
  • TLS required: MongoDB is enforcing SSL, requiring ssl=true with the URI.
  • authSource missing: The specified authentication database was not specified. Add authSource=admin to the URI.

​
Learn more

Retrieve data from a MongoDB instance.You can configure the Fusion MongoDB connector to read from the MongoDB oplog rather than from the entire MongoDB collection. In this mode, the connector crawls the full MongoDB collection, saves a checkpoint in ZooKeeper, then continues running indefinitely, grabbing updates from the oplog as they happen in real time. This way, the connector can delete documents that are deleted from MongoDB.If the connector stops for any reason, it stores a timestamp in ZooKeeper that shows what the latest update was. When the connector restarts, it continues reading from that checkpoint onward.
  1. Make sure your connector authenticates to Mongo as a user with read oplog permissions. See Role-based access control in the MongoDB documentation.
  2. Make sure Process Oplog is selected in the Fusion MongoDB connector UI.

​
Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.
⌘I