Recently you added a specific WinEvent for when DNSFilter's roaming agent can't start due to p53 already being bound to another Windows service. This is VERY appreciated as it now allows us to tie a 'fix' automation to this event via our RMM. However, since there is no 'successfully started' eventID raised, we can't rig the same monitor to 'auto heal'. This is minor, but adding this small change would improve our MSP workflow when it comes to dealing with alerts raised due to this.

If implemented, please continue to use the same event source (DNS Agent / DNSFilter), but preferably a distinct eventID. While re-using the same evID would work as long as there is unique event-text we can key from, its less efficient. Thanks!