Operations | Monitoring | ITSM | DevOps | Cloud

So, you want to become a DevOps engineer? It’s a stimulating, challenging, high-paying career choice, but the lynchpin role holds software development and operations together. We’ve compiled a DevOps roadmap that includes all the steps required to fill the shoes of a DevOps expert. As you know, DevOps is a set of practices and tools to integrate and automate processes between IT and software development teams.

Have you considered cloud portability, i.e., the ability to easily move workloads between on-premises systems and across multiple cloud service providers (CSPs)? The idea is that workloads should run in the environment that delivers the most value for your organization, but as that “optimal” environment can change over time, you need to be able to move your workloads accordingly.

In this part 1 of a blog series on serverless monitoring, we will learn how to run the observIQ Distro For OpenTelemetry Collector, referred to as “oiq-otel-collector”, in Google Cloud Run. There are many reasons that someone may want to run monitoring in a serverless state. In our example, we will be monitoring MongoDB Atlas, a cloud hosted version of MongoDB.

The DevOps practice of continuous integration and continuous deployment (CI/CD) improves software delivery. CI/CD platforms monitor and automate the application development process ensuring a better application, faster. CI/CD pipelines build code, run tests, and deploy a production-ready version of an application that has passed all automated checks.

Charting can be complicated and intimidating, especially when dealing with web performance data, flame charts, and percentiles. There is so much data crammed together! Why are the numbers all different?! Let’s break down these charts, what they are good for, and when to use them.