Module Integration Guides
Linux
Push application logs
5 min
using bytebeam cloud, it is possible to view the logs of the device this guide assumes your device is running using systemd and logs are being pushed to journald this guide will show you how to view journald logs on the cloud create a stream called " logs ", with the following parameters now , we need to create a " logs " dashboard create logs dashboard go to the " dashboards " section of bytebeam cloud and select " create dashboard " give the title " logs " and select the dashboard type as " device dashboard " click on submit the created dashboard should be visible now click on the " logs " dashboard and select the device for which you want to see the logs create a new panel select the "logs" panel give the appropriate title and select the " logs " option from the " table " drop down menu click on submit to enable the logging feature on the device, the following lines are to be added to the config toml file \[logging] tags=\["sshd", "systemd"] stream size=1 min level=7 restart uplink the logs should be visible on the cloud now update log config from the cloud with the help of config toml file, we can filter the logs related to a particular process in this example, we see logs related to ssh it is possible to change the logging configuration, from the cloud as well to do that, we need to create a new action type called " journalctl config " follow the guide on creating new action types docid\ qpcsie hkxdpje0aj8z1j " journalctl config " is internally handled by uplink itself it manages log level and tags click on submit on the device management section, the " journalctl config " action should be visible select the device and click on " journalctl config " you will be prompted to create a json file to see systemd logs also, use the following json we can also choose the desired log level click on yes this will trigger " journalctl config " action to view the logs, select the device and click on " device dashboards " select "logs" dashboard now, you should be able to see the logs of sshd and systemd as well