Pipes and other output redirection are not supported by LaunchDaemons directly but there are some workarounds.įor example, the following would not work in a LaunchDaemon but will work in a terminal or other shell environment. My solution to add timestamps is very simple but relies on a shell output redirect - aka “pipe” - to have the sed command prepend the date to each output line. Activity Monitor shows you a wealth of information about each process. In Terminal, type man top to see the various options. If you use the command line in Terminal, the top command is useful too. The answer has to do with how LaunchDaemons are loaded without a shell environment. The app /Applications/Utilities/Activity Monitor is what you're looking for.

Note: This script generates a fair bit of data, I recommend you limit your deployment of this to only a few machines. I know Splunk the best so I use it in the examples below, but the energy data is completely portable.

The ProcMon combines the capabilities of two legacy Sysinternals utilities at once FileMon and RegMon. This utility allows you to show how processes access files on disk, registry keys, remote resources, etc. The downside to the new approach is that new commands must now be run as a script the upside is that we now have easy access to timestamped energy impact data that is very easy to parse and chart in any log analytics tool. The Process Monitor (ProcMon) tool is used to track the various processes activity in the Windows operating system. I have spent the last few days improving the collection and analysis features of the original powermetrics command to better support Splunk ingestion.

Macos process monitor