Log output to stderr and let journald handle the logging and log rotation

[reubenmiller]

It looks like a python log file handler is being used to redirect the log output. Since this is being designed for a systemd based OS (a requirement enforced by the Sony IMX lib dependencies), then the service should use the standard journald logging mechanism as it reduce the python code and it ensures that logs are output to a central location (journald).

Note: Yes currently thin-edge.io does not support the retrieval of journald logs, however we're currently working on that.

Example

• the systemd service definition is ignore stdout and stderr
  

  vision-ai-thinedge-plugin/rpi-vision-ai-processor/usr/lib/systemd/system/rpi-vision-ai-processor.service

  Line 13 in a892ded

  StandardOutput=null

• python log configuration can be removed afterwards, rpi_vision_ai_processor_logging.conf, vision_ai_mapper_logging.conf

[vdiwe]

Updated Journal to handle standard output os systemd - 3d3379d

[reubenmiller]

Generally you shouldn't need to explicitly set the StandardOutput and StandardError values in the service as the defaults should be fine. However the file logging is still used (which was the main point of the ticket).

[vdiwe]

Hi @reubenmiller I have checked internally, right now users of this service are familiar with file based logs for debugging or checking something, So we would like to keep the file based approach for now. May be in later version we would change that.

[reubenmiller]

ok, but then we can leave this ticket open in the meantime.