You may not have heard of Opsmatic, but if you’re trying to juggle 27 projects in 15 different development languages that spawn 13 different versions of your application then you really should look them up. Opsmatic is a DevOps tool that creates order out of chaos. It monitors application development in real-time and allows policies to be set against the live-state to create intelligent alerting, and to get away from the alert-fatigue associated with current DevOps tools.
The problem with DevOps is DevOps itself – a recursive problem if you will. DevOps encourages change, which is fine when you have a single application, with one set of code and a team that sits in the same room. But who the hell does that? Most development teams are wide spread, code is produced by everyone from interns to code ninjas, and most of it is done in the language that’s most appropriate to the section of the application they’re in - and what side of the bed they got out of that morning - so C# sits next to Java, and Ruby on Rails etc and the code is sat in lots of different silos. Then when you add in mobile, things get much worse. Applications these days need to work everywhere including mobile and all of the different flavours of iOS, Android and Windows etc In short it’s an administrative nightmare and huge potential source of problems. According to research done by Opsmatic configuration errors account for over 40% of outages.
Opsmatic was developed in-house by a team with a background in development at digg, Yahoo and flickr and works with and augments Puppet, Chef, Ansible, SaltStack and Docker, configuration management tools and Slack, Pagerduty, DataDog, Nagios, Hipchat alerting and issue management tools and New Relic performance monitoring. But there are plans to extend its use to cover all of the different areas of application development – from security to testing.
The SaaS solution monitors the development systems in real-time via a secure agent on each host that feeds into the central Opsmatic platform which collects and analyses the data. From the dashboard you can see and track all the code changes made to the infrastructure, you can see run failures and cookbooks used, see drifts, and then assert policies against the live state, and see how the different parts of the project relate to each other all in real-time.
In an interview with CCi founder Jim Stoneham said. “Our goal was to produce a central source of truth, it’s built as an api service – with host agents passing data to a central saas repository and collector of live-state data. Our entry point is configuration monitoring and associated policy checks, but we also additionally integrate with a number of tools on the alerting, notification and performance monitoring side.”
The Opsmatic service is sold as a monthly subscription, with billing based on usage $5 per host, per month, based on the peak number of hosts being monitored each month.