xperf recipes

See also: all the recipes and the intro Xperf is the Windows Performance Analyzer, in the Unix terms it would be called a profiler. It can be used to profile both the user-space and in-kernel code. The profiling data is collected in the form of the ETW events in the ETL files (the ETW format…

0

ETW and logging recipes

See also: all the recipes and the intro I have the other more detailed posts on the other aspects of the ETW logging, and here is a pile of assorted links and examples about it. Some very short introduction: The Windows logging has multiple layers. There are the pre-ETW Classic events (that can also be stored…

0

Error handling part 6: ETW logging example

<< Part5 I want to show an example of how to do the error logging through ETW, for the error objects described in the Part 5. It goes against some of the commonly accepted ETW principles but I think that it would out better this way. I think that these commonly accepted ETW principles are…

0

reading the ETW events in PowerShell

When testing or otherwise controlling a service, you need to read its log that gets written in the form of ETW events. There is the basic cmdlet Get-WinEvent that does this but with it you can’t just read the events continuously. Instead you have to keep polling and connecting the new events to the previous…

0

localization both ways

The localization of messages on Windows is done through the MUI files. I.e. aside from mycmd.exe or mylib.dll you get the strings file mycmd.exe.mui or mylib.dll.mui, to be placed next to it in a subdirectory named per the language, like “en-us”, and the system will let you open and get the strings according to the user’s…

0

Collecting the boot-time events over the network.

Today I want to talk about what I actually do at work. I work on the service called “Setup and Boot Event Collector”.  It has been included in the previous Server Technical Previews but disclosed only to the partners. Now it has been officially announced at the Ignite Conference and will be generally available in…

2

Error handling, part 4: error information recap

<<Part 3 Part 5>> Picking up again the series on the error handling, here is the summary of what a good error handling system should contain and do (starting with a recap of the previous posts and then going further): Errors should be nestable, with the high-level information on top and the full details on the bottom. Errors…

0

Error handling, part3: the ETW way

<< Part 2 Part 4>> The Part 2 ended with the summary: In a good error reporting system, the errors should have both the types/codes for the automatic handling and the free-form human-readable strings with the detailed description. However there is one more way, a sort of “middle” way, that is used by the Event Tracing…

0