Lists the own Master Controller along with all configured remote master-controllers. The status of other MCs will only be updated if synchronization is enabled.
The following data is available in the Master Controllers table.
| element | description |
|---|---|
| MC ID | The master controller McId. Displayed in the header |
| Status | OK when a recent heartbeat is available, failed otherwise. Displayed in the header |
| Pending tasks | Tasks about to be dispatched when FSS become available. |
| Running Tasks | Number of tasks running for the listed master-controller. |
| Last Heartbeat | Timestamp of the last available heartbeat. |
| OC Sessions | Number of sessions that have been updated in the last hour. |
| Software version | The mc release build. Not available for Remote MC. |
| Schema version | The version of the database schema / data update scripts. Not available for remote MC. |
| Database version | Version of the central database software. Not available for remote MC. |
| MCStatus code | Latest status code reported by the Master Controller |
| MCStatus description | Latest status description reported by the Master Controller |
For every FSS Group of a Master Controller the groups status is reported.
The following data is available in the FSS Groups Status table.
| element | description |
|---|---|
| FSS Group Id | ID Of the FSS Group |
| FSS Group Name | Name of the FSS Group |
| Description | Description of the FSS Group |
| Minimum Awake Count | The minimum number of Forecasting Shell Servers that are kept awake in this group. |
| Status | A FSS Group is marked as Failed if the number of awake Forecasting Shell Servers is less than the configured Minimum Awake Count. |
