AcademySoftwareFoundation
Configure RQD log root separately from CueGUI
Is your feature request related to a problem? Please describe. If having a lot of machines and machines in multiple locations it can be tricky to depend on mounts for writing out the log files. We have therefore implemented a system with our current render manager where we write log files locally on the render nodes and then use logstash and filebeat from the elastic product suite to transport the logging information back to a central point.
Describe the solution you'd like Be able to configure the root for writing log files separably for the nodes and the main location to read logs from. Preferably also on a per OS level which seems to already be in the works.
Describe alternatives you've considered We thought about recreating the log root mount points on each node but our main root location is on a mount point where we also have project data so it would become a little messy. It would also stop us with the current setup from writing the temp logs to /tmp and relying on linux built in systems to automatically clean them up.
Additional context Great to see the progress OpenCue has been making the last couple of months, year.
Log configuration based on OS has been implemented on https://github.com/AcademySoftwareFoundation/OpenCue/pull/1143
I agree the best solution would be using a log aggregation tool like Loki or logstash to collect the logs and add support for querying the tool from the GUI.
