With so many IT vendors claiming they provide AIOps platforms, how do you understand the differences between them, and decide what flavor of AIOPs to choose for your organization? Join us in a CTO Perspective discussion with Elik Eizenberg, CTO and co-founder at BigPanda, to find the answer. Read the skinny for a brief summary, then either lean back and watch the interview, or if you prefer to continue reading, take a few minutes to read the transcript. Enjoy!

AIOps isn’t an IT magic wand, but it sometimes works like one. One day last fall, our IT ops team was heads down on a major cloud migration project. Meanwhile, ServiceNow Event Management detected a high volume of alerts from the monitoring system—600% more than usual. That typically means a lot of unplanned work for our IT team, not to mention a delay in our cloud migration schedule.

In this blog, we will walk through the scenario of sending or E-bonding ServiceNow incidents to 5 destinations simultaneously, using Robotic Data Automation and AIOps Studio. E-bonding refers to a scenario where data is delivered (one-way) or synchronized (two-way) between two or different systems, which are typically under different administrative boundaries. E-Bonding term originally appeared in Service Provider and Telco space (see: ATT E-Bonding).

I don’t know about you, but April traveled at the speed of light. A blink and it happened. Our teams have been working at the same speed throughout one of our favorite months of the year. With an incredible amount of updates, we’ve made our product even more transparent and easier to use. It’s not just our world-class documentation that enables you, it’s also the in-product visualizations and enablement that help guide you without you even realizing it.

Coined by Gartner in 2016, the term ‘AIOps’ refers to the combining of big data AI and machine learning to automate and improve IT operations processes. Back then, this very broad definition led to some confusion, with different IT vendors characterizing AIOps differently, depending on what they were actually offering.

Implementing any IT project requires time, planning, and effort and AIOps probably requires even more planning and stakeholder involvement, because of the breadth of coverage and potential to bring profits to multiple IT domains/functions (ex: ITOps/ITSM/NOCOps). Customers have high expectations from AIOps, but, even after taking such major projects, most AIOps vendors are only able to support a few core AIOps use cases, which severely limits the utility and potential of AIOps.