What this category of data looks like
This category of data originates from enterprise CMDB systems, cloud resource auto-discovery tools, hardware procurement ledgers, and ITSM change records. Core delivery formats include configuration item lists, service dependency topology diagrams, change operation logs, and asset inventory tables. Fields include configuration item unique identifiers, affiliated business domains, associated components, update times, and responsible persons. Data updates run on a daily or weekly basis, with a single update covering newly added, decommissioned, or changed assets and dependency relationships.
Constraints imposed by these characteristics on the deployment and upgrade phase
This category of data has scattered sources and requires regular synchronization. Configure connection parameters for multiple data sources during deployment to ensure network connectivity with systems such as CMDB and cloud resource lists. Data update frequencies vary between daily and weekly, so set the trigger interval for scheduled synchronization tasks during deployment to adapt to update rhythms of different businesses. Preload basic topology data during deployment for the configuration item dependency relationship verification logic to avoid dependency verification failures after startup. Additionally, as data volume grows with asset scale, adjust database connection pool parameters properly to ensure stability of queries and synchronization. FastGPT v4.17.0 and later versions require configuration of AI Proxy-related environment variables as a basic system dependency.
How to configure these settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://mongo:27017/fastgpt_cmdb | Database connection address for storing CMDB configuration items, topology relationships, and change records. A dedicated database name must be specified to isolate business data |
REDIS_URL | redis://redis:6379/0 | Caches frequently queried configuration item information and synchronization task status to reduce database query pressure |
DB_MAX_LINK | 20–30 | Adapts to concurrent queries and batch synchronization requirements of CMDB data, avoiding excessive database load caused by too many connections |
FE_DOMAIN | http://internal-fastgpt:3001 | Configures the access domain name for the internal operation and maintenance frontend, used for pushing configuration change tickets and page redirection |
ROOT_KEY | Custom complex random string | Serves as the root key for internal system authentication to ensure the security of configuration synchronization and ticket interfaces |
STORAGE_S3_ENDPOINT | http://internal-minio:9000 | Object storage address for storing CMDB change logs and asset snapshots, suitable for internal private storage deployment scenarios |
Three common configuration mistakes
- A missing required parameter error occurs when starting the App/Admin service. Troubleshooting steps: Check if
AIPROXY_API_ENDPOINT(root address of the AI Proxy service) and a non-emptyAIPROXY_API_TOKEN(AI Proxy administrator token, consistent with the AI Proxy server configuration and cannot be empty) are configured in the server environment variables. - Embedding model calls fail, and the number of retrieval results is 0. Troubleshooting steps: Check if
AIPROXY_API_ENDPOINT(root address of the AI Proxy service) is configured as the root address of the AI Proxy service, and must not be configured as a single model address such as VLLM/Ollama/Xinference. - A database connection exhaustion error occurs when synchronizing CMDB configuration items in batches. The cause is that the value of
DB_MAX_LINKis too low, failing to adapt to the concurrent requirements of batch data processing.
How to verify successful configuration
- Run the startup verification process for the App/Admin service, confirm that the configuration of
AIPROXY_API_ENDPOINT(root address of the AI Proxy service) andAIPROXY_API_TOKEN(AI Proxy administrator token, consistent with the AI Proxy server configuration and cannot be empty) passes verification. - Initiate a manual synchronization task for CMDB configuration items, check that there are no errors related to database connections or data source connectivity in the task logs.
- Access the internal operation and maintenance frontend domain name, confirm that the configuration item list and service dependency topology diagram load normally.
- Call the configuration change ticket interface, confirm that relevant operation and maintenance tickets can be generated and pushed normally.
The values given 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.