We at Icinga / NETWAYS (yes, that’s the order) held an internal event recently. It’s name was Knowledge Days and I got to to talk about how I review code. Now, I will share my knowledge with you! Though, this is specifically how I personally perform reviews. This is by no means the definitive way of doing it! Find your own, I can only share my experience. So without further ado…

As 2024 peeks into 2025, cloud-driven businesses are poised for yet another year of record cloud spending. After exceeding $675B this year, cloud spenders are expected to shell out more than $820B in 2025 (Gartner). But as any good unit economist knows, it’s not just that cloud costs are growing, it’s that they’re growing inefficiently — taking too big a bite out of companies’ profits.

Earlier this year, we introduced relational fields. Relational fields enable you to query spans based on their relationship to one other within a trace, rather than only in isolation. We’ve now expanded this feature and introduced four new prefixes: child., none., any2., and any3.. Previously, you could use root., parent., and any. to query on the root span of your target span’s trace, the parent span of your target span, and any other span in the same trace as your target span.

In today's data-driven world, businesses need to collect, process, and analyze large volumes of data in real-time to make informed decisions. Amazon Kinesis, a powerful streaming platform, helps companies build scalable and resilient data pipelines. However, ensuring that the pipeline functions efficiently requires robust monitoring practices.

Oracle Cloud Infrastructure (OCI) is a powerful, comprehensive cloud platform that supports a wide range of enterprise workloads. Whether you're running complex databases, applications, or large-scale analytics, OCI offers the infrastructure to handle it all. But as with any robust cloud environment, effective monitoring is crucial to ensure performance, security, and cost-efficiency.

Application performance is critical for a seamless user experience, but all too often, developers find themselves struggling to pinpoint slowdowns. Understanding the root cause is the first step to diagnosing and solving performance issues. In this article, we’ll explore six common root causes of application performance slowdowns and share actionable advice on how to fix them. We will also show how platforms like Sentry can help uncover, trace, and debug these issues faster.

Two of the most popular guides we’ve written are the GitOps promotion guide and the ApplicationSet guide. Used together, they explain an end-to-end solution for organizing your GitOps applications and promoting them between different environments, while keeping things DRY by using application sets. Both of these guides use Kustomize. We offered some hints for Helm users, but this is a dedicated guide for Helm applications.

The primary objective of an IT incident response plan is to clarify roles and responsibilities, communication protocols, escalation scenarios, and technical steps to minimize further damage and safeguard business operations. The plan formally defines guidelines, procedures, and activities for identifying, evaluating, containing, resolving, and preventing IT incidents. Whether they cause intermittent errors or global service crashes, IT incidents can severely disrupt service quality and cause outages.