By default, device logs are not collected until you explicitly subscribe to a ROS topic in case of ROS deployments.
Before viewing device logs, it is necessary to have the ROS Master up and running. Add a ROS Publisher package that has a Talker component with device runtime. It publishes /telemetry ROS topic with High QoS.
/telemetryis subscribed. Ensure the status of the subscribed topic(s) is Subscribed and is highlighted in green.
Once you subscribe to a topic, the device logs are displayed in the logging area (a terminal-like window).
Initially, you will see the latest 500 logs in the logging area. As you scroll up to the top of the terminal window, the previous 500 logs are displayed. You may continue scrolling up till all the logs are exhausted.
To get updated logs, scroll down to the bottom of the logging area, and then click Get recent logs.
To switch between the topics, click the drop-down list (at the top-left corner
of the logging area) and select one of the subscribed topics. A tick mark against the topic
/telemetry indicates that you are currently viewing the logs belonging to
You can search the logs for matching phrases using the Search bar. All occurrences of a match are highlighted.
If you prefer to view the timestamp of every log displayed in the logging area, select Show timestamps checkbox.
Topics such as
/rosout_agg are already available for a
You can upload logs collected from a device (like dmesg, journalctl, rosbags etc.) to rapyuta.io. It lets you:
The log data can be text, images, or videos. You can upload log files by clicking on the Upload button, which is found on the device’s Manage tab.
A list of statuses indicates the progress of an ongoing upload. They are:
There are certain parameters to take care of while uploading a log file from a device to rapyuta.io
When providing the absolute path of the log file, ensure it does not end with a backslash. Hence, folders are not supported. You are only allowed to upload a single log file at a time.
Sometimes constrained resources can limit a device’s ability to execute tasks while uploading logs. For instance, a significant amount of network bandwidth is consumed while uploading enormous log data, which can affect the execution of other high priority tasks on the device. In this case, rapyuta.io lets you tune network bandwidth based on the device and its environment limitations. It lets you upload log files without interfering with task execution. You can choose the upload rate value in Mega bytes, or Giga bytes.
Select the purge option to remove a log file from a device after successfully uploading it to the cloud storage.
Select the override option to replace an existing log file with a new log file with the same name.
Metadata lets you create static tags for log files while uploading.
After successfully uploading the log file, a summary of the log details is shown. It includes information like the name of the log file, its size, creator and creation time among other details. It lets you download the log file, and also share it publicly outside rapyuta.io platform by creating direct links.
Sharing a log file requires you to generate a publicly accessible direct link (URL) by setting an expiration time for the link. The expiration time defines the duration for which the link will be valid. Multiple publicly accessible direct links can be generated with different expiration times.
A direct link is valid as long as a log file is not deleted even if the device is deleted or is in a failed state.
The private URL is a permanent URL of a log file. It provides access to the log file to rapyuta.io users in a project.
You may also: