When choosing a IT Monitoring tool, you should pick only one. If you have more systems, try to replace them, even though the process is painful. Select a tool that is based on the functionalities that you are looking for and aligns with your technical and business needs. The CIO thinks that the SLAs, the reports and getting a text message if the servers go down is important. The CIO is also worried about the budget and is considering the total cost of ownership. You just want easy deployment, the GUI to be top of the line and want to be able to view your monitoring in an app and on the web. You can both get what you want. Don’t compromise.
It was clear that IT deliverability and performance directly affect the business of Company X. Everything from email and servers provides the tools for this international Online Gambling Company. If the website goes down no customers will lose their money and the house won’t win. The company is large and the setup is complex. The systems administrators at the different locations at Company X has had too much freedom, according to the CIO. Some locations have sub-par systems, others are seeing vital IT personal changing jobs. The CIO makes the decision to evaluate one Enterprise IT Monitoring tool to rule them all. The IT infrastructure consists of multiple datacenters with more than 30 servers each. The suite needs to monitor SQL, disk space, memory, applications, hosts (up or down via ping), switches, email service and more.
When selecting OP5 Monitor Company X considered functionalities, ROI and how easy it would be to move from the Open Source Solution that was most common among the company’s datacenter locations. The unified dashboard was a big plus according to the CIO. Whilst considering costs they took into account hardware, maintenance, license, configuration and training. The configuration was done remotely and on-site with help from the OP5 Support team and the Professional Services team. The training was completed online and the OP5 Knowledge Base was a great help.
During the implementation the most important elements in the IT Infrastructure was set up first to figure out where the level of alarms should be set and who should get the alarms. The alert system was integrated with the ticketing system and the tickets now go to the most relevant support level and area. Furthermore, the main objective was to solidify the communication and information by pulling it all into one tool and to get an overview of the Enterprise IT Infrastructure. This lead to some very handy automations and reduced both incidents and the time to resolve them. Fewer tickets are handled quicker. The CIO gets the reports and has not gotten a “panic” text message (yet). Company X is even thinking about OpenStack as the next step in regards to handling their server environment. Monitored by OP5 off course.
Could we help you and your datacenter? Feel free to reach out!