We wrote this article in response to a question asked in our Slack Community. Click here to join hundreds of technology leaders discussing best practices for incident response! ✨ We know a thing or two about incident response. As such, we're often asked to advise when companies are designing their incident response processes. A common question is "How do you design your incident severity levels?". It's a great question given how central they are to incident response!

One of the most well-known and commonly used open-source operating systems is Linux. It's a clone of UNIX, however unlike UNIX, it's free to download and use. Despite being an open-source operating system, it has a safe and resilient architecture, and many individuals and companies rely on it. You can, interestingly, make your own Linux version. You can accomplish so by simply downloading Linux and making the necessary adjustments. In essence, we can distinguish them as different Linux versions.

You have many options when it comes to choosing a platform to deploy your app. In this article, we will compare AWS, Heroku, and Qoddi. Heroku is hosted on AWS, making Heroku, like Qovery for instance, nothing more than a management platform for AWS services. You can do everything you do on Heroku (or Qovery) directly with AWS for a lesser price but Heroku removes all the infrastructure management layer (or DevOps) you still need to have with AWS or any other cloud providers.

“What is up with the Context in OpenTelemetry? Why do I need to mess with it at all? Why, when I set a span as active, don’t subsequent spans just use it as a parent?” Oh, yikes, yeah. The Context abstraction in OpenTelemetry is hard to understand. Here are several ways it’s tricky.

Our brand new Google Analytics integration has just landed! Now you can benchmark your website performance on your real website analytics.

We discuss what an incident response team does, how it is structured, and how to form the best one for your organization.

In 2022, it’s hard to find places in the business and technology ecosystem where performance is not measured, where lots of data is not collected and where insights are not analyzed to improve operational and business performance and trace accountability.

Great news for the SCOM community – SCOM 2022 is going to be released in the spring! SCOM isn’t going anywhere and it’s only getting better. We saw this proven in the Big SCOM Survey Results 2021 where more than half of respondents said they were going to increase their SCOM deployment to monitor more of their existing and new infrastructure.

This article was written by Donal O Duibhir, Founder & CTO, PanSift. Scroll down for the author bio and photo. In 2015 I gave a brief talk at the Wireless LAN Professionals conference in Berlin about remotely troubleshooting client performance and Wi-Fi at scale. The solution I described then was rough and didn’t yet use a time series database (TSDB), but the requirements and goals are still valid and even more vital today.

Gone are the days where software development was slowed down by the top-down, water-fall approach for getting work done. The rigidity of this methodology made for a longer development lifecycle, and it affected the way software was created and deployed.