Unless end users (EUs) are directly prevented from using applications, they are unlikely to report IT anomalies or malfunctions; it’s much easier to restart a program or click “x” to make the error message disappear than submitting a ticket. Every day, employees settle for small IT glitches which never go reported, giving IT departments the perception of smooth service delivery while, in reality, EUs are experiencing constant obstacles and frustration.

There should be no doubt anymore that containers are revolutionizing the world of application development and leading the charge for purpose-built cross-cloud and hybrid-cloud topologies. There are other virtualization platforms that solved problems in server consolidation and data center optimization, but in the new world of cloud and mobility, proprietary monolithic middleware may have had its day.

One of the key pieces of wisdom regarding any kind of development project is that all software problems are inherently hardwaret problems. This is one among many reasons why devices like the iPhone and the Xbox have been so popular over the years. When software and hardware integrate properly, and code is written to specs that take full advantage of the platform, great things become possible.

In a previous post, we explained the concept of configuration management and presented three of the most popular tools: Chef, Puppet, and Ansible. We also briefly explored the impact that containerization is having on configuration management, and how the two can be used in combination. This article takes a more in-depth look at this relationship by presenting different techniques for using Chef, Puppet, and Ansible to deploy and manage a Kubernetes cluster.

Enterprise users of Office 365 often need to configure a multi-function printer to use the platform’s SMTP email capabilities on their network. There are several ways of doing this, each with their own benefits and disadvantages. In this guide we’ll be looking at the steps required in setting up Office 365 network printing and email under various conditions.

It’s been a big month of great product updates in January, including the launch of the OpsRamp Winter Release, the ability to deliver collaboration across service delivery and IT operations teams with our certified ServiceNow integration and silver membership in the Cloud Native Computing Foundation (CNCF). In this month’s OpsComm, we’ll take you through some of the exciting news and updates at OpsRamp. To see all of the recent OpsRamp coverage, check out our newsroom.

The importance of effective business continuity planning (BCP) cannot be understated. Being able to avoid and mitigate the risks and damages associated with a disruption to operations is critical to the health of any business. And, the two main pillars upon which a robust BCP program rests are, of course, the plan and the testing program.

Gatsby is currently generating a ton of buzz as the new hot thing for generating static sites. This has lead to a number of frequent questions like: A static…what now? How is GraphQL involved? Do I need to set up a GraphQL server? What if I’m not a great React developer, really more of a bad React developer?

A site under maintenance can be stressful for employees and customers. In our fast paced and hyper-competitive business environment, pulling through unharmed from a difficult situation requires a lot of effort, communication and teamwork. Often the level of effort required to ensure things run smoothly goes unnoticed by those on the outside of your organization.

Let’s start with the happy ending — after a long search, we managed to identify a Netty memory leak in one of our log listeners and were able to troubleshoot and fix the issue on time before the service crashed.