Operations | Monitoring | ITSM | DevOps | Cloud

Azure environments are growing fast, and so are the challenges of monitoring them at scale. In this blog, part of our Azure Monitoring series, we look at how real ITOps and CloudOps teams are moving beyond Azure Monitor to achieve hybrid visibility, faster troubleshooting, and better business outcomes. These real-life customer stories show what’s possible when observability becomes operational. Want the full picture? Explore the rest of the series.

When SentinelOne, a leader in cybersecurity and endpoint protection, experienced a major outage last week, thousands of organizations were suddenly left in the dark. With SentinelOne down for hours, IT and security teams scrambled for information and updates. But there was a critical missing piece: SentinelOne has no public status page. This gap left customers frustrated, searching for answers on social media, Reddit, and unofficial channels.

The familiar scene unfolds: Critical applications are sluggish, user complaints are mounting, and the IT war room is buzzing. Eyes quickly dart towards the network team. It’s an almost instinctual reaction. But what happens when the problem isn't within the corporate LAN or even the data center? What if the real culprit lurks somewhere in the vast, untamed wilderness of the internet, a cloud provider's backbone, or a third-party SaaS application’s infrastructure?

Ever wondered how Icinga 2 manages all those variables, and how it knows which one to use? In this blog post, we will explore all the different variable scopes in Icinga 2, and by the end, you will know what this mysterious error message means when you see it in your logs.

Join the live stream at 11 am ET, here. Platform teams tend to start with just one, or in some cases a handful of OpenTelemetry (OTel) Collectors usually running in gateway mode. They then embrace the benefit of a vendor-neutral, standardized, telemetry collector for unified logs, metrics, and traces.

The Internet Engineering Task Force (IETF) is the premier Internet standards body, developing open standards through open processes. The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of Internet architecture and the smooth operation of the Internet. The IETF standards-setting process is open to any individual interested in providing technical contributions.

Over time, web applications have evolved from simple request/response-based systems into complex, distributed ones with lots of moving parts. If something goes wrong (and you can be sure it will), finding the cause can be nearly impossible. But this need not be the case: enter tracing. Tracing refers to the process of collecting detailed information about the execution of requests within an application, including function calls, execution time, and other relevant data.