Changes since Mojave are subtle. No new fields have been added to the log format, and code-level access is largely undocumented. Console remains at version 1.1.
One solution to running 32-bit apps in Catalina is a VM. Here I assess the performance of Parallels Desktop 15. Is it up to the job?
You can use Signposts readily from scripting languages, shell scripts, even within 3rd party apps, with the aid of these tools.
A simple command tool to write messages to the unified log in Sierra and later. Now signed, hardened and notarized.
Both are now notarized for added security, there is a small bug fixed in Consolation, and updated documentation.
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.
Picking the right time system for the purpose is critical when you want to analyse very short periods. Sometimes it takes time to discover how to juggle with time.
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?