What data for this category looks like
Data for this category comes from incident timelines, system logs, monitoring metrics, and code commit records. Update frequency is either after each major incident or once per month. Regularly produced documents include root cause analysis (RCA) reports, incident tickets, review minutes, and rectification tracking sheets. Document fields cover incident occurrence timeline, impact scope, root cause analysis conclusions, rectification measures, tracking status, and more. There are no unified fixed units; values adjust based on document type. Data volume fluctuates with incident scale, and relevant data entries vary significantly across different incident scenarios.
What constraints do these characteristics impose on the database and operations link
The non-fixed update rhythm of incident data requires the database to support on-demand writes and batch imports, avoiding redundant overhead from fixed scheduled tasks. Multi-source heterogeneous data sources require the database to support mixed storage of structured logs, time-series metrics, and text-based review documents. The fluctuating data volume for a single incident requires database connection pool configuration to adapt to peak loads, preventing connection exhaustion. The long-term retention requirement for rectification tracking sheets requires the database to support cold data archiving mechanisms to reduce storage costs. Additionally, cross-document association queries related to root cause analysis require the database to establish appropriate indexes to improve query efficiency.
How to configure settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
MONGODB_URI | Configure using the actual deployed MongoDB instance address, in the format mongodb://user:pass@host:port/fastgpt?authSource=admin | Adapts to multi-source heterogeneous incident log and review document storage needs, supports flexible document-type data queries, and is compatible with the document storage logic of FastGPT v4.17.0 |
PG_URL | Configure using the actual deployed PostgreSQL instance address, in the format postgresql://user:pass@host:port/fastgpt | Used to store structured incident tickets and rectification tracking sheet data, ensures transaction consistency, and supports CRUD operations for structured data |
DB_MAX_LINK | 20–30 connections | Adapts to peak data writes and batch query connection needs for single incidents, preventing service interruptions caused by connection exhaustion |
REDIS_URL | Configure using the actual deployed Redis instance address, in the format redis://:pass@host:port/0 | Used to cache frequently accessed incident time-series metrics and root cause analysis intermediate results, reducing database load |
Three common configuration mistakes
- Symptom: In Docker deployment environments, when uploading knowledge base parsing files, logs continuously output
slow operation xxxxmsalerts, and MongoDB connection responses time out. Cause:DB_MAX_LINKis not configured to a reasonable range, insufficient connection pool capacity causes database requests to queue, triggering slow operation alerts. - Symptom: The dataset.csv exported from the knowledge base only contains the index field, with no content field. Cause: The storage content field corresponding to
MONGODB_URIis not correctly associated, and the text field of review minutes or RCA reports is not mapped. - Symptom: When fetching data from database tables, only partial records are returned, and the complete dataset is not provided. Cause: Reasonable batch read parameters are not configured, or incremental synchronization rules are not set, resulting in interruptions during batch data reading.
How to confirm configurations are correct
- Connect to the corresponding database instance, verify that the addresses and permissions configured for
MONGODB_URI,PG_URL, andREDIS_URLare valid. - Submit a test incident data entry, check whether it can be correctly written to the specified database collection and table.
- View system runtime logs, confirm that the database connection count does not exceed the threshold configured for
DB_MAX_LINK. - Export a test rectification tracking sheet data set, check whether field integrity and format meet expected requirements.
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.