That's what we've been doing for 30 years.
Waiting for blinking lights. Waiting for urgent pages. Waiting for the phone to ring.
Infrastructure has monitored us. We've been scheduled and manipulated and frustrated by our own franken-systems that generate billions of signals yet force us to react to noise. While we've been focused on optimizing human-based IT processes we've let machines run amok.
In a world where people talk to people and machines, and machines talk to machines, we're finally able to create new taxonomies and processes that deliver on the unfulfilled promise of operations management: automated service remediation.
We're hard at work making it as easy and reliable to let either machines or people initiate IT processes and tasks. We're on the cusp of a breakthrough that will finally operationalize the closed-loop change management sequence we've been teased with for years:
- Infrastructure events generate alerts which are
- Correlated with known error patterns and
- Associated with CIs in the CMDB which are
- Associated with business services which are
- Automatically maintained by network discovery in topology maps which
- Define business impact and SLAs which
- Are linked with configuration automation tasks which
- Update service health dashboards and
- Automatically restore infrastructure to a desired state when issues are identified which
- Automatically resolve incidents, problems, and changes as issues are remediated which
- Clear associated infrastructure events and
- Create knowledge to improve subsequent remediation behavior.
That's what we're working on in the lab. That's why we've been building out our portfolio of orchestration applications that started with a sophisticated workflow editor which led to deep integrations into Active Directory and PowerShell and has since extended into cloud provisioning, configuration automaton, and event management.
It may sound overly ambitious (we hope it does). It may sound like what others have promised for years (that's why we're hungrier than ever). It may sound hollow or opaque (it won't in a few days).
Students of history should recall that the same criticism was used in 2004 by skeptics casting doubt on the ambitions of a company disrupting another stodgy market suffocated by legacy software. The company was ServiceNow and the market was IT Service Management. We now process 3.4 billion transactions in the cloud monthly and those naysayers are nowhere to be found.
Join us and 6,000 of the most talented technology visionaries on the planet this week in San Francisco at Knowledge14 and learn more about other outlandish goals we set in years past and how we've over-delivered on our promises. Can't join us? Follow the action here.
1 Comment
