Operations | Monitoring | ITSM | DevOps | Cloud

Splunk recently announced exciting updates and significant modernizations for the upcoming releases of Splunk Enterprise and Splunk Cloud Platform. This blog is the first in a series to help prepare your organization for these changes by exploring upgrade readiness best practices. This first installment will highlight the Splunk Health Assistant Add-On, a vital tool that supplements the Splunk Enterprise Monitoring Console, designed to streamline your transition to the next version of Splunk Enterprise.

Coroot is excited to feature an editorial from GlassFlow for our first Open Source Spotlight. We hope to improve the workflow of our global community of SREs and DevOps professionals by sharing exciting projects like Glassflow, which make innovation accessible for everyone through the freedom of open source. If you have an open source or open core project you’d like to see on our blog next, send us a message!

Traditional databases store data in structured tables, whereas NoSQL (non-SQL) databases use more flexible, non-tabular storage methods. NoSQL databases can store a wider range of data types, including document stores, wide columns, key-value stores, and graphs. These databases first emerged in the late 2000s to support massive horizontal scaling and high-throughput workloads for web applications.

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.