The system reports provide a detailed insight into the events and status of the system. They are particularly suitable for troubleshooting, problem analysis, and monitoring system processes.
The system reports can be opened via the context menu under Antcas Control System Reports.
Notes: The system reports are only available from Core 2 or higher.
When opening the monitor, the last 100 system events are displayed automatically. Subsequently, new events are added in real time. If the connection to the server is temporarily interrupted, the entries created during this time are automatically reloaded once the connection is restored.
In the menu under Timeline, all recorded events are available. The entries are categorized by boot processes and chronologically by date, enabling easy navigation through older logs.
Note: If the server is reset or the system log is deleted, the previous entries are no longer available.
As in other areas of Antcas Control, events can be searched using the filter. Multiple lines can be marked simultaneously and then copied to the clipboard.
Displays the time at which the event was recorded by the system.
Displays the service that generated the event. All Antcas services start with the prefix antcas. The main service is named exclusively antcas, while other services are supplemented by corresponding suffixes. Since the system reports are primarily intended for diagnostic and debugging purposes, the internal service names are displayed unchanged.
The process ID (PID) identifies the process that generated the event. When a service is restarted, it receives a new process ID. This makes it possible to determine whether a service has been restarted in the meantime.
Each event is assigned one of seven priority levels:
The priorities are highlighted in color for better recognition.
Contains the actual description of the event. If a message consists of multiple lines, each line is displayed as a separate event.
Displays the time at which the corresponding boot process was started.
Not every message marked as an error indicates a critical fault. The system reports contain all outputs of the system services and are primarily used for diagnosis and analysis.
Antcas Control continuously monitors the status of the system and automatically informs about critical errors. If such messages occur, the system reports can provide valuable clues to the cause.
Under normal operation, the monitor only occasionally contains new entries, for example through time-controlled tasks or regular system activities. A larger number of recurring warnings or errors, on the other hand, may indicate a malfunction and should be investigated more closely.
Tip: The timeline can be exported as a CSV file and used for further analysis or to pass on to support.