What This Category of Data Looks Like
This category of data primarily comes from pressure testing platforms, APM monitoring, database slow logs, and production traffic baselines. The update frequency is monthly or when major versions are released. Daily produced documents include pressure testing plans, capacity assessment reports, pressure testing data records, and optimization suggestion sheets. Fields cover throughput rate, latency, resource usage rate, traffic baseline peak value, with corresponding units of transactions per second, milliseconds, percentage, and Mbps. Data volume grows as the pressure testing scale expands, requiring support for large file storage and batch query operations.
Constraints Imposed on Deployment and Upgrades
This category of data requires storage of large-volume pressure test reports and batch query historical records. Configure sufficient storage and database connection resources during deployment. This avoids insufficient storage or query timeouts after upgrades. Offline scenarios require adaptation to environments without public network access. Do not rely on external object storage services. Version upgrades must maintain compatibility with legacy pressure test data formats. This prevents historical documents and reports from failing to load normally. Internal ticket Q&A requires connection to dedicated model services. During deployment, ensure intranet connectivity between the model service and the FastGPT instance. This prevents cross-environment call failures.
How to Set Configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–200 | Supports concurrent query demands for batch pressure testing data and internal ticket access |
MONGODB_URI | Intranet offline deployment MongoDB connection address | Stores large-volume documents such as pressure testing plans and capacity assessment reports |
REDIS_URL | Local Redis instance address using port 6379 | Caches real-time pressure testing metrics and internal ticket session data to reduce database query pressure |
STORAGE_S3_ENDPOINT | Intranet MinIO deployment address | Stores large-volume pressure testing data and optimization suggestion sheets in offline environments |
FILE_TOKEN_KEY | 32-character random string | Ensures access security for internal ticket attachments and prevents unauthorized downloads |
ROOT_KEY | Random key string generated according to the deployment environment | Restricts access permissions for internal operation and maintenance interfaces, meeting security requirements for on-duty scenarios |
Three Common Mistakes
- Symptom: After upgrading in a network-free environment, historical pressure testing data fails to load, and the interface displays an incorrect storage path. Cause: The
STORAGE_S3_ENDPOINTwas not configured to the local offline storage address during the deployment phase, and a public network object storage address was still used. - Symptom: After upgrading to FastGPT v4.9.0, document parsing tasks in internal tickets fail, returning an "insufficient permissions" error. Cause: The authorization configuration for the document parsing function was not confirmed, and the switch for a commercial version exclusive feature was mistakenly set to forced enable.
- Symptom: When connecting to a deepseek model deployed locally via ollama or using the v2 version of the marker image offline, model call timeouts or report generation failures occur. Cause:
STORAGE_S3_ENDPOINTorREDIS_URLwas not configured correctly, or intranet access ports were not opened.
How to Confirm Configuration Correctness
- Confirm that the currently deployed FastGPT version is v4.17.0, compatible with the latest pressure testing data storage format.
- Run a database connection test to verify that the connection number configured in
DB_MAX_LINKcan support concurrent pressure testing data queries, with no connection timeout errors. - Upload a pressure testing plan document, confirm that it can be stored normally and accessed via the intranet domain name, with no upload failure prompts.
- Check the system logs to confirm that the connection status of
MONGODB_URIandREDIS_URLis normal, with no disconnection or authentication failure errors.
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.