Operations | Monitoring | ITSM | DevOps | Cloud

A few weeks ago I went to quantify a trend I had already clocked: our test-writing had climbed, and kept climbing. Where a typical month once brought a handful of new tests, last month brought 436.

If you've been watching the Puppetlabs namespace on the Forge (or waiting on a pull request you opened) you've likely noticed that the pace of inclusion of community pull requests and fixes into the module releases has slowed over the last several cycles. That isn't how we want to serve the community that built these modules with us. The team has been reviewing how we can improve and this post is our commitment to do better. Here are the steps we're taking now: Back to top.

The numbers from the 2026 State of the Database Landscape: AI Edition are striking. 99% percent of respondents using AI report at least one measurable benefit for their database work. Automation is up, performance is improving, and three-quarters report significant cost savings. By almost any measure, AI is delivering. However, sitting alongside that near-universal positivity in the same dataset, security and privacy concerns have climbed to 64%. Regulatory compliance anxiety has risen to 40%.

Turning off trend comparisons cuts Explorer load times in half on long date ranges.

In the hospitality industry, every second counts—especially when it comes to online bookings. Recently, I’ve been working with a hospitality customer who relies on eG Innovations SaaS to monitor the performance of their booking website. Like many modern sites, theirs is powered by numerous plugins and external third‑party services, each playing a crucial role in delivering a smooth booking experience while also introducing potential points of delay.

Almost every network monitoring tool on the market promises the same few things, which is full visibility, faster root cause, and fewer pointless alerts. Spend enough time looking into them and the websites all start to sound the same, and most of them read better on the page than they hold up on the day the network actually slows down.

An IT ticket rarely arrives as a ticket. Instead, it arrives as a Teams DM to whichever technician replied fastest last time, and the request dies with that person's inbox. When a 200-plus-comment r/sysadmin thread on favorite ticketing tools outranks almost every vendor page on Google, that tells you how many teams are still hunting for a system their users will actually use. We compared the 9 best IT ticketing systems for 2026, aimed at IT teams handling internal tickets, not customer support desks.