So how do we borrow flow-monitoring techniques from the Cisco jockeys and apply it to Windows? The idea here is to actively flow all your server events into some sort of a collector, which crunches them, finds patterns, and surfaces the signal from the noise.īig Data for Server Guys is all about letting the computer do what the computer’s good at doing: sifting data, finding patterns, and letting you do what you are good at doing: empowering your organization for tech success.īut we Windows guys have a lot of noise to deal with: Windows instruments just about everything imaginable in the Microsoft kingdom, and the Microsoft kingdom is vast. The problem is that I, just like that IT Guy waiting around for failure, am human, and I’m prone to failure myself.Įnter machine learning or Big Data for Server Guys as I like to think of it.īig Data for Server Guys is a bit like flow monitoring on your switch. I don’t wait upon failure to visit, I seek it out, kick its ass, and prevent it from ever establishing a beachhead in my infrastructure. That’s not a recipe for success in my view. Maybe it’s just my IT scars that bias me, but when I hear a vendor push a “monitoring” solution, I visualize an IT guy sitting in front of his screen, passively watching his monitors & counters, essentially waiting for that green thing over there to turn red.
0 kommentar(er)
