Operations | Monitoring | ITSM | DevOps | Cloud

Earlier this year, we introduced Ivanti Innovators Hub to bring together support, knowledge and community into a more unified experience. That launch established a strong foundation for a more effortless and predictable experience. Now, we're building on it with new enhancements designed to make the Hub more personalized, connected and relevant, with integrated learning opportunities, stronger community engagement and more tailored experiences.

How many backup jobs completed successfully in your environment last night, and how many of those systems could you bring back inside the window the business agreed to? Most backup consoles answer the first question well. They report job status, completion time and volume written, then roll it into a reassuring compliance summary. The second question needs different evidence, usually missing from that screen. The distance between those answers shows up during the recovery attempt.

Why does a ClickHouse cluster report every node as healthy while inserts start failing and dashboards go stale? Most often the failing subsystem was never represented in the metrics anyone had on screen. A node answers its health check while its replication queue has been growing for hours. ClickHouse breaks in specific, repeatable ways. Parts accumulate faster than background merges can consolidate them. Coordination drops quorum and every replicated table quietly turns read-only.

Today, I’m very happy to share a new report, Bridging the AI Acceleration Gap, from Harvard Business Review Analytic Services and sponsored by Nexthink. It examines how employee-led AI adoption is reshaping the role of IT—and what technology leaders need to do next.

ITSM best practices are standardized ways to design, operate, measure, and improve IT services. For enterprise teams, the most important practices are clear service ownership, consistent incident and problem management, risk-based change controls, trustworthy configuration data, standardized request fulfillment, outcome-based metrics, governed automation, and continual improvement.

Ask an IT administrator what they mean when they say they need a Configuration Management Database (CMDB), and more often than not, they are describing something else entirely: knowing what assets they have, who is responsible for each one, and what breaks if one of them fails. That is the job of the Asset Management Database (AMDB), the lifecycle record built to answer exactly those questions.

When did anyone last open your network diagram and trust what it showed? A diagram drawn in a static drawing tool is accurate on the day it is saved. One quarter, two circuit upgrades and a hardware refresh later, it describes a network that no longer exists. Nothing warns you that this has happened. The file still opens, still prints, and still gets attached to change requests, which is what makes it risky during an incident.

When an application slows down, how long does it take to confirm whether storage caused it? The answer depends entirely on whether anything is collecting from the array itself. The server dashboard reports healthy CPU and memory, the network graphs look clean, and the array holding the data says nothing at all. Storage failures announce themselves late.