IT infrastructure: Inventory before AIOps

In addition, there is another aspect that he believes is too often overlooked: “Ultimately, the introduction of AIOps also reveals potential on the employee side. The fewer manual interventions in the infrastructure are necessary, the more employees can focus on things that really require their attention. For this reason, I see the use of open integration platforms as helpful in making automation and AIOps usable across different platforms.”

Storm Reply’s Henckel even sees AIOps as a tool for greater harmony: “The introduction of AIOps also means an end to finger-pointing between departments. With all the different sources of error — database, server, operating system — it used to be difficult to pinpoint the cause of the error. AIOps provides detailed analysis across all areas and brings more harmony to infrastructure evaluation.”

Overall, experts note a wide variation in the degree of maturity in the implementation of AIOps. Particularly with regard to “naturally” evolved IT landscapes, you should plan carefully and, above all, not neglect the basics to create the necessary database in the first place. A clearly defined trigger that signals the pressure to act at the decision-making level is most effective. Instead of a “big bang” approach, it is better to introduce AIOps in a targeted manner in areas where there is an acute need, to quickly achieve visible effects and generate initial benefits, for example through more efficient and secure processes. All of this not only helps to build internal acceptance but also facilitates support from management.