Operations | Monitoring | ITSM | DevOps | Cloud

With multiple teams working on many projects, having a single pipeline for your software is just not enough. These projects need to be built and integrated before they can be tested and released. So how do dev teams handle this situation? Many teams approach the problem by breaking down software into smaller parts that do less, and are easier to maintain and build. This approach has resulted in the microservices architectures that are increasingly common in our industry.

In 2021, the most popular vendor in the cloud infrastructure services market, Amazon Web Services (AWS), controlled 32% of the entire market. To encourage more businesses to choose AWS, Amazon started a program to help accelerate migration — the AWS Migration Acceleration Program (AWS MAP). Below we’ll cover the details of the program, the potential financial benefits for companies looking to take part, and how to make sure you get all the financial benefits available.

Since its introduction in 2014 to the world, Kubernetes has been helping usher in the next generation of distributed workloads. As workloads started to be containerized, so did the need to manage the containers, thus the inception of container orchestrators. There have been a few container orchestrators out there before Kubernetes such as Docker Swarm and Apache Mesos. Though as a feature developer, Kubernetes can certainly feel like an 800-pound gorilla in the room.

Datadog Notebooks enable your teams to create and manage key reports and documentation as they build out, monitor, and maintain their infrastructure. Notebooks can include both text and graphs of any telemetry data you have collected in Datadog, and they support collaborative editing so that multiple team members can edit and leave comments simultaneously.

For many of us in the technology world, around the holidays family will always ask you to solve their technology problems. Being in February, I am only several months away from sharing the below card with my family, again.

The waiting can be intensely stressful. You are mid-way through a critical production upgrade during the weekend. The schedule is tight. Suddenly there is an unexpected problem you aren’t able to resolve. You need help. So, you call in a support ticket. And that’s when the waiting starts. While you’re waiting for the support team to review and get back to you, questions race through your mind: How quickly will they respond to the ticket?

Severity and priority can be challenging for a company to nail. When an incident is declared, it's essential to have a system to define the impact and how urgently it should be handled. Incident severity and priority are the two knobs teams can leverage to define scope and urgency, and eventually, the appropriate process to take action. But how should we define them, and what are the differences?