We utilize OP5 Monitor in both on-premise and cloud environments. We have a master OP5 Monitor for our primary clients, and other deployments located globally that are integrated with the master. Our monitoring includes databases in both public and open-stack clouds, covering both on-premise and cloud deployments. The workload, including the VM workload, is similar across both environments, and we do not encounter any monitoring issues in either. Therefore, OP5 Monitor is effectively used in both on-premise and cloud environments.

We utilize OP5 Monitor to monitor various aspects of our servers, including CPU usage, memory usage, disk space, and specific URLs. In the cloud, we monitor up to 8,000 to 10,000 servers worldwide. While the tool is capable of monitoring network performance, we specifically use it to capture server-related data.

We have a set of standard monitoring parameters that we follow, which include tracking server performance metrics, such as memory usage, disk space, processor usage, etc. In addition to these standards, we also monitor databases by tracking important database terms such as database logins, read rate ratios, and write rate ratios. We are also capable of providing custom monitoring solutions as per the specific needs of our internal customers.

While standard monitoring parameters are deployed across all servers, application-specific monitoring requirements such as monitoring of URLs or databases are handled on a case-by-case basis as per the requirements of the individual customer. This approach is driven by the fact that not all customers require the same monitoring solutions.

We used it for network monitoring, including utilization and bandwidth.

We use OP5 Monitor to monitor servers, databases, storage, filers, storage devices, network devices, and log file monitoring.

Most of our clients are IT operation departments in larger organizations. They use OP5 Monitor to get an understanding of what's going on in their IT infrastructure: everything from network and server infrastructure to applications and specific metrics inside applications. It's mostly operational stuff.

For a standard IT department the types of applications they monitor would include, infrastructure-wise, everything from the network, service virtualization environment, VMware, cloud, and everything that runs on top of that, like databases, web servers, financial systems, payroll systems, and internally developed systems.

We have hospitals who use it for systems where they keep track of ambulances. We have a cruise line as a customer that uses it on systems that keep track of the IT services onboard cruise ships. It could be used on cooling containers, temperature and environmental monitoring, redundant power, uninterruptible power supplies with diesel generators. Everything from smaller workshops to nuclear power plants are running the system. It's used by a very wide scope of clients.

The reason why a system like this exists and is needed in an IT operations department is to automate the process of getting to know if stuff is working or not. If you don't have this, you will have to physically inspect your servers; log onto everything and check what's going on, and you will have to do that frequently. If you do that manually, it's not going to work. And it's not going to be done with good enough quality. This monitoring system is a way to implement automated tests of all your responsibilities as an IT operations manager.

We use this product for our network monitoring solution.

Our customers are using the OP5 solution for monitoring. Our customers are using log management, but it's not the only part of the software that they are using. They are using all the features, and log management is one of the features of the software.  

We are working with its latest version.