Configuring history data for the cloud using History Learn
Exporting cloud histories (that is, pushing history data to the cloud) occurs much like other history exports. A history learn
automatically discovers and adds each history in the station's history database to cloud history. History Learn is strongly
recommended over manual discovery both for speed gains and to avoid inadvertent creation of duplicate history exports. History
Learn does not provide a query filter option.
Prerequisites: Cloud connectivity and communication are already configured for the station. The source station contains histories
to be exported.
- Expand and double-click Histories.The Cloud History Export Manager opens.
- Click History Learn.The Learn Histories configuration window opens.
- Configure as needed any
Device Exclusion Pattern,History Exclusion Pattern,Begin Export Time,and click OK.The Confirm window opens. - To add cloud history exports to all discovered histories, click OK (or you can cancel the export).The history export learn job immediately discovers and adds all histories to the station's history database. This includes certain history types that may not be able to successfully export to
When the next history
Batch Trigger Timeoccurs, the driver sends history records created after theBegin Export Timeto the cloud. It does not send history records recorded prior to the specified time. Once the driver learns the histories and starts to send them to the cloud, it continues to send to the cloud upon each historyBatch Trigger Time. (You configureBatch Trigger Timeon the cloud history device extension.)The driver groups history exports into Cloud History Folders replicating the History Device in which they are contained in the history database.
- To view the Job Log, expand the station’s Services node and double-click JobService.The Job Service Manager opens.
- To view the log, click the chevron (>>) icon to the right of the Cloud History Learn job.The Job Log opens.