Operations | Monitoring | ITSM | DevOps | Cloud

TL;DR - Turbopack became the default in Next.js, so we reworked our SDK to stop depending on bundlers. The result is less code, faster builds, and the same telemetry. This blog explains how we got there. You know the feeling when you spend years building tooling that supports something and all of a sudden that something becomes deprecated and you have to rethink your full approach?

As per the Enterprise AI Survey conducted by Digitate in collaboration with Sapio Research revealed that IT operations have emerged as the primary proving ground for artificial intelligence in the enterprise. With 78% of organizations already deploying AI in IT, 65% identifying ITOps as the biggest AI beneficiary, and adoption outpacing every other function, IT leads enterprise AI maturity.

Reliability used to mean “are we up?” Today, customers ask something more demanding: “Are you fast, everywhere, every time?” The SRE Report 2026 shows that this change is no longer emerging. It is already established.

Splunk is a leading platform for searching, monitoring, and analyzing logs across IT tools and systems. Well-known for its ability to handle vast volumes of log and event data, Splunk empowers organizations to gain real-time visibility into their systems and operations. However, while Splunk offers rich telemetry and analytics, its dashboards can sometimes become complex - making it difficult to surface the most critical insights quickly. That’s where SquaredUp can elevate the experience.

APIs are no longer just technical connectors between systems; they are production infrastructure. Customer-facing applications, partner integrations, payment flows, and internal microservices all depend on APIs working correctly, consistently, and at scale. When an API fails, the impact is rarely limited to a single endpoint; it can disrupt user journeys, compromise revenue, and breach service-level agreements (SLAs).

We’re excited to roll out an improvement many of you have been asking for: extended historical metrics for website and ping monitors. Until now, monitor metrics like availability, downtime, and response times were limited to the last 24 hours. While useful for short-term checks, this made it harder to spot trends, investigate intermittent issues, or understand long-term performance. That changes today.

From an IT pro’s perspective, the future of networking technology in 2026 is a mixed bag of potential and security risk. New wireless tech, agentic AI, and the increased distribution of networks are enabling new use cases and helping automate toil, but they also create new attack surfaces and risk profiles. In this article, we’ll take a look at the ten network security trends we’re most excited about in 2026 and provide key insights about what each one means for IT and MSP teams.

This article explains how to integrate metrics from Prometheus into Icinga checks using the check_prometheus plugin. There can be multiple reasons why this could be desired: Maybe you have different teams with their own monitoring systems, and you need to bridge the gap, or you want to perform queries that are just better expressed in Prometheus than in plain Icinga check plugins. The latter can be the case if you want to aggregate data from multiple sources or you want to take historic data into account.

In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already going wrong? One answer, used quietly but consistently by high-performing teams, is the checklist.