What the Data for This Category Looks Like
The data sources for this category are Prometheus, Zabbix, cloud monitoring, application logs, and CMDB systems. Daily content includes four types of documents: monitoring metric lists, alert rules, on-call manuals, and alert change records. Data is updated daily or after each configuration change. Fields include metric name, collection cycle, threshold parameters, notification link configuration, associated team identifier, and more. Some metrics use units such as milliseconds, request count, and bytes.
Constraints on Permissions and Data Isolation
This category’s data sources cover multiple monitoring systems and are associated with different operations teams. Permissions and data isolation must accurately match team access permissions for corresponding data sources. Documents contain sensitive threshold parameters and notification link configurations. Cross-team access and modification permissions must be strictly restricted. Data is updated in real time after configuration changes. Isolation rules must be synchronized to adapt to the updated resource scope. Alert change records retain operation traces. Configuration permissions and view permissions must be differentiated to prevent unauthorized modification or leakage of sensitive configuration information.
How to Configure
The following configurations are based on FastGPT v4.17.0, and are adapted to the permissions and data isolation requirements of the monitoring alert configuration scenario.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Unique identifier bound one-to-one with the operations team | Matches FastGPT v4.17.0’s team permission system, accurately dividing the access scope of monitoring data across different teams |
| Data Source Binding Scope | Only bind Prometheus and Zabbix instances associated with the current team | Restrict cross-team access to unauthorized monitoring data sources to avoid data leaks |
tmbId | Unique identifier bound to the team’s alert configuration template | Ensures each team uses an exclusive alert rule template, preventing cross-team reuse of templates |
| Alert Rule Activation Delay | 30-60 seconds | Matches the collection cycle of monitoring data, avoiding excessive delay that affects alert response timeliness |
| Change Audit Switch | Enabled | Retains operation traces of alert configurations to facilitate permission tracing and problem troubleshooting |
| Team View Permissions | Only team members can view alert change records for their own team | Restricts the view scope of sensitive configurations to comply with operational data security specifications |
Three Common Misconfigurations
- Phenomenon: Cross-team alert data remains visible after configuring
teamId. Cause: The data source binding scope was not updated synchronously, leaving old permission configurations unoverwritten. - Phenomenon: SQL permission errors occur after restarting the deployment environment. Cause: Database access permissions were not bound to
teamId, leading to lost or incorrectly loaded permission configurations after restart. - Phenomenon: Unable to add monitoring configurations for a second team. Cause: The association between
tmbIdand the new team was not configured correctly, preventing the new team from accessing exclusive alert templates and data source permissions.
How to Verify Successful Configuration
- Log in to FastGPT accounts for different teams, view the monitoring alert configuration list, and confirm that only alert rules and data sources associated with the current team are visible.
- Perform an alert configuration change operation, and check whether the operation trace and team identifier of the current operator are recorded in the change audit log.
- Restart the FastGPT deployment environment, and verify that the permission rules for alert configurations are not reset, and that the binding relationship between
teamIdand data sources still matches correctly. - Attempt to access the alert configuration page using an account that is not a team member, and confirm that the page returns a no permission prompt or an empty list.
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.