Welcome!

VictorOps Helps Your IT/DevOps Team Solve Problems Faster

VictorOps Blog

Subscribe to VictorOps Blog: eMailAlertsEmail Alerts
Get VictorOps Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by VictorOps Blog

Greg Frank is a VictorOps engineer on the plat-frastructure team. An iOT aficionado, Greg built a smart home system using SmartThings and VictorOps. Over the years, I’ve had the misfortune of experiencing some small water leaks at my house. These were minor events: a leaky ice maker and a water valve for a sink. But among my friends and relatives, I have seen and assisted with cleanup for more severe water leaks that involved great expense and effort. Configuring a smart home My instinct as a developer is to attempt to find patterns of problems and connect them with general, proactive solutions that address the broadest category possible. This thinking process sent me down the path of evaluating smart home solutions and using automation to reduce the problems and stress of owning a home. Throughout this search for a solution, my instinct toward DIY was tempered by ... (more)

Skyscanner Case Study: Alerting Beyond Ops Metrics By @Tarable | @DevOpsSummit #DevOps

Skyscanner Case Study: Alerting Beyond Ops Metrics By Tara Calihman Skyscanner is a global search engine that enables people to find comparisons for flights, hotels and car hire. Headquartered in the UK, Skyscanner has been an excellent customer of ours, providing feedback on new features and helping us with testing. When Lance Gobaira, a web operation engineer at Skyscanner, offered to share with us how they’re using VictorOps to alert on key business metrics, we jumped. Read on to see what he had to say… Here at Skyscanner Engineering, we are serious about our metric collection ... (more)

NOC, NOC… Who’s There? By @VictorOps | @DevOpsSummit [#DevOps]

By Bryce Ambraziunas In part one of this series, our COO tackles the history and purpose of the NOC. A NOC, for those who don’t know, stands for Network Operations Center and, quite simply, is how large organizations with complex systems monitor them. Early versions of the NOC came about in the early 1960’s when there was a need for humans to actively take part in noticing, and fixing, complex errors. An early NOC was opened by AT&T in New York to display switch and route information, in real-time. It’s easy to see why a NOC used to be considered essential for larger companies ... (more)

Actors as Microservices | @DevOpsSummit #DevOps #Microservices

Actors as Microservices By Nick Isaacs Here at VictorOps, we rely heavily on Akka and during my time working with the environment/tool/language, I started seeing similarities between microservices and actors. Actors allow you to take pieces of your app, put them on their own servers and then enable them to communicate via HTTP. You can scale the app in places where there are bottlenecks and apply resources without being wasteful. Microservices are untyped (they communicate via JSON) however it is often the approach to write a client library on top of a JSON API, taking a weakl... (more)

SBT, Scrooge, Intellij and You By @VictorOps | @DevOpsSummit [#DevOps]

How to Set Up a Playdate Between Scala, Thrift, Scrooge, SBT and Intellij By Nick Isaacs Here at VictorOps, we are going through the process of overhauling the serialization framework that we use for inter and intra process communication. We evaluated several great options including Kryo (and its Scala companion Chill), Protobuffers, and Thrift. In the process, we put together a little test project to help us decide which of these choices was right for us. Testing Thrift posed some challenges as the tooling, while quite mature, wasn’t quite as plug-n-play with our local developme... (more)