Overview
The system logs can be found in the system log screen in the systems section in the SDX-Cloud. Each system has its own log screen showing the latest logs pushed by the system in real time.
The purpose of this log screen is to give our users the option to quickly get insights about the current state the system is in and if there are any problems.
System logs are only stored for 2 weeks in the past.
General Functionality
The log screen consists of 3 sections:
- Filter Section (on the left)
- Log Section (in the center)
- Log Details Section (on the right, only active if user selected a log)
- Each log entry includes a timestamp and a type.
- Logs are color-coded according to their severity.
- If multiple logs of the same type appear consecutively, they are summarized into one entry showing the number of occurrences.
Walk through the interactive demo available just below to familiarize yourself with the basics of the Logs Screen.
Available Log Types
In the table below, all currently supported log types our systems will log are listed and explained.
Note that the latest version of the SDX-Framework might be required to have access to all log types. To find out if your system has the latest version, please refer to the CHANGELOG section of our helpcenter.
| Type | Severity | Description |
|---|---|---|
| system_online | INFO | A basic ping sent out by the system every 5 minutes indicating the system is online. Also contains the current version of the SDX-Framework. |
| system_started | INFO | A one time ping sent once the SDX-Framework has started. |
| simple_debug | DEBUG | A simple unspecified debug log containing a message. |
| simple_info | INFO | A simple unspecified info log containing a message. |
| simple_warning | WARNING | A simple unspecified warning log containing a message. |
| simple_error | ERROR | A simple unspecified error log containing a message. |
| simple_critical | CRITICAL | A simple unspecified critical log containing a message. |
| sensor_pwr_on | INFO | Triggered if either the user or the autostart turns on the sensor power of the system. |
| sensor_pwr_off | INFO | Triggered if either the user or the autostart turns off the sensor power of the system. |
| project_loaded | INFO | Triggered if a new project is loaded. The ID and name of the Project is also displayed in the SDX-Cloud. |
| autostart_sensor_pwr_on | INFO | NOT INTEGRATED YET - COMING SOON |
| autostart_sensor_pwr_off | INFO | NOT INTEGRATED YET - COMING SOON |
| autostart_project_loaded | INFO | NOT INTEGRATED YET - COMING SOON |
| autostart_start_scan | INFO | NOT INTEGRATED YET - COMING SOON |
| autostart_stop_scan | INFO | NOT INTEGRATED YET - COMING SOON |
| autostart_overwritten | INFO | Triggered if the autostart functionality is overwritten by the user using the SDX-Mate. |
| creating_snapshot | INFO | Triggered if the SDX-Framework is creating a new snapshot. |
| snapshot_part_uploaded | INFO | Triggered if the SDX-Framework successfully uploaded a new part of a new snapshot to the SDX-Cloud. Also displays the part number which has been uploaded and the total number of parts for that snapshot. |
| snapshot_started_processing | INFO |
Triggered if the snapshot is fully uploaded and processing starts on our servers. Note: the snapshot is not yet displayed and available in the SDX-Cloud. |
| snapshot_finished_processing | INFO | Triggered if the snapshot finished processing and is available in the SDX-Cloud. |
| creating_ref_img | INFO | Triggered if a new reference image is created in the SDX-Framework. |
| reference_image_uploaded | INFO | Triggered if a captured reference image got uploaded successfully and is available in the SDX-Cloud. |
| sdx_mate_note_uploaded | INFO | Triggered if a manual captured SDX-Mate Note got successfully uploaded and is available in the SDX-Cloud. |
| high_res_layer_loaded | INFO | Triggered if a new high res layer is loaded via the SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| high_res_layer_unloaded | INFO | Triggered if a currently loaded high res layer is unloaded using the SDX-Mate. |
| high_res_scan_started | INFO | Triggered if capturing for an active high res layer is started. |
| high_res_scan_stopped | INFO | Triggered if capturing for an active high res layer is stopped. |
| high_res_layer_data_uplaoded | INFO | Triggered if data of the captured High-Res layer got successfully uploaded. |
| high_res_layer_processing_started | INFO |
Triggered if the layer is fully uploaded and processing starts on our servers. Note: the layer is not yet displayed and available in the SDX-Cloud. |
| high_res_layer_processing_finished | INFO | Triggered if the layer finished processing and is available in the SDX-Cloud. |
| photo_mode_layer_loaded | INFO | Triggered if a new photo mode layer is loaded via the SDX-Mate. The layer ID is displayed in SDX-Cloud. |
| photo_mode_layer_unloaded | INFO | Triggered if a currently loaded photo mode layer is unloaded using the SDX-Mate. |
| photo_mode_capturing_started | INFO | Triggered if capturing for an active photo mode layer is started. |
| photo_mode_capturing_stopped | INFO | Triggered if capturing for an active photo mode layer is stopped. |
| machine_profile_loaded | INFO | Triggered if a new machine profile is loaded. The machine profile ID is displayed in SDX-Cloud. |
| scan_started | INFO | Triggered if 2.5D scanning is started by the user (SDX-Mate) or by the autostart. |
| scan_stopped | INFO | Triggered if 2.5D scanning is stopped by the user (SDX-Mate) or by the autostart. |
| points_scanned_last_minute | DEBUG |
Periodic message pushed every minute containing the number of points scanned in the last minute. Important: Only pushed if 2.5D scanning is active and the system is inserting data. Not pushed if the system is standing still or does not have an RTK-Fix. |
| camera_set_active | INFO | Triggered if either the user or the autostart sets the cameras to active. |
| camera_set_inactive | INFO | Triggered if either the user or the autostart sets the cameras to inactive. |
| uhf_config | INFO | If a UHF radio is configured and what configuration was applied. |
| ntrip_config | INFO | If NTRIP was configured and what configuration was applied. |
Comments
0 comments
Please sign in to leave a comment.