Does your team use Azure DevOps for tracking work? You’re going to love our latest integration if that’s the case. You can now create and resolve Work Items in Azure DevOps directly from Rollbar, making error monitoring and debugging even faster. This is the latest addition to our toolkit for the Microsoft ecosystem (read about our Azure Active Directory integration). It reinforces our mission to help software developers build software quickly and painlessly.

We’ve built a lot of amazing things into the open-source Netdata monitoring system. But, no matter how far we’ve come, we’ll always be proud of how little RAM it uses. Right now, Netdata stores metrics in your system’s RAM using a ridiculously efficient database. It only saves or loads historical metrics from disk when you restart it. With this system, Netdata can be both low-resource and exhaustive in its collection of real-time metrics.

Site reliability engineers (SREs) are the glue between “Dev” and “Ops,” ensuring that software engineering expertise is applied to operations challenges. SREs naturally focus on making systems more reliable, efficient, and scalable. If you’re an SRE yourself, you’re already deeply familiar with these ideas.

AWS Elastic Load Balancing is one of the most widely used of Amazon’s cloud services. In many AWS stacks, an Elastic Load Balancer (ELB) will be involved in almost every single request that customers make to your application. Since they are critical to the health of your application, properly monitoring ELBs is a top priority for most teams. In this blog post, we will go over how Blue Matador monitors Classic Elastic Load Balancers automatically and without configuration.

Thanks to all who attended our second annual Dash conference! We hope that you enjoyed your time with us at New York City’s Chelsea Piers, and that you were able to learn about building and scaling systems and teams in our breakout sessions and workshops. For those of you who were unable to attend, we hope to see you next year. Check out some of the highlights from our two-day conference below.

At Honeybadger, we use Redis a lot. It's our Swiss Army Knife; it's a cache, a single source of truth, it stores background jobs, and more. Basically, Redis is one of those services that should never fail. I was pondering the DevOps apocalypse recently, as one does (could Redis be one of the four horsemen?), which led me to jump into our #ops channel to ask Ben a simple question: what are the risks if someone executed flushall on our redis instances?

It’s not the first time I’ve been asked by a sales rep the following question: “The customer has looked at Stackalytics and is wondering why Rancher doesn’t have as many code commits as the competition. What do I say?” For those of you unfamiliar with Stackalytics, it provides an activity snapshot, a developer selfie if you will, of commits and lines of code changed in different open source projects.

If you ever need to duplicate or clone your Azure VMs or perhaps even migrate your Azure VMs from Azure Service Manager (ASM) to Azure Resource Manager (ARM) you can use one of our Azure Management Tools, Azure VM Cloner (AVMC) to quickly and easily do this for you.

Transformation of IT Ops When I think of the term IT Ops I immediately think of Enterprise IT and the traditional attributes that make up this function – many of which are in the middle of an industry-wide disruption – and its associated impact. At LinkedIn, when we first looked at business process support, shadow IT and non-accounted-for IT spend, about 10 years ago, it was a bit of a revelation to me how the landscape had already changed by then.

The radical shift towards DevOps and the continuous everything movement have changed how organizations develop and deploy software. As the consolidation and standardization of continuous integration and continuous delivery (CI/CD) processes and tools occur in the enterprise, a standardized DevOps model helps organizations deliver faster software functionality at a large scale.