yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-12-03 19:16:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Mongodb integration Addition (#20873)

Browse Source 
Co-authored-by: Rounak Dhillon <rounakdhillon@Rounaks-MacBook-Air.local>
This commit is contained in:
Rounak Dhillon 2025-04-17 14:04:11 +05:30 committed by GitHub
parent 1063e019ba
commit 89dab09376
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 84 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
openmetadata-docs/content/v1.6.x/connectors/database/mongodb/troubleshooting.md
View File

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

42
openmetadata-docs/content/v1.7.x-SNAPSHOT/connectors/database/mongodb/troubleshooting.md
View File

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