As a TechOps community, we’re awash in buzz words. Most are initially used to establish geek credibility yet quickly become cliches. Take, for example, the term “DevOps”. From its inception as a Twitter hashtag used to promote a meetup in bucolic Ghent, Belgium in 2009, it began to be co-opted months later by ops teams around the world aspiring to manage infrastructure with code.
Every company’s a target, every customer’s at risk. But the now-cliched threat of data breaches from Distributed Denial of Service (DDoS) attacks obscures a bigger threat: outages that impact not just data integrity but also profitability, brand equity, and customer retention.
The volume of attacks is growing and so is the impact of down time. According to Akamai’s most recent State of the Internet report, DDoS attacks are a bigger threat than ever before. “The number of DDoS attacks continued to increase substantially in Q2 2015, more than doubling the number observed in Q2 2014.”
We’re adjusting to the new reality that DevOps is a compelling layover on the journey between legacy ops and self-healing infrastructure. Eliminating the cultural gap between developers and operations, the now-cliched state of IT nirvana called “DevOps”, is by no means the end goal. The goal is reliable system performance and availability without human intervention - the panacea called “NoOps”.
We’re proud to be unveiling a new concept we pioneered in the den that finally moves beyond dashboards as eye candy to a new place where IT analytics can be used to make better ops decisions. It’s called Service Health Analytics and it exposes all data from all monitoring sources in the form of configurable dashboards that can be customized, saved, and shared.
Tsunami detection. Crop dusting. Biohazard monitoring. What may sound like innuendos in the next EL James novel are also fields being revolutionized by quant jocks and smart algorithms. And yet, despite all the innovation, we technorati continue to bastardize the terms “data science”, “machine learning,” and “big data”. They’ve become lazy speak for “we’re not sure what we’re doing so we’ll hand wave cliches until we have real technology and a business model."
Rishi is too humble to be the CIO of a Fortune 100 bank, too busy to be the father of four, too accomplished to blog about ice cream, and too educated to love John Gray. Mostly, he's too unpredictable to fit stereotypes and too passionate about everything he does to do anything at less than full throttle.
I met Rishi this week at the Pacific Crest Global Technology Leadership Forum in Vail where he was presenting and I was lucky to be in the audience. We spent an hour together before his talk that inspired me to rescue Nepalese orphans... and eat more ice cream.
Rishi's been an IT leader since before we called it that. He has helped organizations grow and shrink and grow again. He's more scared about the state of IT today than he has ever been.
Here are excerpts from the discussion...
What is MTTR? Don’t answer with what it stands for or how you use it. The question is more philosophical than literal. For too long we’ve measured operational performance based on the number of minutes it takes to resolve an incident. The almighty trend line slopes down then we gulp milk from the jug of IT inflated ego like NASCAR drivers drunk on Nagios exhaust fumes.
Like the Zen riddle about one hand clapping it’s important to first ask:
In 1792, the New York Stock Exchange opened its doors on Wall Street with five stocks available for trade. Today, more than 2,800 companies list on the NYSE with a combined market value of more than $15 trillion. In 223 years, everything except the name has changed.