rapyuta.io provides tabular searchable logs (historical logs) for components of deployment both in the cloud or on a device.
Additionally, for components deployed on the cloud, rapyuta.io offers a to stream (live logs) and follow stdout/stderr.
Add a ROS package to rapyuta.io, which will have a component with cloud runtime. It will publish the ROS topic /telemetry with Maximum QoS as well as print debug information to stdout. Deploy the package on the cloud, and name the deployment as ROS publisher exclusive deployment
To view or analyse the corresponding deployment logs, click Historical Logs.
A tabular listing of historical deployment logs is displayed, where each row consists of a log’s timestamp, its component name and executable name, and its information or message.
The table displays the most recent logs generated in the indicated time range. The widget fetches 500 log entries at a time. If the set of most recent logs contains more than 500 entries and you want to view logs not rendered in the first 500, use the Load Previous Logs In Time Range available at the top of the table. So each time, 500 new logs are fetched. You may use the time range selectors to narrow your search window. As you scroll to the bottom of the table and click Load More Logs, the table will append additional logs that are yielded after now.
You can select a specific component-executable combination to view its corresponding logs. You may also select multiple such combinations. If you select only a component’s name, you will view all the logs generated by all of the executables of that component. If no component is selected, you will view all the logs generated by all of the components that are deployed. For example, the historical logs of only the Talker component are shown below.
You can choose to view logs from within a time range. But, ensure the time slice is neither in the past from the start time of a deployment nor in the future from now. You will be able to view logs up to seven days in the past if a deployment has been running till now.
Moreover, for advanced searching of logs, you will have to write a lucene query in the Advanced Search box.
You may download historical logs of a deployment as a .log file by clicking the download button.
You may want to refresh the logs by clicking the refresh button.
Any errors or exceptions that occur while logs are being generated are redirected to stderr output window, but otherwise, a valid logs output is displayed in stdout window.
To view the corresponding deployment logs in real-time, click Live Logs tab. They are streamed in a terminal-like window and can be useful to view and debug your application in the cloud as it generates new logs. It is similar to the tail -f functionality one is used to in a UNIX terminal console.
To search for a specific phrase in the continuous log stream, enter the phrase inside the Search box. If there is a match, all occurrences of matching patterns of the phrase are highlighted.
You may view logs in the full-screen mode by clicking on the fullscreen button that is located at the top left corner of the terminal-like window.
On the other hand, the corresponding component-executable combination for which deployment logs are currently being streamed is displayed at the top right corner of the window.