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

Jonathan is a platform engineer at VictorOps, responsible for system scalability and performance. This is the second part in a series on system visibility, the Detection and Analysis part of the Incident Management Lifecycle. If you missed it, read Part 1 first. Unified Interface Like any good engineering approach, we wanted a simple, thin facade that would codify our use-cases, provide a single extension point, and be low-overhead to maintain. With the exception of appender performance, we needed unification of the interfaces in order to address all the concerns mentioned in Part 1. We did just that. We created a top level Logger that would house all supplemental functionality and become our primary interface regardless of whether we’re logging from a “typical” class, an actor, or a controller. There are two implementations: ClassLogger and ActorLogger which behind ... (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)

ChefConf 2015 Wrap-up By @VictorOps | @DevOpsSummit [#DevOps]

By Jason Hand Community is an area of great interest to me. As the evangelist for VictorOps, I’m tapped with many challenges and responsibilities. Not only do I try to provide useful guidance and feedback regarding VictorOps and DevOps best practices, but also bring together customers and partners with shared interest and excitement for what we are building to make on-call suck less. If there is a group in which one could model how to build a great community after, it’s Chef and this year’s ChefConf is a testament to that. Taking place in the Santa Clara Convention Center, Chef... (more)

An Interview with Jason Dixon | @DevOpsSummit #API #DevOps #Containers #Microservices

DevOps Interview: Jason Dixon By Jason Hand If your primary role within your organization is Operations, you likely realize the importance and significance of monitoring. The DevOps philosophy teaches us that measuring and collecting as much as possible is critical to not only the health of infrastructure, but it also plays a critical role in the architecting efforts of both software and hardware. Jason Dixon of Librato knows this better than many and has made a career of helping others understand and implement the best tools and processes of successful monitoring. Known by many ... (more)

Common On-call Scheduling Issues

One of the hardest things about managing on-call for your team can be creating the schedule for on-call rotation. Are you going to go with a standard weekly rotation cycle? Do you have coworkers in other parts of the world you’ll have to include on this rotation? And what about holidays or vacation time…are those even allowed in your current on-call schedule? Is it up to individuals to sort out any substitutions or on-call swaps? We’ve offered some tips on how to take care of your on-call team and how to prevent burnout. But when it comes to actually scheduling on-call rotations, ... (more)