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.
log
Reading the log in macOS isn’t easy, but here ten systems where it’s the only way to discover and address problems, and a bonus 11th.
Where would you find a 7C3457EF-0000-11AA-AA11-00306543ECAC? How UUIDs have taken over to identify so much, and how to generate your own.
Have noticed brief periods of high CPU for universalaccessd in Sonoma? Do you know what com.apple.axserver is and why it can’t be found? Can you help with this puzzle?
How local files retain their extended attributes and versions when moved to iCloud Drive, but they’re not available to other Macs. Sparse files and storage economy as well.
Further insights into how iCloud Drive works using a folder of 20 small files. These reveal system limits including chunk size and throttling.
Apple: “The logs are typically very overwhelming.” So what can the user do to get information about iCloud Drive problems?
When run on Sonoma, these now show log entries from com.apple.FileProvider rather than CloudDocs – a real revelation.
How Sonoma’s new FileProvider mechanism is reflected in log entries for the upload of a test file to iCloud Drive.
You can disable its checks of scheduling, and it better analyses Speed in Big Sur, and backups in macOS 11-14.
The Eclectic Light Company 