Open JohnTigue opened 1 year ago
For example, here's some Apache2.0 licensed code that tails a log file: logstation, "Tail log files in web browser." The brain_trust just got another compelling feature (if we implement this versus the current AWS console hack).
I bet Docker can already do this for us. There must be a way in Docker to write a container's console messages to a file. Then we can use logstation (see previous comment herein).
This is very valuable for the architecture. We want this sort of functionality inside brain_trust, rather than as is currently with the hack of letting user into the EC2 instances via EC Instance Connect, which is an AWS thing – a leak in the architectural lines.
Since the vast majority of SD users are happy nerds with fancy GPUs on their desktop machine sitting next to them, they can simply look at the informative log message in their textual console. But since brain_trust has the console in the web, this is not viewable remotely.
Sure we are currently hacking up a solution whereby our internal users can jump on the AWS Console and connect to an instance, we have a way of enabling this. But that is not acceptable for a full open source solution.
Perhaps we could tee the console output to a file and then serve that text file up over the web. Dunno, we can punt on this now and simply go with the current hack, which is an architectural leak.