This document applies to FastGPT v4.17.0.
What the data for this category looks like
The data for this category primarily comes from design documents, standard instruments and environmental monitoring equipment, calibration software, laboratory information systems, and customer range requirements. Daily processed documents include assembly and commissioning sheets, calibration procedures, original calibration records, error curves, metrology certificates, and software version records. Data is updated per device per calibration. A single calibration record includes fields such as tested part number, calibration date, error value, standard instrument number, environmental parameters, and metrology certificate number. Fields must meet metrological traceability requirements, and there are no bulk unified update scenarios.
Constraints Imposed by These Characteristics During Deployment and Upgrade
Data sources for this category are scattered, requiring integration with heterogeneous data sources such as calibration software and laboratory information systems. During deployment, multiple storage connections must be configured to adapt to the interface formats of different systems. Data updates are per device per calibration, with a small number of documents generated per single operation but frequency fluctuating with production scale. During deployment, concurrency processing parameters must be adjusted to adapt to small-batch, high-frequency write requests. Documents involve metrological traceability, so access permissions must be strictly controlled. During upgrades, the integrity of the original data’s traceability chain must be retained, and fields and storage paths of historical calibration records must not be modified arbitrarily. Large files such as error curves and metrology certificates require separate storage. During deployment, storage parameters adapted to large file transfers must be configured.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 20–30 connections | This category generates multiple documents per calibration. Concurrency connections should not be too high to avoid database blocking, adapting to small-batch, high-frequency write requests |
MONGODB_URI | Determined through actual testing | Requires integration with heterogeneous data sources such as laboratory information systems and calibration software, needing adaptation to connection string formats for different deployment environments |
REDIS_URL | redis://:custom password@deployment address:6379/0 | Required to cache temporary calculation results of calibration records, maintain session state for multi-round reviews, and adapt to small-batch, high-frequency read/write requirements |
STORAGE_S3_ENDPOINT | Determined through actual testing | Required to store large files such as error curves and metrology certificates, adapting to endpoint configurations for local or cloud storage |
FILE_TOKEN_KEY | 32-bit random string | Ensures download permissions for sensitive documents such as calibration certificates, preventing unauthorized access |
ROOT_KEY | Only used during initialization | Documents in this category involve metrological traceability, so super administrator permissions must be strictly controlled to avoid accidental modification of historical data |
Three Common Misconfigurations
- Symptom: Some containers cannot access port 3000 after startup, and logs only show startup initialization information. Cause:
REDIS_URLorMONGODB_URIis not configured correctly, causing the ledger summarization service to fail to connect to the cache and database, and terminate automatically after startup. - Symptom: Calling the application via an interface returns empty results. Cause: Calibration record fields are not mapped to the knowledge base retrieval template, making it impossible to match corresponding documents.
- Symptom: Workflows cannot support multi-round conversations. Cause: A reasonable value for
DB_MAX_LINKis not configured, causing database connections to be exhausted and unable to maintain session context.
How to Verify Correct Configuration
- Access the frontend address corresponding to
FE_DOMAIN, log in, and enter the knowledge base management page to confirm that uploaded documents such as assembly and commissioning sheets and calibration certificates can be previewed normally. - Call the test interface, pass in the tested part number, and confirm that the returned ledger summarization result includes the fields of the corresponding calibration record and the error curve link.
- Check the database connection logs to confirm that the concurrency connection count of
DB_MAX_LINKdoes not exceed the set value, and there are no connection timeout errors. - Restart the service, check the running status of all containers, and confirm that ports 3000 and 3001 can be accessed normally.
The values provided are common starting points and should be measured against the reader's own samples.