Operations | Monitoring | ITSM | DevOps | Cloud

An incident can take many forms. It can look like a small issue that locks a few customers out of their accounts or a huge catastrophe that brings down your entire product for a full day. How you respond to the incident should vary based on the impact of the incident. And that’s where severity comes into play. Defined severity levels are crucial to any good incident management program.

Everyone’s talking about Platform Engineering these days. Even Gartner recently featured it in its Hype Cycle for Software Engineering 2022. But what is Platform Engineering really about? Is it the next stage in the evolution of DevOps? Is it just a fancy rebrand for DevOps or SRE? As a veteran of the PaaS (Platform as a Service) discipline about a decade ago, and a DevOps enthusiast at present, I decided to delve into this topic, peel off the hype, and see what it’s about in practice.

Business organizations that want to save money and be competitive take into consideration the time costs associated with investments in new technologies. Will the efficiency gains translate to a rapid return on investment? Will users embrace the change and be more productive? Or will those investments be a hassle to employees and result in time-wasting workarounds and a fallback to inefficient, manual processes?

Setting FinOps KPIs helps keep your whole organization aligned toward the same financial goals. However, it takes more than simply setting a broad, company-wide financial goal and turning every employee loose to work on that goal without more specific directions. It’s far better to come up with realistic and achievable goals tailored toward each person or team that will be responsible for them. That’s because KPIs should ideally be focused around the typical persona of each team.

Monitoring indoor air quality with Airthings and Netdata. Understanding and measuring common contaminants and pollutants reduces your risk of air quality health concerns.