Event-Driven Automation with PowerShell: Listening for Change, Acting in Real Time
summary
Shows concrete code and outcomes: PowerShell uses Register-CimIndication/Register-ObjectEvent and .NET watchers to trigger handlers that ran instantly in demos (process start, forwarded event log entry via Windows Event Forwarding using WinRM and XPath filters, and a file system watcher), combined into one event queue. Counts: multiple demos showed event detection and handler execution, cleanup required (unregister/dispose), traps for memory leaks, debounce and validate sources, and handing off work to an orchestrator like OpCon.
AI-written summary · about
chapters (21)
- 0:00Event-driven automation intro
- 2:51Introduction
- 3:55Why event-driven matters in DevOps
- 5:43PowerShell event architecture
- 8:17WMI vs CIM in events
- 10:35Demo: Monitor process starts with CIM
- 14:31Instant automation reactions
- 14:53Windows Event Forwarding explained
- 19:20Setting up WEF demos
- 20:48Demo: React to forwarded logs
- 23:47Exploring .NET event sources
- 26:18Demo: File system change detection
- 29:58Real-world use cases
- 32:13DevOps orchestration integration
- 34:19Reliability and performance tips
- 35:43Cleanup to prevent leaks
- 36:32Security and compliance
- 37:13Unified event pipelines
- 39:29Demo: Fuse multiple signals
- 41:17Key takeaways and resources
- 43:05Q&A on WEF and Azure
related talks
43mAdvanced PowerShell Eventing Scripting Techniques
46mParsing Event Logs for FREE
43mHow to Tame the Event Log Beast
25mCreating Automation with APIs and PowerShell
49mMonitoring Using PowerShell
01h 11mWorkshop - Automating for DevOps
34mWhip Your Scripts into Shape: Optimizing PowerShell for Speed
01h 34mM365 Automation using PowerShell in Azure Function