Introduced with Mac OS X, logs became a good way to diagnose a Mac’s problems, using Console. Then in 2016 it all changed, and not for the benefit of administrators or users.
Console
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.
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.
T2M2 is nearly 7 years old, and has already found at least two bugs in Time Machine. Here’s why it’s so hard to get it to work perfectly with each version of macOS.
When was the last time a WWDC session focussed on a utility, or one was singled out in features for the next macOS? It’s time to reimagine the utilities in macOS.
In Sonoma, some healthy Macs are unable to retain complete logs for 24 hours because of the frequency of entries, and even when privacy is removed, some content is censored.
How can you browse a logarchive sent from an iPhone, iPad, or someone else’s Mac? With Ulbow it’s really simple – and it can create logarchives too.
A revamped configuration profile to remove censored private data from log entries, and how to get network diagnostic data too.
The only place you’re likely to find that crucial piece of information about outgoing connections, bugs or problems is the log. How to get started.
The Eclectic Light Company 