What this category of data looks like
Data for this category comes from manufacturing enterprise MES systems, online inspection equipment, laboratory systems, process parameter libraries, customer standards, and historical defect libraries. Daily associated documents include control plans, patrol inspection records, SPC reports, final product inspection reports, nonconforming product review forms, release forms, and quality monthly reports. Data is updated per production batch or shift, or collected continuously by inspection equipment. It includes fields such as process parameters, inspection results, defect types, and release status. There are no unified fixed units; specific units vary based on the inspection item and document type.
What constraints these characteristics impose on the deployment and upgrade phase
This category of data has scattered sources and high update frequencies. During deployment, storage configurations must be adapted to support multi-system integration, to ensure stable concurrent read and write operations. Diverse document structures require the system to support multi-format data parsing, and corresponding storage paths must be configured to manage files such as inspection reports. Permission control related to production release requires clear system permission configuration logic. For scenarios of batch data import and continuous collection, database connection parameters must match high-concurrency requirements to avoid data synchronization delays or nonconforming product release review timeouts due to insufficient resources.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 20–50 | Adapts to the connection pool logic of FastGPT v4.17.0, supports concurrent requirements for batch data import and continuous collection per production batch, and prevents connection pool exhaustion |
MONGODB_URI | mongodb://[username]:[password]@[host]:[port]/fastgpt?authSource=admin | Stores unstructured quality data such as historical defect libraries and SPC reports, supports flexible multi-condition queries |
PG_URL | postgresql://[username]:[password]@[host]:[port]/fastgpt | Stores structured business data such as control plans and patrol inspection records, ensures stability of transactional operations |
STORAGE_S3_ENDPOINT | Fill in according to the enterprise's self-built object storage address | Manages uploaded files such as final product inspection reports and nonconforming product review forms, adapts to storage requirements for multiple scenarios |
ROOT_KEY | Randomly generated string of 32 characters or more | Controls the system's highest permissions, only used for background configuration by quality management personnel, ensures the security of release review permissions |
REDIS_URL | redis://[password]@[host]:[port]/0 | Caches frequently queried process standards and customer requirements, reduces query load on the database |
Three common mistakes
- Symptom: System response delay exceeds 600 seconds when batch importing patrol inspection records, and a timeout error is displayed on the interface. Cause: The
DB_MAX_LINKparameter was not adjusted, and the database connection pool is insufficient to support concurrent read and write operations for batch data. - Symptom: The system reports an error after uploading a final product inspection report, prompting that file storage failed. Cause:
STORAGE_S3_ENDPOINTwas not configured correctly, or the object storage address or permission settings are incorrect, resulting in failure to write files. - Symptom: Empty results are returned when querying quality standards via Q&A. Cause:
REDIS_URLwas not configured or the parameter is incorrect, frequently queried process standards are not cached, and database query timeout prevents results from being returned.
How to confirm that configurations are correctly set
- Perform a batch import test of sample data, check database connection logs, and confirm that the number of connections does not exceed the configured
DB_MAX_LINKlimit. - Upload a final product inspection report, check the object storage console to confirm that the corresponding file is generated, and verify that the
STORAGE_S3_ENDPOINTconfiguration takes effect. - Initiate a test request for frequently queried process standards, check cache monitoring metrics, and confirm that the cache service configured via
REDIS_URLresponds normally. - Log in to the system background, use
ROOT_KEYto verify that the highest permission configuration is only open to designated quality management personnel.
The values provided are common starting points and should be evaluated against the user's own samples.