Operations | Monitoring | ITSM | DevOps | Cloud

Buying software is often the answer for busy engineering teams in search of a quick solution with minimum aftercare. But while your team may be sure of the problem, how do you go about searching for a product to fix it? Far from being the 'easy option', there is a lot you need to consider before you invest in a bought solution – user experience, cost comparisons, and support features to name a few. Let’s explore some of the considerations when making a good decision.

Do you author plans for Puppet Enterprise? Looking for ways to improve them? Read on! The Puppet Plan language allows a variety of methods to pick targets. In this article we will explore two of these methods (TargetSpec parameters and PuppetDB queries) and how plan authors can employ the latter to: Note: the following examples assume that you are running against targets that have the Puppet agent installed.

How different are DevOps and SRE? Are they related to each other? In this blog, James Samuel sheds light on the similarities & differences between SRE & DevOps followed by the possible ways to structure an SRE team in your organization. One of the terms that people often find confusing is SRE and DevOps. People often ask, should I hire a DevOps Engineer or a Site Reliability Engineer? What is the difference between SRE and DevOps and which one do I need? In this post, I attempt to shed some light.

As IT landscape is changing from in-house systems and servers to cloud ones, server monitoring has become an essential task. Without server monitoring, it’s not possible to detect issues in memory, operating systems, storage drives or applications. Server monitoring is vital to know what went wrong and what was the cause behind the problem.

The real-world use cases for deploying a Microsoft Direct Routing Survivable Branch Appliance (SBA)

Virtualization and cloud have forced the need for automation. In the “old” days, it would take weeks for a new physical server to arrive. There was little pressure to install and configure the operating system on it rapidly. We would insert a disc into the drive and then follow our checklist. A few days later, it would be ready to use. But the ability to spin up new virtual machines (VMs) in minutes required us to get better at automating this process.