What the data for this category looks like
Dairy processing production ledgers cover documents including raw milk acceptance records, standardized ingredient lists, pasteurization or UHT sterilization records, CIP cleaning records, filling records, sample retention and microbial test reports. Data sources include milk source testing equipment, MES systems, homogenization and heat treatment equipment, online temperature and flow collection devices, CIP systems, and LIMS laboratory management systems. Data updates occur in real time per milk tank and per batch. Some online parameters such as temperature and flow are updated every second. Ledger fields include raw milk antibiotic and physicochemical indicators, heat treatment time and temperature, filling batch numbers, cleaning verification results, and more. Units include ℃, m³/h, seconds, batch numbers, and more.
What constraints these characteristics impose during deployment and upgrade
Dispersed multi-source data sources require compatibility with protocols of different devices and systems during deployment. Multiple data source connection parameters must be configured. High-frequency real-time and batch updates require database connection pool parameters adapted to high-concurrency scenarios to avoid data write blocking. Diverse document structures and field rules require flexible field mapping rules to adapt to different types of production ledgers. The production characteristics of perishable liquid raw materials require ledger data timeliness. Deployment must control data synchronization delay within a reasonable range. Severe error consequences require strict data verification rules to prevent erroneous data from flowing into subsequent production links.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 | Multiple structured data entries are generated per milk tank and per batch. Sufficient connections are required to support real-time synchronization and batch import in high-concurrency scenarios |
MONGODB_URI | mongodb://username:password@server IP:27017/dairy_prod?authSource=admin | Stores unstructured documents such as raw milk acceptance records and sample retention microbial test reports. Create collections by batch to facilitate classified retrieval |
PG_URL | postgresql://username:password@server IP:5432/dairy_prod | Stores structured ledger data that supports associated queries, including filling records, heat treatment parameters, ingredient lists, and more |
REDIS_URL | redis://default:password@server IP:6379/1 | Caches real-time updated online temperature and flow data, CIP status data, and reduces database query pressure |
STORAGE_S3_ENDPOINT | http://enterprise storage node IP:9000 | Stores large-volume documents such as microbial test reports and cleaning records, adapts to the enterprise's existing object storage architecture |
FILE_TOKEN_KEY | Set via actual measurement | Used to encrypt access tokens for ledger files, prevent unauthorized downloads. Key length must be no less than 32 bits |
Three common mistakes
- Symptom: The code execution node returns
500 Internal Server Errorafter running. Logs show external service connection failure. Cause:AIPROXY_API_ENDPOINTandAIPROXY_API_TOKENare not configured correctly, making it impossible to call the AI service required for generating ledger reports. - Symptom: When configuring MCP nodes in FastGPT v4.8, the interface fails to recognize relevant parameters. Cause: The v4.8 version does not have a built-in MCP adaptation module. Upgrade to v4.17.0 or later.
- Symptom: When batch importing raw milk acceptance records, some fields are empty and the import task is marked as failed. Logs show file parsing failure. Cause:
FILE_TOKEN_KEYis not configured correctly, making it impossible to normally parse field content from encrypted documents.
How to confirm the configuration is complete
- Run a batch import test for sample documents, verify that ledger fields in the background are consistent with the original documents, with no missing or incorrectly mapped fields.
- Trigger a real-time data synchronization task, confirm that the database updates the latest production data within a reasonable time frame.
- Access the ledger report page corresponding to the configured
FE_DOMAIN, verify that encrypted documents can be downloaded and accessed normally. - Check database connection pool monitoring, confirm that the
DB_MAX_LINKconfiguration does not trigger connection exhaustion alerts.
The values provided are common starting points and should be measured against the reader's own samples.