Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleChanges in 2018.02

The implementation of the LogEventProcessor changed in 2018.02. In order to have more predictable behaviour 2018.02 contains the following changes:

  1. Local logEntries will not trigger tasks owned by remoteMcIds unless they are failover tasks.
  2. Where before tasks could be either a Failover task or not. In 2018.02 this is replaced by "Failover policy". This comes with a new mode called SUSPEND_DUTY_IN_FAILOVER. This is similar to a Failover task except that it is not run by the owning (Duty) Mc when that is in manual failover.

Setting up event-action configurations

The live forecasting system can be scheduled to run workflows as a consequence of a log event generated by the system. This facility is used to enhance forecasting, or to export current forecast data on a new forecast becoming available.

...

Note3: It is recommended to set the interval to 1 second if the action should be executed for every event code (e.g. in the case of sending alert messages), but should be increased if it is not desirable to execute several workflows in a short period (e.g. the case of creating web reports). It also needs the "template task" with the relevant tag scheduled (in suspended mode) as a single/one-off task.

Uploading multiple action configurations

You can upload any number of action configurations in one file if you click on "Upload multiple configurations" button. This feature is available since 2019.02. If you click the checkbox "Default", all uploaded configurations will be set as default. If there are no configurations in the database that share an action ID with the new uploaded configuration, it will be set to default automatically. If the set default checkbox is not checked, the new configurations will appear in the lists of versions under the same action id.

...

Code Block
languagexml
titleExample of a scheduled (and suspended) task in the Admin Interface
<task>
    <taskStatus>S</taskStatus>
    <taskTag>import_hirlam_dim</taskTag>
    <runOnFailOver>false</runOnFailOver>
    <taskProperties>
        <workflowId>Import_DIM_HIRLAM</workflowId>
        <taskSelection>
            <singleTask>
                <time0>2014-01-13T14:56:00.000Z</time0>
            </singleTask>
        </taskSelection>
        <forecastPriority>Normal</forecastPriority>
        <makeForcastCurrent>true</makeForcastCurrent>
        <makeStateCurrent>true</makeStateCurrent>
    </taskProperties>
</task>


Dual MC with failover mode triggers suspended tasks with runOnFailOver from remote MC

Since 2015.01 suspended one-off tasks can be triggered by failover (both manual and automatic failover).

...

3. map different event codes to the different event actions.


Related information on Event-codes

See also event-codes for an overview of the event-codes which also contains a brief list of the most commonly used event codes.