• Founded in 2004, headquarters in Cupertino, CA • 400+ employees worldwide • 9 member Ops staff – all remote • CRM == “Customer Relationship Management” • Highly customizable CRM • Diverse technology stack
Started! • Late 2013, old solution no longer cutting it – API breakage with every upgrade – Dashboards difficult to build and inflexible – Building new plugins was painful – Integration with configuration management was difficult, things got missed
• Started here • Most were young or undergoing massive changes • Issues with agent deployment • Many were platform specific • None supported monitoring of network devices • Required us to build plugins
Solutions! • None we found addressed original issues • No budget for new hardware (and software) • Either complicated or difficult to extend • Required us to build plugins
We’re going to be build something, do we want to pay someone for the privilege? How much time will it really take to build and maintain the server-side components?
• Automatic ticket creation didn’t quite work • We’re using JIRA for incident tracking, click-to- create link in every email • Tracking of issues much better
• Sensu checks which trigger no action • Used for systems which already provide notification • Events show up in dashboard • Dashboard becomes central place for events
Reduces performance metrics to single value • Useful in communicating customer satisfaction with other departments Apdext = (Satisfied Count + Tolerating Count / 2) / Total Samples
Initial buildout of backend systems was hard • Ongoing maintenance, not so bad • Scaling out Graphite is a pain – Carbonate makes it tolerable • Smaller components make upgrades easier • On the other hand, always upgrading • Integration between tools is poor, but improving