Operations | Monitoring | ITSM | DevOps | Cloud

In 2020, we started an internal project to price our data center systems to understand what they might cost to run in the AWS or Azure cloud environments. We initially used some of the online pricing tools available from these vendors, but they were slow and difficult to use in bulk. You can find the public cloud tools here: AWS and Azure. We were forced to add individual systems one at a time and pick options for each because of the nature of these tools.

In the first part of my DevOps 101 series, we tackled the fundamentals of What, who why and how. In this follow-up, I’m going to focus on how to gain buy-in across your organization. That said, who do you need buy-in from? DevOps is the union of people, processes and products to enable continuous delivery of value to our end users, according to Microsoft’s Donovan Brown. That’s a good explanation, because the focus is not on tooling, or processes, or even just people.

Welcome once again to another Logic App Best practices, Tips, and Tricks. In my previous blog posts, I talked about some of the most essential best practices you should have while working with the Azure Logic App: And some tips and tricks: Today I’m going to speak about in my opinion one of the most annoying features/tasks and recommend some Best practices, Tips, and Tricks to minimize it: working with expressions.

In this blog, we will be introducing the concept of High-performance computing (HPC) and HPC clusters. We will also introduce a few categories of practical workloads important in the HPC space. This blog is a part of a series of blogs on HPC where we will introduce you to the world of HPC.

Datadog Events provides customers with a data feed about their infrastructure and applications, delivering an up-to-the-minute history of activity such as code deployments, configuration changes, and triggered alerts. Events collects data from Datadog products and over 100 third-party integrations—including Docker, Jenkins, Kubernetes, Sentry, AWS CloudWatch, and Azure Service Health.

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.

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.