What Data for This Category Looks Like
The data for this category comes from design documents, standard instruments, environmental monitoring data, calibration software, laboratory information systems, and customer range requirements. Daily generated documents include assembly and commissioning sheets, calibration procedures, original calibration records, error curves, metrology certificates, and software version logs. Data updates trigger each time a device undergoes calibration. Each individual data entry includes fields such as range, error calculation value, calibration date, standard instrument number, and traceability chain number. Units include specialized metrology units such as Pa, ℃, mL/min, and others. Some documents are structured files with visualizable curves.
What Constraints These Characteristics Impose on Deployment and Upgrade Workflows
Since data updates per device per calibration, support for incremental import and batch historical data migration is required. Field consistency across calibration records from different batches must be maintained. Data includes large files such as error curves and metrology certificates. Storage configurations must support large file upload and read operations. Calibration records are critical traceable deliverables. Fine-grained access and modification controls must be implemented for documents across different permission roles. In scenarios where multiple laboratories perform calibrations simultaneously, support for high concurrent retrieval and database connection requests is needed. This prevents workflow freezes caused by insufficient resources.
How to Configure the Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 | Adapts to concurrent connection needs for cross-review of calibration documents from multiple devices. Prevents database connection pool exhaustion. |
STORAGE_S3_ENDPOINT | Fill in the actual access address of the internal object storage | Used to store large documents such as calibration records, error curves, and metrology certificates. Ensures stable large file upload and reading. |
REDIS_URL | Address of a dedicated Redis instance with access password | Caches metadata of calibration documents and vector retrieval results. Improves response speed during batch reviews. |
FILE_TOKEN_KEY | 32-bit randomly generated string | Protects download permissions for calibration documents. Prevents unauthorized access to sensitive deliverables such as metrology certificates. |
FE_DOMAIN | Frontend access domain name of the deployment environment | Uniformly configures the access entry for the knowledge base management interface. Ensures correct paths for document import and indexing operations. |
Three Common Configuration Mistakes
- Symptom: Chinese garbled characters appear after importing CSV-format original calibration records. Cause: The GBK or UTF-8 encoding format of the file was not specified. Or the system encoding during import does not match the file encoding.
- Symptom: After upgrading FastGPT v4.10, calibration records in the original knowledge base cannot be retrieved. Cause: The vector index format was updated in the new version. The index of the original knowledge base was not regenerated, or database index data was not migrated.
- Symptom: Database timeout errors occur during batch import of historical calibration records. Cause: The
DB_MAX_LINKconfiguration value is too low. It cannot support concurrent database requests during batch import.
How to Confirm Configurations Are Set Correctly
- Upload a CSV test file containing Chinese calibration information. Check that Chinese content displays normally after import. No garbled characters or missing characters are present.
- Perform a batch import operation for historical calibration records. Wait for indexing to complete. Retrieve records for a specified calibration date. Confirm that retrieval results match the imported data.
- Check the database connection pool status. Confirm that concurrent connection counts do not reach the upper limit set by the
DB_MAX_LINKconfiguration. - Access the frontend address configured in
FE_DOMAIN. Enter the knowledge base management interface. Check that large file upload and index generation functions operate normally.
The configuration values listed here are common starting points. They should be evaluated against the reader's own specific samples and use cases.
This configuration applies to FastGPT v4.17.0.