Back to Blog

Procmon for Mac: Choose a Tool for the Events You Need

Looking for Procmon on Mac? Compare Mac Monitor, fs_usage, lsof, Activity Monitor, and ProcXray for event capture, open files, and resource inspection.

On this page

If you want Procmon-style file or process events on Mac, start with an event capture tool such as Mac Monitor, or fs_usage for a focused file-system investigation. If you need CPU, memory, open files, or process details, Activity Monitor, lsof, and ProcXray answer different parts of that task.

This guide is written by the ProcXray team. ProcXray is a process inspector and resource monitor; it is not a replacement for a complete event trace.

Is there a Microsoft Procmon for macOS?

Microsoft’s Process Monitor page describes the Windows tool and links a separate Linux project. It does not list a macOS download. Procmon captures Windows file-system, Registry, and process/thread activity.

Microsoft also has a Process Explorer for Mac project. Process Explorer and Process Monitor are different tools: the existence of that Mac project does not establish a Mac Procmon release. See our Process Explorer guide for that separate search intent.

Choose by the question you need to answer

Your questionStarting pointWhat you get
Which file operations occur during a failure?fs_usageA live stream of file-system activity
Which process or file events occur during a reproduction?Mac MonitorEndpoint Security event collection and analysis
Which files or sockets are open now?lsof or ProcXrayA view of currently observable resources
Which process is consuming CPU or memory?Activity Monitor or ProcXrayResource readings for triage
What arguments, environment, and parent does this process have?ProcXray and psProcess context for a known target

An open-file list answers a state question. An event stream answers what happened during capture. A CPU chart answers how resource use changed. Choose the evidence before choosing the interface.

Mac Monitor for event investigation

Mac Monitor collects macOS Endpoint Security events and presents them for investigation. Its documented scope includes process and file events, making it a candidate when you want to reproduce behavior and examine the resulting sequence.

Follow the project’s current installation instructions. They require approving its system extension and granting Full Disk Access to its security extension. Configure capture before reproducing your issue, narrow the events to the target, and stop after the relevant window. Verify the event types and filters needed for your investigation rather than assuming parity with every Windows Procmon operation.

This is a different setup from opening a resource monitor for a quick CPU check. We have not benchmarked the tools against each other.

fs_usage for a short file-system capture

For a known process, a bounded Terminal capture can be enough. Replace 1234 with its current PID:

sudo fs_usage -w -f filesys -t 10 1234

This requests wide output, filters to file-system activity, and stops after ten seconds. Reproduce the relevant action while capture is active. sudo requests administrator authentication. Check man fs_usage on your Mac for supported options and any access restrictions.

Apple’s I/O monitoring guide documents process filtering and timed captures. Use the output to investigate repeated file operations around your symptom; it does not prove that every displayed operation caused the failure.

lsof and ProcXray for current process state

Use lsof to find an open file or listener without starting an event recording. Our port investigation guide gives commands for TCP listeners and per-process sockets.

In ProcXray, select the PID and inspect Open Files, Connections, Command Line, and ENV. Follow its parent relationship or compare its launch environment with a working run. These views help you decide what to investigate next; they do not preserve every open, close, read, or write operation.

For ongoing resource symptoms, the menu bar dashboard and Watch alerts can help you notice a condition. A Watch start/exit notification still depends on observation and can miss a process that lives entirely between samples.

Move from triage to capture

Start by identifying a reproducible action and the target process. Use resource readings or process details to narrow the question. Then start an event capture, reproduce the action once, and compare the relevant events with the application’s error or log.

A Windows Procmon filter based on a Registry path or Windows operation name does not transfer directly to this workflow. Recreate the question using the Mac tool’s event types and filters. Keep timestamps, target identity, and reproduction steps together so another person can evaluate the evidence.

If you only need a routine CPU or memory check, start with the built-in tool; our Activity Monitor comparison explains when deeper inspection is useful.

Try ProcXray for process inspection and resource monitoring →