Open
Conversation
Allows to graphically access the system logs.
Member
|
This looks really good! |
Member
|
Yeah actually I wonder if that might be more appropriate in Monitor? It might feel more natural if you're looking to debug/manage/monitor the system that logs could be a part of that process |
Member
|
I'm in favour of putting System Logs in Monitor. I think we will have more freedom there to fully develop this functionality. |
Member
Author
|
Makes sense to me :) If someone wants to do it right now feel free. You should be able to use SystemdLogModel and SystemdLogEntry without modifications. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allows to graphically access the system logs. Based on #337 by @tintou
We currently only show the logs from the current boot.
Allow searching and refreshing.
Load in chunks of 200 entries, load more when scrolled end is reached.
A chunk is split into "subchunks" that are defined by time instead of number of items. We allow 1 ms of sync loading before having to wait for the next idle. We do this until at least the number of items in a chunk (200) are loaded or eof is reached.
Performance should be pretty good but lmk if you run into issues.
Also some feedback for the UI would be appreciated :)
It seems columnview and scrolled window have some issues if there are too many headers visible at once but idk if we can do something about that (except for changing the UI ofc)