Summary
System Logs in SDX-Cloud help you review recent system activity, status messages, and configuration events for each system. Use this screen to confirm whether a system is online, understand recent actions, and identify warnings or errors.
Introduction
Each system in SDX-Cloud has its own System Logs screen. The log stream updates in near real time and helps you review system status, scanning activity, uploads, and configuration events from the connected hardware.
Note
System logs are stored for 2 weeks.
System logs are stored for 2 weeks.
Prerequisites
- You can sign in to SDX-Cloud.
- You have access to the relevant system in the Systems section.
- The system has recently sent log data.
- Some log types only appear when the related workflow, hardware, or traffic is active.
- For the newest log types, the system should run a version of SDX-Framework that supports them.
Step-by-step instructions
1. Open the System Logs screen
- Open SDX-Cloud.
- Go to the Systems section.
- Select the system you want to review.
- Open the System Logs screen for that system.
You should now see the latest log entries for the selected system.
2. Use the three main areas of the screen
- Use the Filter section on the left to narrow the log list.
- Review the Log section in the center to scan recent entries.
- Select a log entry to open the Log Details section on the right.
The details area is only active after you select a log entry.
3. Interpret the log list
- Check the timestamp and type of each entry.
- Use the severity to judge urgency. DEBUG and INFO entries help you trace normal activity, while WARNING, ERROR, and CRITICAL entries point to issues that may need action.
- If the same log type appears several times in a row, review the grouped counter because SDX-Cloud combines consecutive identical log types into one entry.
4. Reference: available log types
The following log types are available. Some entries only appear when the related workflow, hardware, or traffic is active.
| Type | Severity | Description |
|---|---|---|
| system_online | INFO | A periodic ping sent every 5 minutes to show that the system is online. It also includes the installed SDX-Framework version. |
| system_started | INFO | A one-time entry that shows the SDX-Framework has started. |
| basic_debug | DEBUG | A basic unspecified debug log containing a message. |
| basic_info | INFO | A basic unspecified info log containing a message. |
| basic_warning | WARNING | A basic unspecified warning log containing a message. |
| basic_error | ERROR | A basic unspecified error log containing a message. |
| basic_critical | CRITICAL | A basic unspecified critical log containing a message. |
| sensor_pwr_on | INFO | Shows that the sensor power was turned on by the user or by autostart. |
| sensor_pwr_off | INFO | Shows that the sensor power was turned off by the user or by autostart. |
| project_loaded | INFO | Shows that a new project was loaded. The project ID and project name are displayed in SDX-Cloud. |
| autostart_overwritten | INFO | Shows that the user overwrote the autostart behavior by using SDX-Mate. |
| creating_snapshot | INFO | Shows that SDX-Framework is creating a new snapshot. |
| snapshot_part_uploaded | INFO | Shows that a new part of a snapshot was uploaded to SDX-Cloud. The log also includes the uploaded part number and the total number of parts for that snapshot. |
| snapshot_started_processing | INFO | Shows that the snapshot upload is complete and processing has started. The snapshot is not yet available in SDX-Cloud at this stage. |
| snapshot_finished_processing | INFO | Shows that the snapshot finished processing and is available in SDX-Cloud. |
| creating_ref_img | INFO | Shows that a new reference image is being created in SDX-Framework. |
| reference_image_uploaded | INFO | Shows that a captured reference image was uploaded successfully and is available in SDX-Cloud. |
| sdx_mate_note_uploaded | INFO | Shows that a manually captured SDX-Mate note was uploaded successfully and is available in SDX-Cloud. |
| high_res_layer_loaded | INFO | Shows that a new high-resolution layer was loaded by using SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| high_res_layer_unloaded | INFO | Shows that a loaded high-resolution layer was unloaded by using SDX-Mate. |
| high_res_scan_started | INFO | Shows that capture for an active high-resolution layer started. |
| high_res_scan_stopped | INFO | Shows that capture for an active high-resolution layer stopped. |
| high_res_layer_data_uplaoded | INFO | Shows that the captured data for a high-resolution layer was uploaded successfully. |
| high_res_layer_processing_started | INFO | Shows that the layer upload is complete and processing has started. The layer is not yet available in SDX-Cloud at this stage. |
| high_res_layer_processing_finished | INFO | Shows that the layer finished processing and is available in SDX-Cloud. |
| photo_mode_layer_loaded | INFO | Shows that a new photo mode layer was loaded by using SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| photo_mode_layer_unloaded | INFO | Shows that a loaded photo mode layer was unloaded by using SDX-Mate. |
| photo_mode_capturing_started | INFO | Shows that capture for an active photo mode layer started. |
| photo_mode_capturing_stopped | INFO | Shows that capture for an active photo mode layer stopped. |
| machine_profile_loaded | INFO | Shows that a new machine profile was loaded. The machine profile ID is displayed in SDX-Cloud. |
| scan_started | INFO | Shows that 2.5D scanning started, either by the user in SDX-Mate or by autostart. |
| scan_stopped | INFO | Shows that 2.5D scanning stopped, either by the user in SDX-Mate or by autostart. |
| points_scanned_last_minute | DEBUG | A periodic entry sent every minute with the number of points scanned during the last minute. It is only logged while 2.5D scanning is active and the system is inserting data. It is not logged when the system is standing still or does not have an RTK fix. |
| radio_bytes_per_minute | DEBUG | Shows the traffic volume between the radio, often used for UHF, and the GNSS receiver. This log type is only logged when there is traffic. |
| camera_set_active | INFO | Shows that the cameras were set to active by the user or by autostart. |
| camera_set_inactive | INFO | Shows that the cameras were set to inactive by the user or by autostart. |
| uhf_config | INFO | Shows whether a UHF radio was configured and which configuration was applied. |
| config_freewave | INFO | Shows that a 900 MHz FreeWave configuration was applied on the radio. This log type is only relevant for systems that are compatible with UHF. |
| ntrip_config | INFO | Shows whether NTRIP was configured and which configuration was applied. |
Comments
0 comments
Please sign in to leave a comment.