As I discussed in my last post, we believe that monitoring, like many other DevOps tools, needs to be adopted by other teams (i.e. developers, product managers, support, QA etc.) outside Operations. The trouble is many of the popular monitoring tools today were written by Operations guys for other Operations guys and don't make it easy for other teams to adopt. Here are our top 7 ideas on what will make your monitoring tool more popular outside your team, so that everyone in your organization can get the visibility and insight they need to build a better service together.
In my Monitorama Pitch in May, I focused on one of the core problems we see with today's monitoring tools - Adoption. When I talked about Adoption, we weren't talking about adoption of the monitoring tools in the Operations team, but all the teams that interact with Operations such as Developers, QA, Support and Product Managers. This was one of the core reasons we launched Dataloop.IO after struggling with this issue at our last company.
It's that time again, here are the videos and slides from DevOps Exchange London last week! The Meetup featured some fantastic talks ranging from docker networking, to building a high performance time series database from the ground up. We were kindly hosted by the Rainmaking Loft this time, located in St Katharine Docks there were plenty of great views to take in. Finally, everything ran smoothly, thanks to the big help from our friends at Linux Recruit.
At Dataloop.IO, our vision is to build a great company that has the potential to be a leader in our space. We spent a lot of time doing customer development before we launched our start-up 8 months ago to ensure we were solving a big enough problem and since then we've had phenomenal traction getting our new company off the ground. Here's a summary of our progress since we started:
Last week we made a trip to Portland, OR in the USA to attend Monitorama 2014. For those of you who've never heard of it before, it is a conference run in the USA and Europe dedicated to monitoring. So as a monitoring company, it was an obvious event for us to attend and sponsor.
Last week we organized our second DevOps Exchange meetup which we sponsored alongside StackExchange, who also hosted the event at their shiny new London offices near Old Street. Since our first meetup a couple of months ago, the meetup has quickly grown to over 270 members, making us officially London's 2nd largest DevOps specific meetup. We think by the time we hold our next event in less than a month, we'll probably be the largest, which is great traction for a meetup we only started in January!
Last week we organized our first DevOps Exchange meetup which we sponsored alongside Equal Experts. Although there are other DevOps meetups in London (for which we're regular attendees of) we decided to host our own after talking to lots of companies that wanted to get into DevOps but didn't know where to start. Many of the current meetups tend to be for experienced DevOps people in our opinion, and although we don't plan to be the meetup for beginners, we hope we can give at least one introduction talk to beginners (and their bosses) at each meetup to bring more people into this highly demanded field.
Back in 2011, a few people started complaining about how monitoring sucked with the #monitoringsucks hashtag appearing on Twitter. Since then a lot of DevOps people have joined the rally. However, more recently, #monitoringlove has appeared after a few open-source efforts—most notably Sensu—to improve the state of monitoring.
As we head into 2014 we wanted to say a huge THANK YOU to all the people who've taken the time to talk to us this year and helped us get our new start-up off the ground. Your advice and feedback has been invaluable in helping us get Dataloop.IO started, and myself and Steven are now working on Dataloop.IO full time with some amazing progress since we launched mid-October.