When you press Return, the command will start digging into the log file, and soon start spewing output-possibly a lot of output-to your screen. Unfortunately, the quotes and dashes in the command as tweeted have been prettified (by Twitter?) here it is in raw Terminal form, using our own Moom as an example: log show -predicate 'processImagePath CONTAINS 'Moom'' Or you might be asked to send the log data if you're working with the developer on your issue. This could be useful if you're having troubles with an app and wonder if anything was logged relative to your troubles. That command browses the captured macOS log data and pulls out anything that matches the specified process name. Log show -predicate ‘processImagePath CONTAINS “processname”’ A response from taught me something I didn't know:įor logs from customers of your app on Sierra, use Terminal: But this tip is such a case, as he recently complained about Console and its inability to see old output. It's not often I get to use a tweet by Many Tricks own Peter Maurer as the inspiration for a tip. This article provides a nice overview on interacting with log and predicates to filter the output-there's a lot you can do to help figure out what might be causing a problem.Īnd now, here's the rest of the original post… You can use s for seconds, m for minutes, h for hours, and d for days as arguments to these parameters. This makes it really easy to get just the time slice you need from the overly-long log files. Log - Default: 4, Info: 0, Debug: 0, Error: 0, Fault: 0Īctivity - Create: 0, Transition: 0, Actions: 0

Skipping info and debug messages, pass -info and/or -debug to include. I'm happy to note that this has been resolved in macOS 10.13.4, as log now functions as expected: $ log show -last 20s -predicate 'processImagePath CONTAINS 'Twitter''įiltering the log data using 'processImagePath CONTAINS 'Twitter'' Regardless of what you listed for parameters, you'd always get the entire contents of the log file. When this tip was first posted, it didn't work right: The log command ignored the -start, -end, and -last parameters.

Mac log files console