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.
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?
Blowhole 7 now writes proper Signposts in Mojave, as well as Pseudo-Signposts in Sierra and High Sierra.
At first I thought it was my mistake. Then it looked like a simple error in the interface. But this bug in Mojave’s signposts is more complex. Here’s a workaround.
A new version of Blowhole, the second alpha of RouteMap, and a complete tutorial toolkit to help you get started using log Signposts from Sierra to Mojave.
What do you want from a log browser? Which do you use for the unified log (Sierra and later), or have you given the log up as no longer useful?
Do you want to measure performance or get other info from your app or script? Using Signposts is ideal, and here’s the first glimpse of a new tool to harvest them.
Stepping through the key stages of opening an app in High Sierra. First, a ‘regular’ open, then with the quarantine flag, showing Gatekeeper checks and translocation.
Recommended for Sierra, High Sierra, and particularly Mojave users, this adds a new feature to check whether log privacy is enabled, and gives Mojave version numbers.