Read from engine log

[andersmmg]

A nice feature (togglable of course) would be to automatically watch the game log file and append logs to the console output. Some other console addons do this (e.g. Panku) and I wonder if it would fit this console addon? I'd be willing to give implementing it a shot if this fits

[limbonaut]

I'm not sure about this, how useful it actually is. Imagine a tux terminal where syslog is directed right into stdout. We have a log command to peak at the log file, which I found more than enough. It's similar to cat logfile | tail - that's what it does. But if there is a reasonable demand for this, we can add an optional feature, I guess.

[andersmmg]

Yeah honestly after using it a lot more, and finding out about the log command, I think that's a better use for it anyway. Some people may prefer it but I don't know how useful it would be for most people

[limbonaut]

We can keep this open to gauge the interest. Vote 👍 if you need this, but please only do it after checking out the log command and using it for a day or two.

[hrothwell]

can this not be achieved using this? https://docs.godotengine.org/en/stable/tutorials/scripting/logging.html

[andersmmg]

@hrothwell No. If you're wondering what that's for, you can read the documentation you just sent

[hrothwell]

@andersmmg

automatically watch the game log file and append logs to the console output

Does this not accomplish that statement? Might've misunderstood, but this will include all logs from print statements into your limbo console. Configure it as an auto load for it to start picking up all logs. Some other "game log" being referred to here?

extends Node 
class LimboLoggerImpl extends Logger:

	func _log_message(message: String, error: bool) -> void:
		if !error:
			LimboConsole.info(message)
		else:
			LimboConsole.error(message)

	func _log_error(
			function: String,
			file: String,
			line: int,
			code: String,
			rationale: String,
			editor_notify: bool,
			error_type: int,
			script_backtraces: Array[ScriptBacktrace]
	) -> void:
		pass

func _init() -> void:
	OS.add_logger(LimboLoggerImpl.new())

[andersmmg]

The print statements isn't what I wanted, it's everything else. I don't use print statements, I use direct LimboConsole functions since that's what it's for lol

[hrothwell]

ma bad. Interpreted that you were trying to get all godot game logs, which I assume are outputted via print variants only or at least have to go through the logging chain that godot has set up, into LimboConsole so that you can view it as it is happening in real time. Essentially an "always tailing" in the demo above, and could register a command to disable it from that same auto load logger extension

[andersmmg]

Yeah unfortunately not how the logging in Godot works. I've just been using the log command as suggested above, which gets the last several lines of the engines log file which works well enough for when you need it

[hrothwell]

Out of curiosity: what are the exact logs you are looking for? I think I'm still failing to notice how "thats not how logging in godot works" - maybe in < 4.5 versions that was true (seems like Logger class added at that time, sept 2025 after this issue was opened), but looking at the log command it just reads the same file that the Logger should intercept / handle as well according to the docs.