What the Data for This Category Looks Like
Data sources for energy storage yield rate daily reports include public spot trading data from domestic power trading centers, and charge-discharge records from local SCADA systems of energy storage power stations. The update cadence is T+1 daily: a summary document for the previous calendar day is generated each day. The document uses a structured table format, with each row corresponding to a single energy storage power station. Fields include: unique power station identifier, total daily charge-discharge volume, transaction settlement electricity price, daily operation and maintenance expenses, government subsidy amount, daily net profit. Units: none (for identifier), megawatt-hours, yuan/megawatt-hour, yuan, yuan, yuan.
Constraints on Conversation Logs and Auditing
The structured nature of energy storage yield rate daily reports requires conversation logs to bind the power station identifier and query date. Without this binding, audit trails cannot associate conversation requests with corresponding business data. The T+1 daily update cadence requires conversation logs to be split and archived by calendar day. This prevents cross-day data confusion. The multi-field business attributes require audit logs to retain only necessary business fields. Filtering out irrelevant content improves audit efficiency. The diversity of data sources requires logs to record the source node of each data call. This facilitates tracing of abnormal data. Compliance audit requirements require conversation logs to retain a sufficiently long period. This ensures traceability of business queries and data calls for any time period.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
logRetentionDays | 365 days | Energy storage yield rate daily reports are long-term data required for business compliance audits, and must be retained for at least one full fiscal year cycle |
userSessionExpire | 86400 seconds | Divide conversation sessions by calendar day, matching the daily report update cycle, to avoid cross-day sessions mixing energy storage power station data from different dates |
auditFieldWhitelist | station ID, daily charge-discharge volume, transaction electricity price, net profit, data source | Retain only energy storage business fields required for audits, filter out irrelevant log content to improve audit efficiency |
externalDataSyncInterval | 86400 seconds | Align with the T+1 update cadence of energy storage daily reports, synchronize the latest transaction and power station data to the log association database daily |
apiRequestLogSampling | 100% | Compliance audits require complete recording of all API requests, to ensure no missing conversation and data call records |
sessionTagEnable | Enabled | Add power station ID and query date tags to each session, to facilitate retrieval of audit logs by business dimension |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis, and it is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- Phenomenon: An error
cannot fetch internal urlis returned when calling the energy storage daily report knowledge base. The backend log prompts that the internal URL cannot be obtained. Cause: The internal API address of the energy storage data source has not been added to FastGPT's internal URL trust list. The security verification added in version 4.9.0 intercepted legitimate internal data requests. - Phenomenon: Conversation logs for multiple business users cannot be distinguished, making it impossible to locate specific user query records during audits. Cause: The
X-User-Idrequest header parameter was not carried in API-connected requests, and the session user binding configuration was not enabled. - Phenomenon: Conversation logs include internal execution logs of specified reply plugins, resulting in redundant audit content. Cause: Historical memory filtering rules were not configured, and non-business conversation content from plugin execution was not ignored.
How to Confirm Configuration Is Complete
- Initiate a conversation request carrying a power station identifier and query date. Check whether the session details display the corresponding business tags, to confirm that the session tag configuration is effective.
- Call the API interface using different user identifiers. Check whether the log system stores session records classified by user identifier, to confirm that the user binding configuration is effective.
- View the audit log panel. Check that only the configured business fields are displayed, to confirm that the field whitelist configuration is effective.
- Manually trigger the energy storage data synchronization task. Check whether the log records the synchronization status, to confirm that the synchronization interval configuration matches the business update cadence.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.