With over 10 years of experience, I’ve been doing everything from hands on programming to complete system architecture. As infrastructure team leader at BigPanda (and before that at Thomson Reuters) I’m responsible for designing and building the IT and software infrastructure that make products tick. My passions in life (in this order): my wife and son, gourmet, cinema and code as craft.
In the last two decades, with the emergence of cloud infrastructure and SaaS delivery models, the monitoring ecosystem has changed dramatically to include over 100 monitoring solutions. The upside of that change is the rapid implementation of monitoring infrastructure, but the unintended consequence of this is that the tools themselves decide what IT measures.
CONNECT ALL THE THINGS! Here at BigPanda we are constantly working on adding new monitoring systems to our arsenal of out-of-the-box integrations. We already provide integration with all of the most popular monitoring systems & services. Nagios, Zabbix, Zenoss, New Relic, AppDyamics, CloudWatch, Pingdom are all there. And there's many more – this list gets longer with every week that passes. These out-of-the-box integrations from BigPanda have many advantages:
Monitoring applications in production has never been easier. With only a few code lines, you'll have New Relic installed and monitoring your application from nearly every angle. When something goes wrong, New Relic will start sending alerts. But then what? (hint – New Relic and BigPanda together is the answer).
As a startup company driven by customer feedback, BigPanda has been practicing continuous delivery from day one. However, continuous delivery cannot be accomplished efficiently without a proper automation infrastructure. So, like many before us, we also began our search for the best deployment automation tool.
Service downtime is a harmful event to most technology businesses, especially to those who require their services to be constantly available. Downtime has many causes, such as hardware failures and network issues. In today’s web-scale world, application deployment is one of the main reasons for such downtime. This is particularly common with organizations performing Continuous Delivery, in which developers deploy their code at an unprecedented speed. Since there is always a good chance that the new code contains errors, the frequency of application changes holds a high risk of service malfunction.