Operations | Monitoring | ITSM | DevOps | Cloud

IT service desk technology has made tremendous strides over the past decade. Despite this fact, however, a recent survey by Gatepoint Research revealed that 74% of today’s on-site workforce still relies on phone calls to get the support they need. Remarkably, this number is even higher (80%) amongst remote workers. This is placing a heavy burden on support teams that are already stretched too thin.

Here on the CircleCI Insights team we don’t just develop stuff for CircleCI users, we are CircleCI users. Really, there’s no better way to get to know your product than to use it, and the Insights team is no exception. A few months ago, we realized that our pipeline configuration for the Insights UI left much to be desired.

This is the second part of our EKS with Terraform series. In Part 1, we talked about Infrastructure as Code and its benefits. We also mentioned the tools we will be using. This time we will actually start using Terraform to create a VPC and EC2 instance.

When I started at Puppet three years ago, I saw a company with a tremendous customer base, an active open source community, an incredible reputation, products that solved some of the hardest problems in the operations space, and a passionate team that had deep values and was purpose-driven, both of which are at my core as a leader.

When your organization uses the cutting edge of technology to function, you may feel like it takes all your time and energy to stay on top of emerging trends. How are you supposed to anticipate what the future will hold when you have to balance those considerations with how to best provide for your customers’ needs today? It’s okay if you don’t have your finger on the pulse 100 percent of the time.

Developers strive to produce efficient code. Many times, developers will add code to their repositories and test it to make sure it works, but they are forgetting one very important step: benchmarking! Benchmarking allows developers to see the performance impact on their code output. If properly integrated into a CI/CD pipeline, it could prevent catastrophic drops in performance before any code is shipped/deployed at all.