What data for this category includes
Data originates from customer ITSM systems, operations and maintenance monitoring platforms, hardware asset inventories, and on-duty shift records. Daily generated documents include on-site daily reports, service desk tickets, inspection reports, and SLA monthly reports. Data fields cover ticket numbers, processing durations, inspection item statuses, and personnel on-duty information. Data update frequencies are divided into daily and monthly. Daily data includes that day’s tickets and inspection records. Monthly data covers SLA statistics and asset inventory reports. The data structure includes structured ticket fields and unstructured inspection logs. It supports unified storage and associated queries for multi-source data, to meet daily retrospective needs of on-site services.
Constraints imposed on database and operations workflows
Scattered, diverse data sources require databases to support multi-source data access and mapping. They must adapt to mixed storage of structured tickets and unstructured inspection logs. Differing update frequencies require configured incremental data synchronization and regular archiving strategies. This prevents excessive storage resource usage from database redundancy. Daily document fields are linked to on-site personnel and customer service requirements. Foreign key constraints and permission controls must be set at the database level. This ensures correct data association and access security. Errors directly impact service contract compliance. Databases must include reliable backup and recovery mechanisms. This reduces data loss risks, and avoids customer penalties or contract termination.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://[username]:[password]@[host]:27017/fastgpt?authSource=admin | Stores unstructured data for on-site tickets and inspection logs. Requires specifying the authentication source and target database name, to adapt to storage requirements of FastGPT v4.17.0. |
PG_URL | postgresql://[username]:[password]@[host]:5432/fastgpt_sla?sslmode=require | Stores structured data for SLA monthly reports and asset inventories. Enables SSL to secure internal network transmission and prevent sensitive data leaks. |
DB_MAX_LINK | 20–30 | Matches daily concurrent processing volume for on-site services. Prevents database connection pool exhaustion from causing ticket write or query failures. |
REDIS_URL | redis://[host]:6379/0 | Caches on-duty shift records and real-time monitoring alert data. Reduces query pressure on the primary database and improves ticket processing efficiency. |
Three Common Misconfigurations
- Symptom: MongoDB fails to start. Logs show mount directory permission errors. Cause: On-site engineers did not reset the owner and permissions of the mount directory during database migration or reinstallation. This prevents the FastGPT process from accessing data files.
- Symptom: Database connection error returns
Failed to connect to [host]:port. Cause: The customer internal network firewall does not allow database port traffic, or the address configuration inMONGODB_URI/PG_URLis incorrect. The configured address does not match the customer internal network database nodes. - Symptom: Single-node concurrent processing capacity is insufficient. 50 concurrent requests cause service lag. Cause: The
DB_MAX_LINKconfiguration value exceeds the database’s carrying capacity, or the connection pool parameters were not adjusted based on daily ticket volume for on-site services. This leads to connection exhaustion.
How to Confirm Configuration is Complete
- Log in to the FastGPT database monitoring panel. Check the active connection count for the connection pool. Confirm the value is within the configured
DB_MAX_LINKrange. - Perform a create and query operation for an on-site ticket. Confirm data can be written and read normally, with no error messages returned.
- Check the database backup task status. Confirm daily and monthly archiving tasks run as scheduled.
- Verify the
REDIS_URLcaching function. Check if real-time alert data update delays meet monitoring requirements for on-site services.
The values provided are common starting points. They should be evaluated 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.