The easy part of this is to control the stopping and starting of battor_agent recording using UIforETW. The trickier part is integrating the battor data into an ETW trace.

I created an experimental UIforETW CL that appends (fake) BattOr data such that it shows up at the end of a trace. I can be zoomed and graphed, but it doesn't line up with the real data. It may be possible to improve this technique so that the data is lined up.

https://codereview.appspot.com/326950043

Possible improvement methods would include using the raw ETW APIs to write the UIforETWbattor.etl file with the correct time stamps, or synthesizing a correct file. The timestamps for the individual ETW packets appear to be offsets from some other clock value which I have not found but they are QPC frequency time stamps. FWIW.

Battor is being deprecated so this will never be done.