Since macOS Sierra, the Unified log has been an unrivalled source of information about what’s going on in macOS. But access isn’t simple.
Console
A new tailor-made log view shows what’s happened in interactions with the App Store, and can give clues as to the cause of delays and failures.
This update is recommended for all users. It finally addresses problems with using 12-hour and other clocks. It also reveals a more useful version of the log command used to get a log extract.
Sometimes, when you return to examine entries in the log a few hours after they were written, many of them have vanished. How come?
Addresses problems with time formatting, so you should now be able to use Ulbow with a Buddhist calendar, 12-hour clock, set to summer time in Mongolia.
Using EtreCheckPro to identify periods of high CPU, then exploring those in the log using Ulbow. A short and simple workthrough.
Diagnosing a problem on a Mac requires careful observation. In the case of kernel panics, this includes the Panic Log. Otherwise, invaluable information is in the log. If you don’t check the log, your conclusions are likely to be wrong.
No longer do you need to fiddle around pre-installing preference files, and each app can now reset its preferences to the defaul
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.
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.
