What data for this category looks like
Data related to internal network and WiFi operations maintenance is generated and maintained by network administrators, desktop support staff, and contracted on-site personnel. Daily documents include network topology diagrams, change orders, fault records, wireless coverage inspection reports, and more. Data sources include switch consoles, wireless controllers, office area network monitoring systems, and end-user trouble ticket channels. Data is updated daily or immediately when configuration changes are made. Core fields include port numbers, VLAN configurations, fault occurrence times, wireless signal strength, and others. There are no unified fixed units. Matching must be done based on specific document contexts.
What constraints do these characteristics impose on knowledge base retrieval and recall?
The data characteristics of this category impose multiple constraints on the retrieval and recall process. First, data sources mix structured device configurations and unstructured fault records. This requires retrieval to support both exact matching and semantic understanding. Second, update frequency is high, with changes taking effect immediately. This requires recall mechanisms to support incremental updates and real-time synchronization. Third, fault location and troubleshooting are core time-consuming tasks. This requires retrieval results to prioritize topology and record documents that are strongly relevant to the current issue. Fourth, the consequences of errors such as service interruptions or meeting disruptions are severe. This requires retrieval results to have high accuracy, avoiding irrelevant information that interferes with decision-making.
How to set the configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Matches professional terminology related to internal network faults, avoids low-relevance results interfering with maintenance judgments, and adapts to the text characteristics of device configurations and fault records |
limit | Top 10 entries | Balances information acquisition efficiency and completeness during on-duty maintenance, avoids excessive content occupying conversation context, and meets the scenario needs of rapid fault troubleshooting |
searchMode | Hybrid retrieval | Matches both structured port/VLAN configurations and unstructured fault record text, covering all types of documents in this category |
usingReRank | Enabled | Re-ranks initially recalled results based on maintenance scenario priority, prioritizes documents related to fault location and network optimization, and shortens troubleshooting time |
collectionIds | Specify internal network maintenance collection | Limits retrieval scope, excludes irrelevant knowledge base content, improves accuracy, and avoids interference from cross-business line documents |
datasetSearchUsingExtensionQuery | Enabled | Automatically supplements extended query terms related to maintenance scenarios, such as "port occupancy", "wireless roaming", "VLAN isolation", and covers more relevant documents |
The following configurations are based on FastGPT v4.17.0.
Three common configuration errors
- Retrieval results exceed the specified internal network maintenance scope, returning documents from other business lines. This occurs because the
collectionIdsparameter is not configured, and the knowledge base collection is not limited, resulting in retrieval covering the full knowledge base. - Network topology diagrams and inspection report images uploaded to the knowledge base cannot be displayed normally in conversations. This occurs because the associated configuration for knowledge base image retrieval is not enabled, or structured index information is not generated for the images, preventing retrieval from associating image content.
- The number of single retrieval results far exceeds expectations, causing context overflow. This occurs because a reasonable
limitparameter is not set, or thesimilaritythreshold is set too low, recalling too many low-relevance documents.
How to confirm configurations are properly set
- Create an independent knowledge base collection that only contains internal network maintenance documents. Call the retrieval interface with the
collectionIdsparameter, and verify that returned results only include documents from this collection. - Enter a typical maintenance question, such as "How to fix weak wireless coverage on a certain floor", and check if retrieval results prioritize wireless coverage inspection reports and fault record content to confirm the re-ranking function is active.
- Upload a test image to the knowledge base, enter a question that includes an image description, such as "View this switch port configuration diagram", and verify that the corresponding image can be displayed normally in the conversation.
- Upload two operation and maintenance change orders with completely identical content, perform a retrieval, and check if only one record is displayed to confirm that the duplicate file filtering logic is active.
The values provided here 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.