...
Double click a message to view the message details (see example below). The message can then be saved to file or printed.
Query definition
A query can be defined to select a subset of the messages to be displayed in the Log Browser. The following options are available:
...
| Wiki Markup |
|---|
The display will be updated on the basis of the user defined query upon pressing \[Refresh\].
|
Acknowledging
...
messages
All messages having a level ERROR or FATAL should be can be acknowledged to identify that the message has been seen and appropriate action taken.
Double click the icon to acknowledge a message or click the Acknowledge button. Multiple messages may also be selected and acknowledged in a single action.
...
When all ERROR messages are acknowledged, the status icon in explorer will change to green.
Debug messages
Please note that a System Manager can configure the system to also provide Debug Messages . These are used to log application internal events for system development and management. Typical debug events are the creation of a database connection or exceptions that occurred due to programming or configuration errors. Debug messages are not displayed in the Log Viewer but only written to a log file called log.txt in the regional configuration folder.
1.2 Anchor
Live System Status
The Live System Status tab is used to show the status of the live system. Three lists show the status of the:
...
The status lists show the currently configured master controllers and forecasting shells. From this list a user can see if the systems are Alive or if they are down.
1.3 Anchor
Scheduled Forecasts
The Scheduled Forecasts tab includes a list with all scheduled forecasts together with some information of these forecasts. The following information is included:
...
Please note that not all options are available for all workflows. A user can for example normally not cancel the current forecast and import runs runs scheduled by the super user. Also the status of system management workflows can normally not be changed by a user.
1.4 Anchor
Running Forecasts
The Running Forecasts Tab includes a list with all tasks that are currently running on a Forecasting Shell. The list includes information on the task that is running and the Forecasting Shell it is running on.
From the example below can be seen that the first task is a Rolling Barrel task, running on the Master Controller. The second task is a Riverflow Forecast running on forecasting Shell FSS00.
Wiki Markup
Batch Forecasts
| Wiki Markup |
|---|
1.5 <ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="e869e456-a130-4f2e-b13c-b37ee78cd624"><ac:parameter ac:name="">_Toc172823855</ac:parameter></ac:structured-macro>Batch Forecasts
The Batch Forecast tab will list the forecasts that have been submitted in the Manual Forecast display of a standalone system. You stop all submitted forecast runs by clicking \[Stop\]. |
Anchor
Synchronisation Status
The Synchronisation Status tab provides the status of all synchronisation activities. For each synchronisation activity the following information is provided:
- Activity: identifies the synchronisation activity
- Type: single or continuous. A single type activity is only started after certain manual actions
- Frequency: only applicable for continuous synchronisation activities. The frequency is given in minutes.
- Last Synch Time: the date and time the synchronisation activity has last taken place.
- Status: is either empty or shows 'synchronising', meaning that this activity is now synchronising.
- Progress: shows the number of records of the maximum number of records to synchronise. This field is only used for the activity being synchronised.
1.7 Anchor
Synchronisation Monitor
In the Synchronisation Monitor tab the log messages are shown that are generated by the synchronisation module. These messages will inform the user of synchronisation problems.
Anchor
Import Status
The Import Status tab provides information on the files that were last imported. For each import task the file name of the last imported file is shown including the date and time of the import. Also the number of files that were imported in that task are shown, with the number of failed imports.
1.9