Technical Documentation and API Q&A for CDN and Edge Acceleration Configuration: Source Citation and Traceability

The data for this category mainly comes from CDN consoles, DNS resolution records, user access logs, and monitoring alert data. Update frequency is

What data does this category include

The data for this category mainly comes from CDN consoles, DNS resolution records, user access logs, and monitoring alert data. Update frequency is daily or triggered when configuration changes. Daily generated documents include domain name access forms, cache rule configuration tables, refresh and preheating record forms, and fault analysis reports. Core fields include node ID, cache effective duration, access source IP, refresh request number, etc. Field units are mostly basic measurement units such as seconds, entries, and MB.

Decentralized data sources require traceability to associate unique identifiers across multiple platforms to avoid cross-data-source matching errors. Uncertain update frequencies require marking the generation time of source data when citing, to ensure cited content matches the current configuration. Fragmented document structure requires traceability anchors to match the field format of corresponding documents. Otherwise, original configuration items cannot be accurately located. Errors in this category directly affect public network access. The traceability link must retain complete call chain records to facilitate subsequent fault troubleshooting.

How to set configurations

Configuration ItemRecommended ApproachRationale for This Approach
quoteMaxToken800–1200 tokenMatches the single-item content length of CDN cache rule documents, to avoid truncating key configuration parameters
responseDataEnable full returnCovers all fields of CDN access logs and refresh records to meet traceability requirements
detailEnable detailed traceabilityRetains the original configuration’s node ID and request timestamp to facilitate association with monitoring alert data
Variable reference format{{datasetId:xxx,source:cdn}}Adapts to the data source identification rules of the CDN category, replacing the general format
Single traceability entry countTop 3 entriesMatches the conventional troubleshooting scope of CDN fault troubleshooting, to avoid information overload
Citation cache duration24 hoursMatches the daily update frequency of CDN data, to avoid citing expired configuration information

Three common misconfigurations

  • Symptom: Citation content is returned without configuring the citation switch. Cause: In FastGPT v4.17.0, citation output is enabled by default in some scenarios, and the corresponding configuration item is not manually closed.
  • Symptom: Variable reference format is invalid, unable to associate with the CDN data source. Cause: The general variable format is used, and the CDN category’s data source identification rules are not adapted.
  • Symptom: The output content is not the knowledge base original text, or the source data is associated but citation content cannot be output. Cause: responseData or detail configuration is not enabled, and complete fields and unique identifiers of the original document are not retained.

How to confirm configurations are correctly set

  • Navigate to the FastGPT knowledge base configuration page to verify whether the value of quoteMaxToken meets the single-item content length requirement of CDN documents.
  • Initiate a test query to check whether the returned result includes original field information from the CDN console and access logs, confirming that responseData and detail configurations are effective.
  • Input the test variable format to verify whether it can correctly associate with the specified CDN data source, confirming that the variable reference rules are adapted.
  • Review the timestamp mark of the cited content to confirm that the detail configuration retains the generation time of the source data, matching the update rhythm of the current configuration.

The values provided are common starting points and should be measured against the target deployment’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.