WindowsSecureContainerExecutor hadoopwinutilsvc is difficult to troubleshoot

The hadoopwinutilsvc logs using the NT service logging infrastructure (ie. Event Viewer). Ideally it should log within the Hadoop logging expected location/format, and be configured via the same parameters.
As native C++ code it cannot leverage directly the log4j (and log4c++ is rather different config etc). I'm thinking that the hadoopwinutilsvc could establish a communication channel with NM itself and log via the NM. We already have the infrastructure in place (RPC, IDL etc).