Operations | Monitoring | ITSM | DevOps | Cloud

GPU monitoring in OpManager: Full visibility for every AI workload

AI has moved to be a core part of enterprise infrastructure. GPUs are the engines behind that shift. Every training run, every inference request, and every fine-tuning job depends on GPU chipsets that are expensive and delicate. A GPU that overheats, runs out of memory, or sits idle for hours doesn't just slow a project down, it quietly drains the IT budget. Most monitoring tools weren't built with this hardware in mind. This leaves AI and DevOps teams blindsided when a job fails or a chipset degrades.

LAS Migration Aftermath: What Happened to Your License Usage Metrics?

When Citrix introduced License Activation Service (LAS), customers transitioned from the traditional file-based licensing model to a new cloud-connected licensing architecture. For most administrators, the migration itself was straightforward. The biggest surprise came afterwards, when familiar licensing metrics such as licenses in use, licenses available, and peak license usage disappeared from the Citrix License Server. The answer is no.

Choose a group when adding monitors

We’re making it easier to organize your monitors from the moment you add them. Previously, clicking Add would immediately add a monitor to your board. If your board already contained one or more groups, new monitors were automatically placed in the Ungrouped section, requiring an extra step to move them into the correct group. Now, clicking Add opens a list of your monitor groups, allowing you to choose exactly where the monitor should be added.

UptimeRobot has acquired IsDown.

For 15 years, UptimeRobot has answered one question for millions of people: is my site up? Today we’re taking on a related question that’s become just as important: is everything my site depends on up? We’ve acquired IsDown, which tracks the status of more than 6,000 cloud and SaaS providers in one place. Here are the details on what it is, why we bought it, and what we’re building with it.

Your AI agent can now set up uptime monitoring. No signup required.

We’re happy to introduce you to the first agentic uptime monitoring setup! Now your AI agents can continue their coding, testing, and deploy flows into setting up the monitors, including a free account. The agent submits your site’s URL and your email, you confirm with one click in the email you receive, and you have a working monitor plus a free account. No registration form, API key, or dashboard configuration needed.

Aiven for ClickHouse 26.3 LTS: Full-Text Search, Async Inserts, and Materialized CTEs

Aiven for ClickHouse 26.3 is now available in Early Availability. This upstream Long-Term Support release makes full-text search generally available, enables asynchronous inserts by default, introduces materialized common table expressions, and brings a wide range of JSON and query-performance improvements. The upstream 26.3 release includes 27 new features and 40 performance optimizations.

Who Owns Deployment Governance? Structuring Accountability in the AI Era

In this series, we have talked about how generative AI is shifting the landscape of software creation. In The New Software Creator, we explored how AI expands who can write code. In When Anyone Can Build Software, Deployment Governance Is What Keeps It Safe, we looked at why the deployment pipeline is the ultimate control point. Finally, in Security at Scale: What Changes When Everyone Can Deploy, we dug into the technical realities of patching, container hygiene, and identity management.

AI-Powered Spacecraft Operations with InfluxDB 3

Summary The InfluxDB satellite telemetry demo is a live mission-control application that monitors a simulated fleet of 12 satellites in real-time. It shows how the InfluxDB 3 Processing Engine can detect anomalies as data is written, enrich time series data with third-party data, and power a grounded AI agent using the InfluxDB 3 MCP server to investigate and explain fleet health.

Shipped: Catch a broken regex before it breaks your rules

Let’s say you want a Matches condition that picks up “prod”, “PROD”, and “Prod”, so you write ‘Matches: (?i)prod’ and check it in an online regex tester before publishing. It looks fine. Python accepts it, and so does JavaScript. Dimension Studio used to accept it too, and the rule is published. Then your data stops updating. The new pattern is what’s keeping it from materializing, but nothing tells you that.