This document is written for FastGPT v4.17.0.
What this category of data includes
This category of data primarily comes from logging systems, distributed tracing (Trace) platforms, metrics systems, and business application SDKs. Data updates typically occur via daily batch synchronization or alongside application version releases. Daily supporting documents include logging collection specifications, distributed tracing guides, metric dictionaries, and dashboard configuration records. Common data fields include timestamps, service identifiers, log levels, distributed trace IDs, metric values and their corresponding units. Some fields carry request context and error stack information.
Constraints imposed by these characteristics on permission and data isolation
This category of data spans multiple systems and carries link context and error stack information. Access scope for different operations and maintenance teams must be strictly separated to prevent cross-team acquisition of sensitive business logs. Log and metric data updates alongside service versions. Permission configurations must match the iteration rhythm of service groups to avoid leftover permissions from old versions. Daily supporting documents such as collection specifications and dashboard configuration records contain sensitive configuration items. Access to these items must be restricted to operations and maintenance personnel from the corresponding teams only. Some fields carry request context. The tmbId must be used to associate the team to which the user belongs, to prevent unauthorized access to cross-team distributed tracing data.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Team data isolation dimension | Divide data scope by teamId | Match the service ownership groups for logging and distributed tracing data, ensure that operations and maintenance personnel in the same group only access data from their own team |
| User permission binding | Limit operable dashboards and log collections by tmbId | Match the team ownership of metric dashboards and log collection configurations, prevent cross-team modification of configurations |
| Permission cache duration | 300 seconds | Balance the response speed of permission changes and system load, adapt to the daily batch data synchronization rhythm |
| Sensitive information filtering rules | Automatically hide sensitive fields in error stacks | Prevent sensitive information leakage, meet security requirements for operations and maintenance scenarios |
| Permission check timing | During each session initialization | Ensure permission changes take effect immediately, adapt to the real-time access needs of operational on-call work |
| Global variable isolation | Isolate variables with the same name by user ID | Match the work scope of different operations and maintenance personnel, avoid conflicts of global variables |
Three common misconfigurations
- Symptom: When attempting to access cross-team distributed tracing data, a prompt "No permission to operate this conversation record" appears. Cause: No data isolation rule configured for the
teamIddimension, and the system does not verify the match between the user's affiliated team and the data's affiliated team. - Symptom: Different operations and maintenance personnel see identical values for global variables with the same name. Cause: No variable isolation configured by user ID or
tmbId, and the global variable scope is not limited to the corresponding team or individual. - Symptom: Log dashboards do not update after switching teams. Cause: Permission cache has not expired in a timely manner, and permission checks for the
teamIddimension have not been retriggered.
How to verify correct configuration
- Initiate a cross-team log query request, confirm that the system intercepts the request and returns a permission denied prompt, verifying that the
teamIdisolation rule is active. - Use different user accounts to log in, view the values of global variables with the same name, confirm that different accounts display different results, verifying that variable isolation for the
tmbIddimension is active. - Switch teams and refresh the page, confirm that dashboards and log data update synchronously, verifying that the permission cache refresh logic works correctly.
- View error stack content, confirm that sensitive fields are automatically hidden, verifying that the sensitive information filtering rule is active.
The values provided here are common starting points. They should be evaluated against the user'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.