What data for this category looks like
This category’s data is generated following post-incident root cause analysis and remediation implementation, and is maintained daily by SREs, technical leads, and quality teams. Daily documents include RCA reports, incident tickets, post-mortem minutes, and remediation tracking sheets. Data sources are incident timelines, operational logs, monitoring metrics, and code commit records. Update frequency is either after each major incident or once per month. Document fields include incident occurrence time, root cause description, associated code commit ID, remediation measures, verification results, and other items. There are no uniform fixed units of measurement, and some fields are associated with specific business system identifiers.
What constraints do these characteristics impose on the source citation and traceability link
Incident-related data is scattered across multiple types of systems. Citation and traceability require linking cross-source data, and must clearly establish the association between code commit IDs and incident events. Update frequency is low but per-batch data volume is large, so the context length of a single citation must be limited to avoid exceeding processing limits. Document structures are non-standardized; RCA report fields vary across different teams, so flexible matching of source identifiers for document fragments must be supported. Associated fields in remediation tracking sheets must be bound to original incident records, and consistency of the association relationship must be verified during traceability to prevent incorrect associations. Matching cross-source data must account for format differences across systems to ensure the accuracy of traceability results.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Matches the typical text length of a single RCA report or post-mortem minute, to avoid context overflow |
responseData | Includes source, title, content fields | Adapts to the standardized traceability field requirements of documents in this category, ensuring complete return of source information |
detail | Enabled | Used to return detailed traceability information for code commit records associated with root cause analysis |
| Single search limit | Top 3 entries | Matches the number of incident-related documents per monthly batch, to avoid redundant citations |
| Source matching threshold | 0.75–0.85 | Used to match the degree of association between incident timelines and code commit records, ensuring accuracy of root cause traceability |
| Maximum context | 4000 token | Adapts to the total length limit after splicing multi-source data, aligning with FastGPT processing capabilities |
This configuration applies to FastGPT v4.17.0.
Three common misconfiguration issues
- Phenomenon: When calling the knowledge base, the returned citation limit is insufficient, and all associated RCA reports and incident tickets cannot be loaded. Cause: The
quoteMaxTokenparameter is set too low, and does not adapt to the text length of single documents in this category. - Phenomenon: When obtaining question-and-answer results via API, the download link for citation sources is empty or inaccessible. Cause: The
responseDataparameter is not configured correctly, only simplified summary information is returned, and complete source fields are not included. - Phenomenon: Code commit records associated with root cause analysis are not correctly traced. Cause: The
detailconfiguration item is not enabled, and the detailed code commit information matching logic is not activated.
How to confirm successful configuration
- Submit a test query containing incident root cause keywords, and check whether the returned results include associated code commit IDs and RCA report titles.
- Call the API to obtain the question-and-answer response, confirm that the
responseDatafield includes the three required traceability fields: source, title, and content. - View the configuration panel, confirm that the
detailswitch is enabled, to ensure that detailed source information is returned. - After adjusting the
quoteMaxTokenparameter, verify whether the number of returned citation sources matches the expected number of documents.
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.