Are incident reviews about learning or tracking actions? This question has sparked recent debate in incident management circles, including in my recent panel at SEV0 and in Lorin Hochstein’s post. Should the goal of an incident review be learning, or should it focus on tracking actionable improvements? When is the right time to discuss actions, and are they picked up just to make us feel better? From my experience, learning from incidents and identifying actions are inseparable.

This month marks a huge milestone for us at Cortex. We’re excited to announce that ServiceNow, the global leader in digital workflows, has invested in our Series C funding round. Together, we’re pushing forward with our mission to unify tech operations at the enterprise through our industry-leading Internal Developer Portal (IDP).

Microsoft Azure is the most popular cloud computing platform after Amazon Web Services (AWS). With over 200 services and resources available, there are plenty of ways to use Azure. This means the Azure public cloud allows hundreds, if not thousands, of unique configurations. This flexibility is ideal for tailoring Azure to your workload’s requirements but also makes cloud management more challenging.

Learning how to manage IT infrastructure remotely is an essential capability for businesses of all sizes, particularly with the rise of distributed workforces. With the right tools and strategies, IT teams can effectively monitor and troubleshoot systems from anywhere, ensuring smooth operations and minimal downtime. This guide will cover best practices for maintaining control over your network, regardless of your team’s location.

Are your developers using the latest AI-ready platforms to power ahead with innovation? If not, then it’s time to re-evaluate your platform strategy.

At some point, your development team may be considering implementing load testing (also known as stress testing) as part of your software testing process. Load testing validates that your web app is able to withstand a large number of simultaneous users, decreasing the chance that any traffic spikes will bring down your services once deployed. These stress tests can be highly granular, giving you the opportunity to test run virtually unlimited strategies before they are set into the wild.

It’s 2024; who hasn’t heard of.NET Core, the primary framework developers use to build desktop and web apps? However, if you want to build something impactful, just choosing the right technology isn’t enough. Any major development process requires you to follow certain best practices to ensure that the project you’re building is future-proof. In this article, you’ll find the.NET Core top practices to help you ensure that your application is secure, scalable, and efficient.

Transactions-per-Second (TPS) is a valuable metric for evaluating system performance and is particularly relevant for engineers overseeing Kubernetes environments.TPS, alongside average response time, provides critical insights into system performance during load testing. This post covers two approaches to calculating TPS; a manual approach applicable in all environments, and an automatic Kubernetes-specific solution using production traffic replication.

As developers, one of the most important things we can consider when designing and building applications is the ability to know if our application is running in an ideal operating condition, or said another way: the ability to know whether or not your application is healthy. This is particularly important when deploying your application to Kubernetes. Kubernetes has the concept of container probes that, when used, can help ensure the health and availability of your application.