Under Microsoft Windows, applications, services and drivers often perform IPC (inter-process communication) using named pipes. The problem is, there are no well-known tools to sniff/monitor Windows named pipe communications, making it rather difficult to debug. Pipe Monitor is the missing piece of the puzzle - it lets you see what is flowing through Windows named pipes.
Since in Windows there are many pipes performing communications at the same time, you need to somehow filter only the pipes you are interested in. Pipe Monitor plugins lets you do just that by specifing a pipe name wildcard - you will only see the data flowing through the pipes with matching names.