This configuration applies to FastGPT v4.17.0.
What this category of data looks like
Data for this category comes from CMDB systems, cloud resource inventories, auto-discovery tools, and procurement ledgers. The update cadence is daily or weekly. Daily produced documents include configuration item lists, service component relationship topologies, change records, and asset inventory tables. Core fields include configuration item unique identifiers, affiliated service chains, dependency relationships, change times, and responsible persons. There are no additional custom statistical units. The data structure is centered around dependency associations of service components, differing from single asset records in general IT asset inventory.
What constraints these characteristics impose on the deployment and upgrade phase
Data for this category is scattered across multiple sources with complex dependency relationships. During the deployment phase, connection parameters for multiple data sources such as CMDB and cloud resource inventories must be configured at the same time. Access permissions and update cadences for each data source must be matched. The dependency relationships of service components must undergo topology verification after deployment. During upgrades, the associated links of original configuration items must be retained to avoid service dependency breaks caused by configuration migration. The traceability requirement for change records requires that configuration change audit logs be enabled during deployment. The incremental synchronization frequency must match the data update cycle to prevent excessive system resource usage from full pulls. Uniqueness verification for configuration items must be completed before deployment to avoid asset account-actual discrepancies caused by duplicate configuration items.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 100–200 connections | Adapts to concurrent query demands of CMDB and cloud resource inventories, prevents connection pool exhaustion |
MONGODB_URI | Fill in the internal network connection address of the self-built MongoDB, include authentication parameters | Stores configuration item topologies and change records, requires internal network access security |
PG_URL | Fill in the connection address of the associated PostgreSQL instance, set connection timeout to 30 seconds | Stores configuration item lists and asset inventory data, timeout setting adapts to multi-source data pull cadence |
REDIS_URL | Fill in the connection address of the local Redis instance, set maximum memory to 1000 MB | Caches frequently queried configuration item data, avoids repeated pulls increasing data source pressure |
FE_DOMAIN | Fill in the external access domain name of the platform | Used to generate jump links for configuration item detail pages, ensures correct internal access paths |
FILE_TOKEN_KEY | Generate a 32-bit random string as the secret key | Encrypts access tokens for configuration item export files, prevents unauthorized access |
STORAGE_S3_ENDPOINT | Fill in the internal network address of the self-built object storage, set access timeout to 15 seconds | Stores attachments and change logs for configuration items, timeout setting adapts to small file uploads and downloads |
Three common mistakes
- Symptom: A 403 permission denied error is returned when calling CMDB or object storage APIs after deployment. Cause: The access key permissions corresponding to
STORAGE_S3_ENDPOINTare not configured, or authentication tokens are not correctly added to connection parameters, resulting in blocked data source access. - Symptom: A large number of null value fields appear in the configuration item list after upgrade. Cause: The original
PG_URLconnection configuration was not retained during the upgrade, and default parameters were used instead, making it impossible to read existing asset inventory data. - Symptom: Configuration item topology relationships are not fully displayed. Cause: A reasonable connection number was not set for
DB_MAX_LINK, resulting in some dependency relationship data not being loaded during concurrent queries.
How to confirm the configuration is complete
- Run multi-data source connectivity tests, check the connection status of configuration items such as
MONGODB_URI,PG_URL, andSTORAGE_S3_ENDPOINT, confirm there are no timeout or permission errors. - Export a sample configuration item list, verify field integrity and dependency relationship display logic, match the daily maintenance document structure.
- Trigger a configuration item incremental synchronization task, check whether change records are generated normally, confirm that the audit log function is enabled correctly.
- Verify the configuration item export function, confirm that tokens generated by
FILE_TOKEN_KEYcan normally access exported files, with no permission blocking issues.
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.