Operations | Monitoring | ITSM | DevOps | Cloud

Windows event logs can provide valuable insight into day-to-day operations and potential security issues. But making sense of that data—and getting it to the right place without overloading your systems or driving up costs—takes some planning. Bindplane helps with this by providing a flexible way to collect, process, and route Windows events. It’s designed to support security and compliance needs without adding unnecessary complexity.

Almost two years ago I wrote the first installment of what was supposed to be a 3 part series on Serverless Monitoring. Parts two and three never materialized. Today, however, I am revisiting that original idea and expanding upon it. I hope to succeed this time in making it a full three-part series. For this first installment (Revisited), I will again work with Google Cloud Run to monitor MongoDB Atlas.

OpenTelemetry is officially the second-largest project in the CNCF, only behind Kubernetes. This year we had 13.000 engineers, maintainers, and vendors show up in London.

Instead of deploying a patchwork of proprietary agents for every platform, a telemetry pipeline lets you route your data through a single, consistent layer—and send it to any backend you choose. Flexibility, achieved. But there’s a catch. If your pipeline is proprietary, you’ve only shifted the lock-in left. Sure, you can now add or swap destinations freely—but you’re still deeply dependent on a vendor in the middle of your data flow.