Use case or problem
I have strange errors with obsidian. One where the entire UI becomes a blank white screen. Another where the cursor becomes misaligned from the actual input location.
It’s highly likely that this correlates with one or more plugins, but I have no way to interrogate these issues as the electron console becomes inaccessible.
I have no way to direct these issues to either the obsidian devs or the plugin devs.
Note: I have already checked system console logs. There is a error with the obsidian renderer but it’s basically kernel level, so it’s not really usable.
Proposed solution
- Configurable option to enable persistant debug logging of console output.
This has to exist somewhere in electron but don’t know how to enable it.
Related feature forum posts
3 Likes
I thought I saw somewhere the possibility of putting Obsidian in debug logging mode, but can’t seem to find it now (it’s what lead me to this FR). Usually you have different log levels and can increase as needed when there is reason to do so.
Has this been resolved since it was first opened and I missed it or is there some workaround that anyone has found?
I really would like to see more than just the following lines on repeat:
2024-06-24 18:52:15 Checking for update using Github
2024-06-24 18:52:15 Success.
2024-06-24 18:52:15 Latest version is 1.6.3
2024-06-24 18:52:15 App is up to date.
It’s good to know when Obsidian opens a link or finds updates, but I’d like to be able to see error and trace logs. Is this something to do with it being an electron app? Not actually sure what electron apps really are as I’ve only seen that this and Atom were electron apps.
This has come up again as WhiteNoise asked for sync logs in Obsidian Sync repeatedly restoring deleted files - #4 by WhiteNoise, but they are not persistent so can not be provided.
It’s pretty important that an application have good logging for troubleshooting and in my world (sysadmin and support) you NEVER have any applications without it. I’d like to add to this request that sync logs should be included.
If we were following standard coding practices in Linux you would have a single log where things like sync history and application debug information would be written, though some applications will employ multiple log files for different things. It doesn’t need to be extravagant and could just log to a file in .obsidian , or it could store to the OS appropriate locations. In mac that is ~/Library/Logs, /Library/Logs, or /var/log while in Linux it would most likely be in /var/log… not sure about Windows… Windows has always been less stable for good reason. Good practices are not followed there… that’s why the world runs on Linux behind the scenes.
As a workaround there is the Logstravaganza community plugin.
2 Likes