openremote
Docker OpenRemote-wide logging to Manager Syslog port
This PR introduces the feature of OpenRemote-wide logging from all containers into the manager's SyslogService. This would allow for users to have an easier logging experience and allow for easier debugging/monitoring of OpenRemote as a whole. If I get this to work, I would optimally have that port serve as a Syslog server itself, allowing for sending all those logs outside of the container (to some other monitoring server).
@richturner I'm having an issue within UDPStringServer specifically from AbstractTCPServer, starting somewhere in line 83. When debugging, I send a message using echo "test" | nc -u -w1 localhost 1514 -v, and I can see that I am hitting that line using a breakpoint, but the message does not seem to propagate to my messageConsumer. I'd appreciate any pointers, but I assume it's still my mistake, since it's dealing with low-level stuff. Thanks!
I like the idea of being able to view all container logs within the manager but I have concerns about turning the manager into a syslog server as the manager is already doing too much.
The syslog service is also a considerable burden on the manager and the DB and I'd like to see a more standalone solution to logging and ability to read logs from the UI.
I like the idea of being able to view all container logs within the manager but I have concerns about turning the manager into a syslog server as the manager is already doing too much.
The syslog service is also a considerable burden on the manager and the DB and I'd like to see a more standalone solution to logging and ability to read logs from the UI.
The main use-case for this would be to allow users (mainly the superuser) to view all container logs through the UI/maybe programmatically. This would allow users to debug issues without having to SSH into the instance and view the container logs. I'd personally love to have this with my fleet endeavours, since I have logging set up in a way that I can understand the payloads that come in from the devices. It would be an interim solution without adding new docker containers/services like elastisearch and Kibana to do this sort of thing, and a lot of the infrastructure for it is already there.