What the Data for This Category Looks Like
The core data for performance testing and capacity assessment includes four types of documents: stress testing plans, capacity assessment reports, stress testing data records, and optimization suggestion sheets. Data sources include stress testing platforms, APM monitoring, database slow logs, and production traffic baselines. The update frequency follows monthly archiving or full synchronization when major versions are released. A single stress testing data entry includes fields such as throughput (unit: TPS), average latency (unit: milliseconds), CPU/memory usage, and number of deployed nodes. The stress testing data structure is unified across different business lines, but the content is independent for each line.
Constraints Imposed by These Characteristics on Permission and Data Isolation
Stress testing data is associated with production environment traffic baselines and resource usage, and falls under sensitive business information. Access permissions for different business lines must be strictly isolated. Multiple data sources involve production system monitoring information; improper permission configuration may lead to leakage of sensitive production environment information. Document data includes architecture optimization suggestions involving core business adjustment plans, so access scope must be restricted by role. The data update rhythm is not fixed, so permission configuration must support dynamic adjustments to match monthly or major version update cycles.
How to Configure
In FastGPT v4.17.0, permission and data isolation settings for performance testing and capacity assessment scenarios can be completed via the following configuration items:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId grouping rules | Divide into independent groups by business line | Stress testing data is generated by business line, and stress testing platform data from different business lines must be physically or logically isolated |
| Member permission granularity | Bind corresponding teamId by role | Performance testing engineers can only access stress testing plans and data from their own team; architecture teams can view cross-team capacity assessment summary data |
| Data retention period | Retain temporary stress testing data for 30 days, archived data for 180 days | Matches the update frequency of monthly archiving and major version synchronization of stress testing data, balances storage costs and compliance requirements |
| Cross-team sharing toggle | Default off, requires approval to enable | Prevents unnecessary cross-team access to sensitive data, ensures stress testing data is only shared in authorized collaboration scenarios |
| Sensitive data desensitization rules | Mask production traffic baseline fields | Stress testing data contains core production environment parameters, desensitization reduces the risk of information leakage |
| Export permission restriction | Only allow accounts bound to teamId to trigger data exports within 1000 MB | Prevents unauthorized export of stress testing data, meets security and compliance review requirements |
Three Common Misconfiguration Issues
- Symptom: Members from cross-business lines can view stress testing data not belonging to their team. Cause:
teamIdgrouping is not configured by business line, so the permission verification logic does not take effect. - Symptom: After a team invitation is sent, invited members do not receive any notifications. Cause: The team member notification toggle is not enabled, so permission change information is not synchronized to invited accounts.
- Symptom: In self-hosted FastGPT instances, stress testing data from different accounts is visible to each other. Cause: The binding relationship between
tmbIdand accounts is not configured, so the basic permission verification logic is not enabled.
How to Verify Successful Configuration
- Use a test account not associated with the target team to attempt access to stress testing plan documents from the target team, and confirm that the document cannot be opened or displays a no access permission prompt.
- Send a team invitation link to a test email address, confirm that the invited account can receive system notifications and complete team binding.
- Trigger a stress testing data export operation, confirm that only accounts bound to
teamIdfrom the target team can successfully export data, while other accounts prompt no permission. - View the exported stress testing report, confirm that production traffic baseline fields have been masked, with no original sensitive information exposed.
The values provided are common starting points and should be evaluated against samples from the relevant deployment.
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.