What This Category of Data Looks Like
This category of data is sourced from incident timelines, operational logs, monitoring metrics, and code commit records. The update frequency is either after each major incident or once per month. Daily output documents include RCA reports, incident tickets, post-incident review minutes, and rectification tracking sheets. Document fields include incident occurrence time, root cause identification, impact scope, rectification measures, verification results, and more. There are no uniform mandatory units. Some fields such as incident duration use seconds as the unit, while rectification cycles use days as the unit.
Constraints Imposed by These Characteristics on the "Sharing and Embedding" Workflow
Data has a low update frequency but a large single-content volume. Avoid triggering full-content synchronization frequently during sharing. Documents contain sensitive incident root cause and customer impact information. Sharing authentication must be strictly bound to internal operations account permissions. Holding a sharing link does not grant access authorization. Data sources include unstructured reference content such as logs and monitoring data. When embedding, retain the rendering capability of original reference links. Fields in rectification tracking sheets are updated as incident closure progresses. Content updates are triggered by external business systems and synchronized to the FastGPT knowledge base. The content displayed via sharing links is the latest data currently stored in the knowledge base. The sharing scope in operations on-call scenarios is limited to internal teams, and external access permissions must be strictly restricted.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Sharing Entry shareId | Copy the full sharing link generated by the system; do not manually replace the identifier | Identifies the sharing entry; business records and data permissions for incident management and root cause analysis must still be handled by external systems |
| Sharing Link Validity Period | Test starting point: 7 days; adjust based on actual testing of incident management and root cause analysis collaboration cycles and revocation requirements | Verify availability during the validity period and access behavior after expiration; this value is not an official default or industry statistic |
| QPM | Test starting point: 20 requests per user per minute; adjust based on actual load | Limits the access frequency of a single user; validation requires combining request logs and actual load |
| Identity Verification | When identity permission requirements apply, first verify commercial edition capabilities and the uid returned by the third-party identity service | Holding a sharing link does not equate to having business data permissions; third-party identity and data scope must be verified separately |
| Reference Content Display | Select display configurations for reference fragments, full text, and original text based on the sensitivity of incident management and root cause analysis materials | Check displayed content within authorized data ranges; hidden interfaces cannot be used as a substitute for data permission control |
| Conversation Record Validation | Test example: Prepare 10 incident management and root cause analysis Q&A samples, and check them in the same browser and another device respectively | Anonymous records rely on browser local identity; retention cannot be guaranteed across devices or after cache clearance |
Three Common Misconfigurations
- Failure to open the sharing entry related to incident management and root cause analysis. First verify the full system-generated link and its validity period, then check browser request statuses. Do not manually replace
shareId. - The visible scope of incident management and root cause analysis data does not match expectations. Verify third-party identity verification results, workflow request parameters, and external system data permissions separately. The sharing entry identifier itself does not provide business authorization.
- The same incident management and root cause analysis Q&A cannot display the original conversation on another device. For anonymous scenarios, first check device, browser, and local identity status. Record retention cannot be guaranteed across devices or after cache clearance. Do not use this phenomenon alone to determine service anomalies.
How to Confirm Proper Configuration
- Access the system-generated sharing link via Application Details > Publish Channels > Unauthenticated Window, and confirm that RCA reports, incident tickets, and other content can be viewed normally after passing internal identity verification.
- Open the sharing link or embedded page, and check that reference links in the displayed content can be clicked normally to jump and render.
- Simulate an incident update scenario, have an external business system synchronize the updated rectification tracking sheet to the FastGPT knowledge base, and confirm that the content displayed via the sharing link matches the knowledge base backend.
- Confirm that the associated jump function of the external business system operates correctly.
The values provided here 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.