Leading industry analyst firm Forrester recently published research titled The Forrester Wave™: Artificial Intelligence For IT Operations, Q4 2022. This is Forrester's summary of the report: You can find my original post regarding this Wave here: "Unsolicited Opinions About The Latest Forrester Wave on AIOps, Part 1." In this post, I’ll provide context on some of the events that led up to this Forrester Wave. These are my observations and opinions, not Forrester’s.

Leading industry analyst firm Forrester just published The Forrester Wave™: Artificial Intelligence For IT Operations, Q4 2022. If you're not familiar with Forrester Waves, they're similar to Gartner Magic Quadrants. However, one advantage of a Wave versus a Magic Quadrant is the Wave provides clients a way to customize the evaluation to suit their use cases.

As mobile networks evolved to 4G, network elements transitioned from hardware-based, often with proprietary chassis, to virtualized network elements. Communication service providers often implemented such technologies through private cloud infrastructures based on different flavors of OpenStack. On the other hand, 5G introduced microservices-based deployments with a service-based architecture.

In this video, I explain what topology is and why it’s critical for the success of AIOps projects. Simply adding machine learning to event correlation has proven an ineffective approach for root causing IT issues in environments of any size or complexity. If you’re considering different approaches to AIOps, there are two questions you need to ask about topology. This brief video will arm you with those questions and will help make your AIOps project(s) successful.

In this video, I explain the key difference between Generation 1 and Generation 2 AIOps platforms. As organizations develop strategies for implementing AIOps and as they consider different vendor approaches, it’s critical to understand the differences between those approaches. This brief video will help arm you with a key question you need to ask to easily identify the difference between Gen 1 platforms and Gen 2 platforms. It’s all about the types of data being collected.

In this video, Sean McDermott of the Find Flow podcast sits down with Ani Gujrathi, chief technical officer for Zenoss, and myself. We dive into the original approach to AIOps, how that has evolved, and how it continues to evolve. We start by exploring the entire purpose of AIOps — figuring out how to accelerate problem resolution in modern, complex IT environments while dealing with the pervasive problem of monitoring tool silos.

In this post, Pad Warrier, product manager at Zenoss, interviews Natalia Bakusevych and Carl Camera about the Zenoss design system. A beautiful user experience is the result of a purposeful, principled, and process-driven approach that begins with customer discovery. Natalia and Carl describe Zenoss' continual evolution with before and after examples that highlight increased productivity and efficiency for both Zenoss and our customers.

Imagine finding yourself doing everyday activities such as buying a soda pop in your favorite grocery store or analyzing your finances on your mobile banking app. You may drink your beverage and continue to enjoy your day. You may finish your task in an exceptionally ordinary fashion. You may also discover that your investments grew a tiny percentage since the last time that you reviewed them.

Last week, we announced that we are sunsetting Zenoss Community Edition, which was previously called Zenoss Core. (The title of this blog post refers to it as Zenoss Core, as that was the name for most of those 15 years and is the name by which most people know it.) Zenoss Community Edition was a free, on-prem monitoring tool the company made available for over 15 years, which had been downloaded millions of times. Zenoss Community Edition version 1.0 was released Nov. 15, 2006.

In the past, troubleshooting an IT service issue could be quite simple. For example, an application disruption could often be isolated to a physical server or small group of servers that neatly fit into the domain of a single team that managed the company’s servers. However, with the dynamic landscape in modern IT environments, this is very rarely the case. Over time, you accumulate IT systems, which usually means you deploy tools to manage them.