Data Sources and Structure for This Category
Data for this category originates from incident timelines, operation logs, monitoring metrics, and code commit records. Update frequency is either after each major incident or once per month. Daily produced documents include RCA reports, incident tickets, retrospective meeting minutes, and rectification tracking sheets. Document fields cover incident occurrence time, root cause identification results, rectification measures, tracking status, and more. Primary units are timestamps, counts, and character lengths. No unified quantitative statistical values exist. Data is maintained by SREs, technical leads, and quality teams. Consistency and completeness of multi-source data must be ensured.
Constraints on Deployment and Upgrade
Data sources for this category are scattered, and update rhythms are irregular. During deployment, access configuration for multi-source logs and monitoring metrics must be supported to prevent data collection interruptions. Daily document structure is fixed. Deployment must complete field mapping configuration for documents such as RCA reports and incident tickets to ensure normal data import and export. Each major incident triggers data updates. During upgrades, historical incident data must not be lost. Existing operation and maintenance tool integration logic for SRE teams must be adapted to reduce operation thresholds. Incident data involves core operation and maintenance information. Access permissions must be strictly controlled during deployment and upgrade to avoid data leaks.
Configuration Settings
These configurations apply to FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@host:port/database?authSource=admin | Stores structured incident data such as incident tickets and RCA reports. Specifies an authentication source to ensure data security |
REDIS_URL | redis://:password@host:port/0 | Caches temporary query results for incident timelines and monitoring metrics to reduce database load |
DB_MAX_LINK | 20–30 connections | Matches concurrent query volume for incident data, prevents connection exhaustion that causes incident ticket entry failures |
STORAGE_S3_ENDPOINT | Fill according to internal network storage service address | Stores log files and retrospective meeting minute attachments related to incidents, adapts to internal network deployment scenarios |
FE_DOMAIN | https://your-fastgpt-domain.com | Provides access entry for RCA reports, adapts to redirection requirements for internal operation and maintenance systems |
FILE_TOKEN_KEY | Generate according to enterprise internal key specifications | Generates temporary access credentials for attachment uploads, controls access permissions for incident documents |
Three Common Configuration Errors
- Phenomenon: Unable to pull official images during internal network deployment. Reported error:
Error response from daemon: Get https://registry-1.docker.io/v2/: net/. Cause: Internal network image source or proxy not configured, preventing access to external container repositories. - Phenomenon: After configuring a locally deployed DeepSeek model, permission errors occur during FastGPT testing. Cause: Model access keys not correctly configured, or internal network network policies restrict port access, preventing FastGPT from establishing a valid connection to the model service.
- Phenomenon: AI conversations after the judge in advanced orchestration cannot obtain initial user questions. Cause: Context passing parameters not correctly configured, causing the judge's output to not be correctly bound to the input fields of subsequent AI conversations.
How to Verify Successful Configuration
- Log in to the data connection module of the FastGPT backend. Check whether the format of configuration items such as
MONGODB_URIandREDIS_URLmatches the internal network service address. - Submit a test incident ticket. Check whether the system can normally save and generate the corresponding RCA report template to confirm that the field mapping configuration takes effect.
- Trigger a simulated incident data import. Check the load status of the cache module to confirm that the
DB_MAX_LINKconfiguration does not exceed the connection limit. - Access the address configured for
FE_DOMAIN. Confirm that the operation and maintenance interface loads normally, and that the attachment upload function can normally generate temporary access credentials.
The values given 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.