Main service does not log to the Balena Dashboard Logs Window.

[time-trader]

Bug report

What is the current behavior?

When running gateway, the logger output is not picked up by the logs window on Balena dashboard. The only logs that appear are the supervisor logs about the start / killing of the main service.

What is the expected behavior?

Balena Dashboard Logs window, in theory, should pick up the stdout from the services that are running (As shown here). But filtering logs by "main" service doesn't show any gateway logger output:

As a result, the only way to check the state of the gateway is to download the log via ssh-scp, which is not optimal.

[time-trader]

This is most likely related to the fact that we don't have gateway daemonized (Related #119), and starting it using interactive session instead of main service in the docker image.

Possible courses of action:

• Leave it as it is, download logs with ssh-scp until we have daemonisation.
• Include gateway start --save-local-logs command in the Dockerfile, and interact with gateway only using routine files (no interactive mode capability)
• Install tmux or screen in the docker image. (as a temp. solution)
• Route logs to our own web-socket. (avoid Balena dashboard functionality)
• Add web-api layer (like flask) to control gateway. (probably not worth the effort)