From 89dab093765bb343ff53a4ae8b4af6ddf8cf9d6a Mon Sep 17 00:00:00 2001
From: Rounak Dhillon <162090200+RounakDhillon@users.noreply.github.com>
Date: Thu, 17 Apr 2025 14:04:11 +0530
Subject: [PATCH] Docs: Mongodb integration Addition (#20873)

Co-authored-by: Rounak Dhillon <rounakdhillon@Rounaks-MacBook-Air.local>
---
 .../database/mongodb/troubleshooting.md       | 42 +++++++++++++++++++
 .../database/mongodb/troubleshooting.md       | 42 +++++++++++++++++++
 2 files changed, 84 insertions(+)

diff --git a/openmetadata-docs/content/v1.6.x/connectors/database/mongodb/troubleshooting.md b/openmetadata-docs/content/v1.6.x/connectors/database/mongodb/troubleshooting.md
index 9a5d7147426..c5ea5c3015f 100644
--- a/openmetadata-docs/content/v1.6.x/connectors/database/mongodb/troubleshooting.md
+++ b/openmetadata-docs/content/v1.6.x/connectors/database/mongodb/troubleshooting.md
@@ -4,3 +4,45 @@ slug: /connectors/database/mongodb/troubleshooting
 ---
 
 {% partial file="/v1.6/connectors/troubleshooting.md" /%}
+
+## Resolving MongoDB Ingestion Failures
+
+When attempting to connect OpenMetadata to MongoDB, particularly cloud-hosted or replica set deployments, you might encounter timeout errors or connection failures. Follow the steps below to identify and resolve these issues.
+
+## 1. Verify Connection Scheme
+
+### Cloud MongoDB (MongoDB Atlas)
+Use the connection scheme `mongodb+srv` in the **Advanced Config > Connection Scheme** field.  
+Do **not** include the port in the host field.
+
+**Example:**
+
+```yaml
+hostPort: ahamove.mongodb.net
+connectionScheme: mongodb+srv
+```
+## 2. Enable SSL for Encrypted Connections
+
+If your connection string includes `ssl=true`, you must explicitly set SSL in the Connection Options.
+
+```yaml
+connectionOptions:
+  ssl: true
+```
+
+This is mandatory when connecting to clusters that enforce SSL/TLS encryption.
+
+## 3. Inspect Debug Logs
+
+Enable and review debug logs for more detailed error messages:
+
+- Navigate to the ingestion workflow in the OpenMetadata UI
+- Enable **Debug Log** in the configuration settings
+- Check logs using the Docker CLI:
+
+```bash
+docker logs <openmetadata-ingestion-container>
+```
+4. Check Docker Networking
+
+Ensure that the OpenMetadata container is on the same network as the ingestion container, especially when running locally via Docker Compose.
diff --git a/openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/mongodb/troubleshooting.md b/openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/mongodb/troubleshooting.md
index 6316c517df9..171483b1774 100644
--- a/openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/mongodb/troubleshooting.md
+++ b/openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/mongodb/troubleshooting.md
@@ -4,3 +4,45 @@ slug: /connectors/database/mongodb/troubleshooting
 ---
 
 {% partial file="/v1.7/connectors/troubleshooting.md" /%}
+
+## Resolving MongoDB Ingestion Failures
+
+When attempting to connect OpenMetadata to MongoDB, particularly cloud-hosted or replica set deployments, you might encounter timeout errors or connection failures. Follow the steps below to identify and resolve these issues.
+
+## 1. Verify Connection Scheme
+
+### Cloud MongoDB (MongoDB Atlas)
+Use the connection scheme `mongodb+srv` in the **Advanced Config > Connection Scheme** field.  
+Do **not** include the port in the host field.
+
+**Example:**
+
+```yaml
+hostPort: ahamove.mongodb.net
+connectionScheme: mongodb+srv
+```
+## 2. Enable SSL for Encrypted Connections
+
+If your connection string includes `ssl=true`, you must explicitly set SSL in the Connection Options.
+
+```yaml
+connectionOptions:
+  ssl: true
+```
+
+This is mandatory when connecting to clusters that enforce SSL/TLS encryption.
+
+## 3. Inspect Debug Logs
+
+Enable and review debug logs for more detailed error messages:
+
+- Navigate to the ingestion workflow in the OpenMetadata UI
+- Enable **Debug Log** in the configuration settings
+- Check logs using the Docker CLI:
+
+```bash
+docker logs <openmetadata-ingestion-container>
+```
+4. Check Docker Networking
+
+Ensure that the OpenMetadata container is on the same network as the ingestion container, especially when running locally via Docker Compose.