OP5 Monitor Reviews

The solution is useful for tweaking. However, there have been some negative experiences, such as limited report capabilities. The only report available is in PDF format, making it difficult for teams managing multiple servers to extract data in Excel format. The speaker recommends that the team improve the report capabilities to better serve users. If there are corrupt files the data can be extracted from them. Anyone who wants to see the performance of memory usage, such as whether it's at 80 to 90 percent, can use this tool. However, other tools can provide this information in two minutes, this tool is more time-consuming and the report it provides is not very effective for practical use. When it comes to reports, the tool falls short. During a recent call, it was noted that while the company has distributed servers across the globe, only the master server can accommodate the reports and events, causing delays. If other servers experience issues, the team cannot view the reporting or tag things, such as for troubleshooting purposes. If this aspect was improved it would be an excellent tool.

What is our primary use case We use OP5 Monitor to monitor servers, databases, storage, filers, storage devices, network devices, and log file monitoring. What is most valuable? Its open-source environment is accessible to everyone. We use plugins and scripts to monitor and can use…

The setup was straightforward for our purposes, but the more you want to monitor, the more you have to fine-tune things. This is true for all products. You get some basic functionality and basic monitoring with minimal effort, but if you put in more effort, you get more granular details out of it. It deployed pretty fast. In one day you can be up and running with basic monitoring, but there were new features added to the system. If you need more, you will want to fine-tune the cluster and the way it monitors things. In terms of the deployment process, you needed to add a virtual machine or a physical machine if needed. You then install the application, provide credentials, and that's it. You then just need to populate and you can do auto-discovery to populate it, although I'm not sure how the auto-discovery works. Our approach was to use the CMDB. We added the devices and elements that we wanted to monitor based on our CMDB. I had two people onboarding it, but they did it as a side job, not full-time. It depends on how you set it up, but if you do it yourself, two people are sufficient to address it. They have to have some technical knowledge.