What data for this category looks like
Data for this category primarily comes from cloud platform consoles, network topology files, traffic monitoring reports, and customer architecture diagrams. Daily maintenance documents include VPC planning plans, security group rule documentation, load balancer configuration manuals, and network change orders. Most entries are structured configuration items with clear parameters and rules. Data updates trigger each time a network change or support ticket is completed, with one update per single change. Document fields include network segment ranges, port mapping rules, health check thresholds, and backend server group IDs. Common units are milliseconds, count, characters, and similar units.
Constraints on Knowledge Base Retrieval and Recall
The high update frequency of this category requires knowledge base retrieval to support real-time synchronization of the latest network change data, to avoid recalling expired configuration rules. Structured documents and specialized segmented fields require retrieval to accurately match professional terms such as network segments and ports, and cannot rely on generalized semantic recall. Differences in data formats from multiple sources require unified processing into standard network configuration entries before recall, to ensure consistency of retrieval results. The small data volume corresponding to a single change means there is no need to recall too many entries, to avoid introducing irrelevant network rules that interfere with responses.
How to Configure Settings
The following configurations apply to FastGPT v4.17.0
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Matches the precision requirement for cloud network professional terms, and avoids recalling irrelevant security group rules |
limit | Top 8 entries | The number of fields in a single network configuration document is limited; too many entries will exceed the context window |
searchMode | Semantic search | Adapts to the semantic matching needs of professional network configurations, and performs better than keyword search |
usingReRank | Enabled | Performs secondary sorting on recalled results by relevance, to correct deviations from semantic search |
datasetSearchUsingExtensionQuery | Enabled | Converts the user's colloquial questions into professional network terms, to improve retrieval matching accuracy |
collectionIds | Bind the knowledge base collections corresponding to the target VPC and load balancer | Restrict the retrieval scope, and avoid interference from cross-category irrelevant data |
Three Common Configuration Mistakes
- Phenomenon: When uploading a load balancer configuration document larger than 800 MB in size, a timeout error is reported in the interface, but the upload process is actually completed, and the corresponding file cannot be found in the interface afterwards. Cause: The timeout threshold for knowledge base uploads was not adjusted. The default threshold is insufficient to cover large-volume network configuration documents.
- Phenomenon: In multi-round technical support conversations, subsequent questions do not associate the VPC or load balancer configuration context of the current conversation, and the retrieval scope reverts to the full knowledge base. Cause: The
collectionIdsparameter corresponding to the current conversation was not bound, resulting in retrieval not being limited to the current customer's exclusive knowledge base collection. - Phenomenon: The retrieval results return a large number of irrelevant cloud host configuration entries, and cannot accurately match load balancer rules. Cause:
datasetSearchUsingExtensionQuerywas not enabled, and the user's colloquial questions were not converted into professional network terms, resulting in semantic matching deviations.
How to Verify Successful Configuration
- A test load balancer configuration document is uploaded. Confirm the upload progress has no timeout error, and the uploaded file displays normally in the interface.
- Test questions containing "security group rules" and "health check" are submitted. Verify that retrieval results only include bound load balancer knowledge base entries, with no cross-category data.
- A multi-round conversation is initiated: first ask about the configuration of a specific VPC, then ask about the health check rules of the load balancer under that VPC. Confirm retrieval results associate the context of the current conversation.
- The
similarityparameter is adjusted to different ranges. Changes in the relevance of retrieval results are tested, confirming that parameter adjustments affect the precision of recalled results.
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.