What data looks like for this category
Data sources for this category include cloud audit logs, IAM permission systems, CMDB resource management platforms, and security baseline scanning tools. Update frequency is monthly or quarterly. Daily output documents include compliance checklists, permission audit reports, resource lists, and rectification tracking forms. Data fields cover resource unique identifiers, permission configuration items, compliance status, rectification tracking records, and more. Content includes both structured and semi-structured data, with no unified single-document length standard.
What constraints these characteristics impose on the re-ranking and hybrid retrieval link
This category has a low data update frequency, so high-frequency real-time retrieval is not required. Retrieval result accuracy must be ensured to avoid missing compliance anomalies. Data comes from multiple systems, with formats including structured resource attributes and semi-structured audit logs. Hybrid retrieval must balance matching logic for both types of content. Document fields focus on compliance-related permissions, configurations, and rectification status. The re-ranking link must prioritize matching high-priority compliance violation fields and filter low-relevance general resource descriptions. The scale of core data entries is moderate. Excessively expanding the recall range will increase the computational load of the re-ranking link and affect overall response speed.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
usingReRank | Enabled | Cloud resource compliance auditing requires prioritizing matching core fields such as permission anomalies and compliance violations. Re-ranking can filter low-relevance recall results and improve the accuracy of anomaly identification |
similarity | 0.75–0.85 | Compliance-related keyword matching requires high confidence to avoid mistakenly recalling non-compliance-related resource entries |
limit | Top 15–25 entries | The scale of core data entries for cloud resource compliance auditing is moderate. Limiting the number of recalled entries can reduce the computational load of subsequent re-ranking |
searchMode | Hybrid Retrieval | Combines the text features of cloud audit logs and the structured resource attributes of CMDB. Hybrid retrieval can cover multi-dimensional compliance-related information |
| Re-ranking model call timeout threshold | Calibrated based on actual testing | Compliance audit data has a low update frequency, so high-frequency calls are not required. The timeout threshold adapts to the model response speed of FastGPT v4.17.0 offline deployment |
Three common configuration mistakes
- Issue: After deploying FastGPT v4.17.0 offline, clicking the re-ranking model test on the model management page displays a request error. Cause: The local deployment path and port of the re-ranking model are not correctly specified in the configuration file, or the re-ranking model service is not started.
- Issue: The number of re-ranking results after knowledge base Q&A does not match the configured
limitparameter. Cause: The re-ranking model and retrieval process are not correctly associated, or the recall results are not correctly passed to the re-ranking link. - Issue: The overall response time is long after hybrid retrieval. Cause: The number of recalled entries is set too high, and the field weight of re-ranking is not optimized for the structured characteristics of compliance audit data.
How to confirm the configuration is complete
- Navigate to the knowledge base configuration page of FastGPT, confirm the
usingReRankswitch is enabled in the retrieval settings module, and verify thesimilaritythreshold andlimitrecall count are set as required. - Upload a compliance checklist as a test document, initiate internal ticket Q&A, and check if retrieval results prioritize displaying entries related to permission anomalies and compliance violations.
- Call the model test interface to confirm the re-ranking model returns a 200 response status code, with no timeout errors.
- Compare retrieval results with and without re-ranking enabled, and confirm the relevance ranking of re-ranked results aligns better with compliance auditing business logic.
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.