Why CloudMunch 2.0: ChatOps

Having come out of the long product development hibernation, I am now in the out talking about CloudMunch 2.0 with some of the prospects and customers. One thing that I keep getting is, Why is this a significant version for you? Why not 1.3 or 1.4, why is it a 2.0? I have given off the cuff answers in some occasions, but then thought that I need to write specifically, "Why this version stands as a significantly different version?". So here goes a series.

The first and foremost reason is ChatOps. We have re-written the platform to give "Self-service", a new dimension via ChatOps. When we were thinking of re-writing the core, we had said, we need to build the platform to natively work with Chat systems. We should be able to plug any communication via ChatOps. So our idea of bringing "self-service" was to bring self service to our end users, our business, our developers and our ops teams. 

I expand each of these at my blog here

What we are finding with this approach is that all alerts being equal, we have the whole team looking for reasons for various alerts, and start making sense of these data as a whole. This not only brings teams together, it also help resolve issues faster and increases mutual respect of all groups. This as a whole has changed culture at CloudMunch, and hence 2.0. Hope this makes sense.

You can learn more about our chat integration by going here and set up a team and see how you will start getting information as and when things happen in your team.

My next reason is Containers and how that brings a significant impact to the quality of service we bring to our customers.

Send in your thoughts.