How can you ensure that Apple is aware when something crashes in macOS? Setting this in your preferences, and making a separate Feedback report.
Console
Many Mac users now have a better idea as to whether anything’s amiss at home than in their Mac. Why we need a way to check a Mac’s status.
Time and timestamps, landmark events, activities like clicks, subsystems as predicates, Find, and bar charts – all aids to navigating the log.
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.
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.
The Eclectic Light Company 