The forecasting itself doesn't have a scheduler, but you can use Watcher itself do accomplish this. You would have an independent Watch (separate from the Watch used for alerting) that did the following:
obtains the unique forecast_id from the response from the API call in 2)
Possibly stores this forecast_id in a lookup table/index using Watcher's indexing action with the timestamp of when the forecast was run for reference by the other, alerting Watch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.