It’s pretty obvious that a new technology (or a new application of an old technology) is white hot when every vendor under the sun starts to co-opt the technology in its marketing material. Last year saw almost every technology vendor deciding that they were now delivering “big data analytical insights” […]

Ben Kepes

Ben Kepes is a technology evangelist, an investor, a commentator and a business adviser. Ben covers the convergence of technology, mobile, ubiquity and agility, all enabled by the Cloud. His areas of interest extend to enterprise software, software integration, financial/accounting software, platforms and infrastructure as well as articulating technology simply for everyday users.

1 Comment
  • Ben – I love this article. Thanks for getting past the hyperbole and pointing out the value of automatic detection and collaborative situation aware support for OpenStack and Docker served environments.

    Our view of the world is that the folks supporting the underlay (OpenStack infrastructure) and Containers are working in a disassociated manner with their ‘overlay’ tenants (the DevOps oriented Apps teams).

    What we’re doing at Moogsoft is (a) using a bunch of real-time Event driven analytics techniques, some unsupervised and some supervised, to detect anomalous behavior earlier than has been possible with other analytics approaches in order to ‘push notify’ the appropriate stakeholders that there is an issue they should be aware of, then (b), use the results of the analytics (which is a cluster of ‘information ally related’ Event messages) to bring together the stakeholders in a collaborative virtual incident room.

    The point here is that traditional ‘linear’ support processes where operations assess a sea of red alerts or assess real time performance dashboards…or receive a call from the users(!) in domain based silos, situationally isolated from each other, and where, if the first level responder cannot resolve the issue, a trouble ticket is created – resulting in a large volume of tickets possibly all related to the same issue with no one aware of their relationship to each other.

    Incident.MOOG ensures that the stakeholders know their relationship with the issue – are they responsible for the causal indicators of the issue or are they suffering the consequences of the issue.

    The thing that we think is cool is that those who need to react to resolve the issue can contextualise and action earlier whereas, those who are impacted can enact their evasive action or continuity…even in the case of service providers, notify their tenants proactively.

    I look forward to engaging in more conversation about this. We all need to begin to ensure that ITIL catches up with modern IT provisioning platforms and their needs from a service assurance ‘collaborative process’ perspective.

    Again, thanks for the thoughts in the article.

    Mike Silvey, Cofounder, Moogsoft.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.