Please propose features in the Discussions area as an idea
https://claude.ai/artifacts/125893ab-136f-47c7-a3e1-947a377c7e08
Tooltip text for MongoDB(would be great if someone could go over these to make sure they're 100% accurate):
Capture Details:
- Connector Search: "The type of database or system you're connecting to. This determines which settings and options are available."
- Name: "A unique identifier for this connector. Use the format: prefix_descriptive_name (e.g., marketing_mongo, sales_db). The prefix helps organize connectors by team or project."
- Data Plane: "The cloud provider and region where your data will be processed. Data storage location depends on your configuration, and you can connect your own cloud storage."
Endpoint Configuration:
-
Address: "Your MongoDB connection string without username and password. Examples: mongodb://my-mongo.test?authSource=admin or mongodb+srv://cluster.mongodb.net.
-
User: "Username for database authentication. This user needs read permissions on the collections you want to capture and access to the oplog/change streams."
-
Password: "Password for the database user. This will be encrypted and stored securely."
-
- Database: "Specific databases to discover (optional). Use comma-separated values for multiple databases (e.g., 'production, analytics, staging'). Leave empty to discover all available databases."
-
Capture Batch Collections in Addition to Change Stream Collections: "Include collections that don't support real-time change streams, such as views and time-series collections. These will be captured using periodic polling instead of change streams. If your MongoDB version doesn't support change streams, all collections will automatically use batch mode regardless of this setting."
-
Default Batch Collection Polling Schedule: "Schedule for polling batch collections. Use either:
Frequency: '5m' (every 5 minutes), '2h' (every 2 hours), '24h' (daily)
Specific time: 'daily at 12:34Z' (runs at 12:34 UTC every day)
Default: 24h if not specified"
Advanced Options:
-
Max Await Time: "Maximum time to wait for new database changes before returning an empty result. Use Go duration format: '10s' (10 seconds), '500ms' (500 milliseconds), '1m' (1 minute). Default: 1 second. Lower values mean faster empty responses but more frequent polling."
-
Disable Pre-Images: "Don't capture the document's state before changes, even if your MongoDB deployment supports it. Pre-images show what data looked like before an update or delete operation. Disable this to reduce storage and improve performance if you don't need the before state."
-
Change Stream Exclusive Collection Filter: "Only capture changes from collections you've specifically configured in your bindings. This adds a MongoDB pipeline filter to optimize performance when monitoring a small subset of your collections. Note: Cannot be used together with 'Exclude Collections'."
-
Exclude Collections: "Skip specific collections when capturing changes. Format each as 'database_name:collection_name' and separate multiple entries with commas (e.g., 'prod_db:logs, prod_db:temp, analytics:sessions'). Useful for excluding high-volume or irrelevant collections. Note: Cannot be used together with 'Change Stream Exclusive Collection Filter'."
Network Tunnel - SSH Forwarding
- SSH Endpoint: "The SSH server endpoint that supports tunneling. Use the format: ssh://user@hostname[:port]. The SSH server acts as a secure gateway to access your database. Example: ssh://tunneluser@bastion.example.com:22"
- SSH Private Key: "The private SSH key used to authenticate with the SSH server. This should be the key pair associated with the user specified in the SSH endpoint. The key will be stored encrypted. You can also upload a key file using the button."
Please propose features in the Discussions area as an
ideahttps://claude.ai/artifacts/125893ab-136f-47c7-a3e1-947a377c7e08
Tooltip text for MongoDB(would be great if someone could go over these to make sure they're 100% accurate):
Capture Details:
Endpoint Configuration:
Address: "Your MongoDB connection string without username and password. Examples: mongodb://my-mongo.test?authSource=admin or mongodb+srv://cluster.mongodb.net.
User: "Username for database authentication. This user needs read permissions on the collections you want to capture and access to the oplog/change streams."
Password: "Password for the database user. This will be encrypted and stored securely."
- Database: "Specific databases to discover (optional). Use comma-separated values for multiple databases (e.g., 'production, analytics, staging'). Leave empty to discover all available databases."
Capture Batch Collections in Addition to Change Stream Collections: "Include collections that don't support real-time change streams, such as views and time-series collections. These will be captured using periodic polling instead of change streams. If your MongoDB version doesn't support change streams, all collections will automatically use batch mode regardless of this setting."
Default Batch Collection Polling Schedule: "Schedule for polling batch collections. Use either:
Frequency: '5m' (every 5 minutes), '2h' (every 2 hours), '24h' (daily)
Specific time: 'daily at 12:34Z' (runs at 12:34 UTC every day)
Default: 24h if not specified"
Advanced Options:
Max Await Time: "Maximum time to wait for new database changes before returning an empty result. Use Go duration format: '10s' (10 seconds), '500ms' (500 milliseconds), '1m' (1 minute). Default: 1 second. Lower values mean faster empty responses but more frequent polling."
Disable Pre-Images: "Don't capture the document's state before changes, even if your MongoDB deployment supports it. Pre-images show what data looked like before an update or delete operation. Disable this to reduce storage and improve performance if you don't need the before state."
Change Stream Exclusive Collection Filter: "Only capture changes from collections you've specifically configured in your bindings. This adds a MongoDB pipeline filter to optimize performance when monitoring a small subset of your collections. Note: Cannot be used together with 'Exclude Collections'."
Exclude Collections: "Skip specific collections when capturing changes. Format each as 'database_name:collection_name' and separate multiple entries with commas (e.g., 'prod_db:logs, prod_db:temp, analytics:sessions'). Useful for excluding high-volume or irrelevant collections. Note: Cannot be used together with 'Change Stream Exclusive Collection Filter'."
Network Tunnel - SSH Forwarding