It would be much easier if the log contained entries detailing the loading of extensions. Instead, there are long gaps. This explores how you can use those in diagnosing problems.
log
Use the log show command, Ulbow or Consolation to browse your M1 Mac booting, and they can fail to show tens of thousands of log entries. How to work around this bug in 11.1.
When does an M1 Mac validate its Sealed System Volume? Who designed its display interface? How soon does Find My Mac launch? So many answers found in the log.
Time has changed in M1 Macs, with the Mach clock ticking every 41.67 nanoseconds. This affects all log entries too, and works differently in Rosetta.
Adds a new log view of background task scheduling and dispatch, greatly improves volume info, and fixes a rare crash.
The more you look at changes to Mach Absolute Time coming in Apple Silicon Macs, the more messy they become, largely because the docs are so incomplete.
How long does it take to write a Signpost to the unified log? Measuring this is essential if you’re going to use them to measure performance.
Makes it easy to write, harvest and analyse Signposts in the log to measure performance. Important fix for Apple Silicon too.
Since we switched to Intel Macs, Mach precision time has ticked away in nanoseconds. That’s won’t be true in Apple Silicon Macs, and could have strange results.
How you can write entries in the unified log which are informative, easily retrieved, and extremely simple.
The Eclectic Light Company 