What This Category of Data Looks Like
Operational data for incident management and root cause analysis originates from incident timelines, system logs, monitoring metrics, and code commit records. Update frequency is once per major incident or once per month. Daily produced documents include RCA reports, incident tickets, post-mortem minutes, and remediation tracking sheets. RCA reports contain incident timestamps, root cause analysis conclusions, and remediation items. Incident tickets include incident numbers, responsible teams, and processing progress. Remediation tracking sheets include remediation item numbers, completion status, and acceptance timestamps. Most data fields involve sensitive information from production environments. There are no unified fixed units, and values vary based on specific incident scenarios.
What Constraints Do These Characteristics Impose on Permission and Data Isolation?
Data sources include production monitoring and code commit records, which involve production environment permissions. Strictly divide data access scope by business teams to prevent cross-team leakage of sensitive operational information. Daily documents are mostly internal sensitive post-mortem materials for their respective teams. Restrict access and editing only to members of the responsible team. Data update frequency is low, but single data volume is large. Configure permission verification to support batch binding of data by team dimension to avoid excessive single verification overhead. Remediation tracking sheets are associated with specific business domains. Keep remediation data from different business domains separate to prevent cross-domain leakage of remediation information.
How to Configure Settings
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Configuration Approach | Rationale |
|---|---|---|
teamId | Bind the unique identifier of the business team to which the incident belongs | Match the ownership team attribute of RCA reports and incident tickets to ensure data is only visible to the corresponding team |
teamId | Divide by the responsible team listed on the remediation tracking sheet | Correspond to the ownership of remediation tracking sheets in business facts to prevent cross-team access to remediation data |
tmbId | Bind the cluster ID to which the monitoring metrics belong | Match the cluster scope of incident timelines and monitoring metrics to isolate operational data from different clusters |
| Team data isolation scope | Only open RCA reports and incident tickets from the current team within the last 30 days | Align with the data update frequency of once per major incident or once per month to avoid leakage of expired data |
| Plugin call permission configuration | Restrict access to team internal members only, return up to 5 incident tickets per request | Match the usage scenarios of operational on-call and internal ticket Q&A to prevent external parties from calling root cause analysis tools |
| Team invitation validity period | 7 days | Ensure invited members complete the team join process within a reasonable timeframe and avoid expired invitations |
Three Common Misconfiguration Issues
- Symptom: Cross-team members can still access RCA reports and incident tickets from the current team. Cause:
teamIdwas not correctly bound to the owning team of the corresponding incident, resulting in ineffective permission verification. - Symptom: Team custom plugins cannot be called as tools, and no related configuration entry exists. Cause: The tool call permission configuration for team plugins was not enabled, or the plugin was not associated with the corresponding
teamId. - Symptom: After sending a team invitation, invited members receive no notifications and cannot view team data. Cause: No notification trigger rule was configured for team invitations, or
tmbIdwas not correctly associated with the target team of the invitation.
How to Verify Successful Configuration
- Switch to an account from a non-owning team, attempt to access the RCA reports of the corresponding team, and confirm that sensitive operational data from that team cannot be viewed.
- Call the root cause analysis tool, check that the returned results only include incident logs, monitoring metrics, and incident tickets bound to the current
teamId. - Send a team invitation, confirm that invited members receive notifications within the 7-day validity period and can successfully join the corresponding team to view data.
- After configuring multiple teams, confirm that root cause analysis data for each team is only visible to members of that team, with no cross-team data leakage.
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.