This first experimental version gets log extracts direct, rather than using the log command tool, and has a SwiftUI front end, but requires macOS 14.6 or later.
Ulbow
macOS logs may only last a few days, or even hours, into the past. Here’s a quick and simple way of browsing the log from weeks, months or even years ago.
Equipping LogUI with controls to get log extracts from arbitrary periods in the past reveals two shortcomings: high memory use, and failure to release that.
Displaying log entries using semantic colour seemed most appropriate using AttributedString, but performs very poorly. The solution is a SwiftUI List view.
Moving away from using the log command tool to obtain log extracts for browsing requires using OSLog. Its API explored and implemented in a demo app.
A strategy for diagnosing problems using the log. How to limit the number of entries shown using appropriate periods and predicates, and more.
There are 3 different ways to access the log, and its entries will be different depending on which way you use. This explains the differences and methods.
Reading the log in macOS isn’t easy, but here ten systems where it’s the only way to discover and address problems, and a bonus 11th.
Apple: “The logs are typically very overwhelming.” So what can the user do to get information about iCloud Drive problems?
When run on Sonoma, these now show log entries from com.apple.FileProvider rather than CloudDocs – a real revelation.
The Eclectic Light Company 