What the data for this category looks like
Data for this category primarily comes from CRM systems, contract order databases, identity management systems, and product backends. Daily generated documents include onboarding application forms, tenant configuration sheets, administrator account lists, and delivery confirmation slips. Data updates occur per order or daily. Core fields include tenant unique identifier, customer association information, basic permission configurations, account status, and onboarding timestamp. No additional statistical quantitative indicators are included.
What constraints these characteristics impose on the database and operations link
Multi-source data access requires databases to support cross-system synchronization configurations, to avoid data inconsistency. The per-order or daily update rhythm requires reasonable configuration of database connection pool parameters to prevent connection exhaustion. Uniqueness checks for core fields require databases to create unique indexes for tenant ID and customer identifier fields, to avoid duplicate initialization. This link directly relates to customer login and delivery progress, so databases require high availability redundancy configurations to ensure stable metadata read and write operations.
How to set the configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
MONGODB_URI | Full connection string containing authentication information and exclusive database name | Stores core metadata such as tenant accounts and permission configurations, complies with FastGPT v4.17.0 storage specifications |
PG_URL | Structured data connection address with read-only permission sub-account | Stores form data such as onboarding application forms and delivery confirmation slips, separates read and write permissions to enhance security |
DB_MAX_LINK | 50-100 connections | Matches per-order or daily update rhythm, prevents database connection exhaustion in high-concurrency scenarios |
REDIS_URL | Dedicated cache connection address with access password, set connection timeout to 30 seconds | Caches tenant sessions and temporary configurations, reduces response latency for high-frequency queries |
| Database unique index | Create indexes for tenant ID and customer identifier fields | Ensures efficiency of data uniqueness checks, avoids duplicate initialization records |
| Database idle timeout | 300 seconds | Reduces invalid connection occupancy, optimizes database resource utilization |
| Session cache expiration time | 1800 seconds | Matches the lifecycle of tenant sessions, avoids resource occupation by invalid cache |
Three common mistakes
- Phenomenon: The console returns the
text index required for $text queryerror, and knowledge base initialization fails. Cause: No full-text index was created in the corresponding PostgreSQL table, preventing normal execution of configuration retrieval. - Phenomenon: MongoDB connection fails, and the interface prompts authentication error or connection timeout. Cause: The
MONGODB_URIconfiguration does not include correct database authentication information or target database name, orDB_MAX_LINKis set too small leading to connection exhaustion. - Phenomenon: Existing tenant data cannot be read normally after upgrading the system version. Cause: No database metadata backup was performed before the upgrade, or the configuration points to an incorrect database instance.
How to confirm configurations are properly set
- In the FastGPT v4.17.0 system backend, enter the tenant configuration module, perform a database connection test, and verify that the
MONGODB_URIandPG_URLconfigurations can establish normal connections. - Log in to the target database, check the index list, and confirm that unique indexes have been created for the tenant ID and customer identifier fields.
- Submit a test onboarding application form, verify that data can be normally written to the corresponding database table and cross-system synchronization is completed.
- Enter the Redis cache management page, confirm that the
REDIS_URLconfiguration can normally read and write cache data, and the session cache expiration time meets preset requirements.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.