ManageEngine OpManager vs Statseeker comparison

"The most valuable feature of ManageEngine OpManager is the management of the virtual machine and the host machine."

"The solution's most valuable feature is its ability to reach most of our network devices and get the most from them."

"I am satisfied with ManageEngine OpManager's monitoring features."

"The integration with the firewall monitoring, the security monitoring, is great."

"The features we found most valuable in ManageEngine OpManager are the probe server and reporting because they're pretty good features."

"We don't have to keep an eye on it; it has a good automation option, which keeps us informed. It gives very less false positives. Overall, a really great product."

"It is easy to use and deploy."

"OpManager can monitor network utilization, downtime, and services in real time."

"We are now able to easily track where problems are with bandwidth and port errors, rather than having to do a lot of diagnostics."

"Key features for us are custom reporting, 95th Percentile, and trend lines."

"It is fairly simple and easy to use as an all-purpose network monitor."

"This solution helps in terms of troubleshooting, and you can do capacity planning with it."

"This solution has helped us to proactively identify issues and push some of those fixes down to tier one."

"The graphics and trends are the most valuable for us."

"I like the fact that I can aggregate multiple interfaces into a single graph. It allows me to quickly the summary of traffic for multiple devices which is helpful."

"We are a smaller enterprise, but we're watching approximately fifteen-thousand switchboards with no problem at all."

"The integration with various OEM products could be simplified."

"The solution's reports need to include the number of applications consumed."

"We would like link monitoring included. At times we need to monitor those specific links closely."

"What I'd like ManageEngine OpManager to improve on is artificial intelligence. In particular, the machine learning feature should be integrated with the sensor flow. Doing this will give leverage, especially when you look at other products such as the Cisco DNA Center. When a switch goes down, I should be able to build on the correlation of other physical devices it's connected to so that I can integrate that with my CA CMDB. The ManageEngine OpManager team needs to draw a long-term roadmap where that feature becomes an integral part of the solution because right now, machine learning in ManageEngine OpManager is a long process. The solution doesn't have MLS search and I want to see ML being developed and applied for CA CMDB to greatly reduce the burden of tying everything. For example, if I have a data center switch that goes down now, I should know what server it's connected to, and when that switch goes down at twenty-four ports, I would get twenty-four alerts for different devices plugged in. I should be able to make a correlation that the major problem lies in the switch and not with the twenty-four elements connected to that switch. That is where machine learning should come into play and the ManageEngine OpManager AI should indicate "This is where the root of your problem is." It could be difficult, but this is a feature that should be improved or added to the solution."

"We encounter challenges in monitoring cloud services. I would also appreciate it if there was someone available to walk you through the documentation."

"If you have a ton of devices, it might slow down a bit."

"WMI and SNMP integration with the domain controller should be seamless"

"The initial setup is a bit complicated. It needs a technician who is very aware of the flow and how to officially set up the flow chart, etc."

"The interface could be more user-friendly and it would be nice if there were enhanced options for reporting."

"It could use more features on Netflow analyser, such as time series graphs and a single network export UDP port and UDP forwarding."

"The inclusion of configuration management features and SIP links would improve this solution."

"I'd say the interface could improve a little bit. I find with new users, I tend to have to spend a bit of time walking them through how to use the interface. It could be a little more user friendly."

"The main issue I've seen, in the last six months to a year, is when I upgrade I seem to be hitting bugs. The upgrade won't go smoothly and I have to engage support. These things happen when you upgrade, it's not the end of the world, but from a stability point of view, the only time I've so far, is during upgrades."

"I would like the ability to update the dashboard. I would also like the ability to access via an API. Then I could produce a dashboard that my C level can understand. This is just so they can go and refresh whenever they want to and see what things look like."

"I would like to see the solution incorporate diagnosis of the workstation."

"It would be nice if I could easily select individual interfaces."

"The price for ManageEngine OpManager is average."

"In terms of pricing, I would rate it a two out of five. It was expensive."

"It is reasonably priced."

"The initial cost is low and the add-ons are reasonable."

"It is not really expensive; it is nominal licensing."

"The licensing costs depend on the number of devices and accounts that are being monitored by the solution."

"ManageEngine OpManager has a three-tier licensing model."

"The tool's licensing costs are yearly."

"We pay a yearly maintenance fee of approximately $40,000 USD."

"We have permanent licenses so there's really no cost, other than ongoing maintenance. When I think about it, that's running us about $20,000 a year."

"Pricing is reasonable but licensing should unlimited."

"The yearly cost varies as per the number of devices being monitored. The cost for 25,000 devices is about $4500."

"This tool would probably be priced well if it had deeper NetFlow capabilities, but for our use case, in particular, we're only recovering ports after ninety days and looking at circuit congestion, it's pretty pricey."

"It would definitely be a yearly licensing cost, but I don't know what it is."

"The licensing cost is yearly and it's $5,000 to $8,000, I think."

"Up until we actually talked to Statseeker, and Statseeker came and gave us an enterprise licensing model for multiple accounts, I would have said the pricing was not good value. The fact they've come to the party now and given us a very good discount, I would say it's probably about right, the pricing they're giving us now. But the retail pricing, if I went out and, as a separate company, and asked for pricing for one account, I probably would say their retail pricing is not competitive. The fact that they've given us a discount now because we have multiple servers across multiple accounts, I would say that pricing is about right, but not their retail pricing. It's too expensive."