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.

It's always good when it's open to more platforms, with even more integration, especially ticketing solutions like ServiceNow. I have built integrations with some other tools, so this is a point for future development, unless they have already addressed it.

There are some lag time and connectivity issues. It is not an OP5 Monitor issue but due to some network issues. We do not get performance reports properly, which needs improvement.

The web-based UI is functional. It's in need of an update. There is a large, ongoing project to release a redesigned web interface, to which we are providing feedback. That's going to be really exciting. OP5 has always been web-first. There are no clients to install. It's always just a web interface.

There are a couple of things in need of improvement that are major. Some of them are on track. IT environments today are in constant flux. This is driven by the newer cloud technologies such as Kubernetes and Docker, etc. The whole Nagios-based monitoring system that OP5 is created on top of, is based on a host-service model. There is a need for a strategy on what to do with more dynamic environments. I know that is a fluffy description, but that's one key thing. There is some cool stuff going on in that direction. We, as a partner, are helping a couple of clients integrate with cloud environments, which is really cool.

Right now, we're focusing a lot on automating the configuration of monitoring systems. That's something that needs improved APIs. 

Finally, it needs a unified, central way to manage and configure agents. That would be a key feature.

The user interface is not what we are used to these days, and should be improved. For example, the dashboards are easily customizable to a certain degree, but not as well as a product like Tableau. From the visual aspect, it could look a bit fancier.

Functionality-wise, this product is missing the NetFlow monitor.

They need to improve the dashboard interface.