What this category of data looks like
Data for this category originates from monitoring alerts, log platforms, APM tools, and user feedback. It updates in real time or is generated when a single incident is triggered. Core documents include fault tickets, incident timelines, emergency response plans, and fault notifications. Fields include incident unique identifier, occurrence time, affected service scope, processing steps, notification recipients, and status identifiers. The size of individual data entries varies based on incident complexity. All data must be linked to the full lifecycle workflow of the corresponding incident. This document is based on FastGPT v4.17.0.
What constraints these characteristics impose on database and operations workflows
Multi-source data access requires databases to support mixed storage of structured and unstructured data, to avoid splitting into multiple independent systems that increase operational complexity. Real-time update requirements demand database connection pools have sufficient concurrent processing capacity, to prevent connection exhaustion during incident writes. Fixed incident lifecycle fields require databases to support transactional operations, to ensure consistency between ticket status changes and notification records. The high-risk nature of fault handling requires databases to have complete backup and disaster recovery mechanisms, to avoid secondary faults caused by data loss.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PG_URL | postgresql://admin:securepass@db-host:5432/fastgpt_event | Stores structured fault tickets, incident timelines, and status data, meeting relational database transaction requirements |
MONGODB_URI | mongodb://admin:securepass@mongo-host:27017/event_logs | Stores unstructured log snippets and user feedback text, supports flexible field expansion |
DB_MAX_LINK | 20–30 | Handles concurrent write requests from real-time alerts and incidents, prevents database connection exhaustion |
REDIS_URL | redis://:securepass@redis-host:6379/0 | Caches temporary incident status and impact calculation results, reduces high-frequency query pressure on databases |
| Database connection timeout | 600 seconds | Adapts to long-duration impact analysis and notification synchronization workflows, avoids mid-process interruptions |
Three common configuration mistakes
- Unable to execute SQL commands after accessing the pgvector container. This occurs because the
PG_URLparameter is not configured correctly, or the database initialization script has not been run to complete table structure creation. - Accidentally setting maximum response tokens to the number of concurrent threads, leading to insufficient system concurrent processing capacity. The symptom is that some incident processing requests time out and return status code 504.
- Unable to connect to Milvus via Attu when using the Milvus database. Symptoms include connection timeouts or inability to view vector data. This occurs because the default port 19530 required by Attu is not open, or the correct vector database connection address is not configured.
How to confirm successful configuration
- Run the database connection test script to verify that the databases corresponding to
PG_URLandMONGODB_URIcan normally write and query structured and unstructured data. - Check connection pool monitoring metrics to confirm that the current active connection count does not exceed the upper limit set by
DB_MAX_LINK. - Access the Attu management interface, enter the Milvus database connection address and port, and verify that vector data can be viewed normally.
- Simulate a fault incident reporting workflow to confirm that data can be synchronously written to the database and the corresponding incident timeline document is generated.
The values provided here are common starting points and should be evaluated against local deployment 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.