Manage Engine OpManager is better suited to serve server and network admins at organization to monitor their servers and network devices. It helps us with compliance with the reports available like utilization reports and capacity planning reports. It helps you to keep track of what all process are consuming the resources. It helps you in monitoring what is happening in your switches, routers and firewall
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
It measures the CPU utilization of hosts, the network bandwidth utilization of links, and other aspects of the operation
It often sends messages—sometimes called watchdog messages—over the network to each host to verify if it is responsive to requests.
Set Up Notifications And Reports.
OpManager offers a set of advantages that allow it to adapt to the needs of the company, guaranteeing effective monitoring of the application networks used in our organization.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Alerts has to be configured correctly otherwise unnecessary bombarding of alerts can cause inconvenience.
The server on which ManageEngine OpManager is to be deployed should have higher resources as monitoring a large number of devices may slow down the performance of the system.
Configuring the advanced features may require a learning curve.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
The rating I provided is based on the product quality, experience (I have been using OpManager for almost the last 4 years), and relevance of the information/response I generated through Manage Engine OpManager. I have also received good support from OpManager.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
At first, we were not able to add our Avaya switches to the configuration backup module, our partner tried to help, but they did not find the solution, we had one remote session with tech support of ME and they solve the problem.
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
During our competitive analysis, we found ManageEngine OpManager was not expensive compared to other vendors. At the same time, there was no compromise on the features such as customized reporting or configuring alerts per our clientele's unique requirements. These are our client words "Other vendors ask us to pay more $$$ for enabling additional email alerts".
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
I don't know if you can calculate ROI with a monitoring solution, there are more factors to calculate.
We found a really big problem with a network switch (faulty transceiver) in a trunk configuration with OPManager. this caused us serial troubles with the overall network stability.
We are loosing around € 3.000 to 5.000 per hour if our network is not working so this was a great help to fix this issue
Our label printers are really important to monitoring in our warehouse system, this makes OPManager a great solution for that
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
