I am delighted to announced that my paper providing the first full description of the macOS unified log […]
What do you do when an app accessing your log returns an error, or no results at all? Step through this to check your log system.
When Time Machine backs up an APFS volume, it works quite differently from the way it did on HFS+. Explored here using log entries from Mojave.
It’s actually even easier to browse the unified log and discover what is going wrong with a reproducible problem. Here’s how.
TCC observed loading overrides during startup, and two typical sequences responding to access requests. Useful tips for fixing problems.
Stepping through key points in the log as Mojave 10.14 starts up. Most of the key waypoints are similar to those in High Sierra.
Survey of changes which have occurred since the first version of the unified log in macOS Sierra, with particular emphasis on Mojave.
Natural language parsing, privacy exploring, update investigating, xattr-tweaking, iCloud poking, log browsing: they’re all here for Mojave.
At last: RouteMap performs some analysis on your Signposts, and with the other tools can be used to estimate latency, and look at macOS system performance too.
Doesn’t writing so much to the unified log result in performance penalties? So how can Apple expect us to use the log and Signposts to measure performance?