v0.4.0: Schedule Configuring Update

This release adds options to fully configure the history management of your application. Previously, all functions of HistoryManager had at most a "tick_rate" specified in minutes, which is excessive for some applications receiving data several times a day. Similarly, the archivation age could only be specified in days, where some applications may need to remove data much sooner.

The new configuration format is fully documented here and the specifics of cron expressions here.

To use the update, please update your history_manager.yml configuration file - this is how the default config looks now:

aggregation_schedule:  
  minute: "*/10"  

datapoint_cleaning_schedule:  
  minute: "*/30"

snapshot_cleaning:
  schedule: {minute: "15,45"}  
  older_than: 7d  

datapoint_archivation:
  schedule: {hour: 2, minute: 0}  
  older_than: 7d  
  archive_dir: "data/datapoints/"