Home

Project Coloma

Event Log Gold

Round One

Hypothesis: There is information in the Event Logs that would help WDG deliver better products - go find gold!

Data was collected with this tool across 100+ machines in June 2016. Visualizations were created in PowerBI desktop and are at \iefs\users\mattgr\Coloma\Analysis.

Data was presented to WDG Core Quality CLIP and recommendations presented:

For now

• Each QD assigns someone to look at the data and enter bugs tagged with #EVENTGOLD
• Continue to collect data with this tool: bug bashes, upgrade fairs, selfhosters
• Build interesting views on the data, mine for gold, enter bugs
• Teams investigate & fix top events: convert to telemetry, fix product bugs, change event reporting...

But better yet

• Move this feature: reporting critical, error, and warning events via telemetry to a feature team now
• Start counting via telemetry: report aggregated identifiable event counts on machines
• Teams need to scrub legacy event calls: no more ::ReportEvent
• Monitor these events with each flight and servicing release
• Build interesting views on the data, mine for gold, enter bugs
• Build a map of Event Log Source -> Team
• Teams investigate & fix top events: convert to telemetry, fix product bugs, change event reporting...

Notes

• With each new flight, we nuke the logs
• There is PII in the details
• Events don't include module name or version
• Events get to the log many ways
• Event are organized by Source, which is just a string field (could be anything)
• Many messages are similar and could be grouped by InstanceID or other fields