ManageEngine's OpManager is network performance monitoring software.
$95
per year
ScienceLogic SL1
Score 8.8 out of 10
Enterprise companies (1,001+ employees)
ScienceLogic is a system and application monitoring and performance management platform. ScienceLogic collects and aggregates data across and IT ecosystems and contextualizes it for actionable insights with the SL1 product offering.
N/A
SolarWinds Server & Application Monitor
Score 7.7 out of 10
N/A
SolarWinds Server & Application Monitor (SAM) delivers application and server monitoring capabilities. SAM allows for self-service for easy setup, 1200+ monitoring templates, and customization options, as well as integrate with other SolarWinds products.
N/A
Pricing
ManageEngine OpManager
ScienceLogic SL1
SolarWinds Server & Application Monitor
Editions & Modules
Standard Edition
$245
for 10 devices
Professional Edition
$345
for 10 devices
Enterprise Edition
11,545
for 250 devices
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
ManageEngine OpManager
ScienceLogic SL1
SolarWinds Server & Application Monitor
Free Trial
Yes
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
Yes
Yes
No
Entry-level Setup Fee
$245 per installation
Required
No setup fee
Additional Details
—
ScienceLogic SL1 offers four tiers:
SL1 Advanced – Application Health, Automated Troubleshooting and Remediation Workflows
SL1 Base – Infrastructure Monitoring, Topology & Event Correlation
SL1 Premium – AI/ML-driven Analytics, Low-Code Automated Workflow Authoring
SL1 Standard – Infrastructure Monitoring – with Agents, Business Services, Incident Automation, CMDB Synchronization, Behavioral Correlation
To get pricing for each tier, please contact the vendor.
Compared to the Solarwinds products ManageEngine OpManager is much easier to configure and use. It's also vastly cheaper!
Something like the Solarwinds suite of applications is incredibly complicated and difficult to configure. ManageEngine OpManager is very straightforward to …
Quick deployment, easy administration, customization flexibity, AIOPS capabilities like anomaly detections, Correlations etc.. are good and quick support on tech issues
ScienceLogic is more feature rich and relatively easy to get into. For example, it is far superior to OpManager and PRTG in terms of features and capabilities. It is much easier to pick up compared to Zabbix. To enjoy a lot of function/features of ScienceLogic, you don't …
In general EM7 stacks up well to other commercial products and open source products. Personally I have worked with well over 25 or 30 different monitoring products (probably 50 if you include product evaluations) and would rate EM7 around the top 75% as it applies to features …
I've tried other monitoring systems before. Nagios and the free version of PRTG have been used in the past. Even had OpManager once. Spiceworks always got me close. I've worked at associations, non-profits, and for-profits. Everyone wants the most they can get for as little as …
SolarWinds is much more robust and has a ton more built-in application monitors available out of the box. The Dashboards are easier to manage and have a ton more detail. The event engine in SolarWinds has a ton of functionality and there is a built-in Message Center to look …
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
For Windows, the issue is in higher resource consumption related to WinRM monitoring, which provides better options then the SNMP monitoring, which on the other hand is less resource intensive. The problem is also with support for OS with other than English language.
It is a well-suited software for monitoring and surveillance of your deployed nodes. The error-readability and filter options for filtering out logs and errors could be improved. But overall, it has a good UI design, is user-friendly, and is very easy to learn and access for new users.
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.
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.
Dashboards are quite old and are of Iron age. Need to have AP2 dashboards only instead of AP1 and consistent new design across all functionalities.
Reporting is not improved since Y2020 and need to revamp completely. Need to integrate Dashboards and Reporting. PowerBI Like functionality to be given OOTB. Reports should be extracted in Excel, PDF, HTML and should be heavily automated.
Create and Open APIs for basic and advanced monitoring data extraction.
Topology based Event Correlation and Suppression should be improved drastically. Need to identify critical network interfaces based on Topology and monitor them. Basic customization of Dynamic App and/or Powerpack to exclude/include certain metrics/events to be permitted OOTB instead of customizations.
Integration with ServiceNow to be improved and to be taken to next level. Automation Powerpack should be made available OOTB as part of base product and to be priced attractively.
Take product to next level where we can monitor actual impacted IT or Business Service instead of metrics and events BSM and Topology map to be auto discovered and identify the network dependencies and alternate paths automatically instead of manual creation of BSM.
It is simply because of all the best possible autonomy solutions it is providing and getting better day by day. Using AI and Devops along with handy automation, The monitoring and Management of devices becomes much easier and the way it is growing in all the aspects is one the best reasons too. Evolution of the SL1 platform in the autonomy monitoring and management is quite appreciable.
We are heavily invested in Solarwinds products for a reason. They are generally easy to setup and run with, requiring only some interfacing with support or help articles on rare occasions. They do what we bought them to do and we can't ask for more.
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.
The core functions are there. The complexity is due to the complexity of the space. The score is based on comfort (I no longer notice the legacy UI) and the promise that I see in the 8.12 Unified UI (a vast improvement). It is also based on the fact that with 8.12, you can now do everything in the new UI but you still have the legacy UI as a fallback (which should now be unnecessary for new installations)
SolarWinds Server & Application Monitor is quite easy to use and super versatile. It allows you to do just about anything you can through premade templates or through scripting. You can use an agent on the servers if you want to, or you can monitor through WMI or SNMP credentials. You can customize thresholds for alerting quickly, and you can configure alerts to be as complex or as simple as you want.
SL is always there and online when you need to get info from it. The only times when SL was not available in our own data center, was when network links from out side of the data center was down and those links were not in our controll. Having a central database and people accessing it all over the world, may put a bit of constarin on the performance of the dashboards when reports gets generated, but that is far and few n between.
SceinceLogic SL1 architecture helps the platform to give a top-notch performance in every respect, Data collection to reporting happens very smoothly. With the new user interface pages load much faster. Individual appliances carrying the individual task ensure things are working without lag. Integration with ticketing tool(SNOW) is well managed by the ScienceLogic, no issue or much delay has been observed while interacting with an external tool.
The graphical interface and the performance of the database leave a little to be desired, they could be better explored.Some functionality and screens do not work well depending on the browser used. The integrations never had any problems or caused crashes in other systems.
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.
So far, it's good as part of my overall experience, except for a couple of use cases. The support team is well knowledgeable, has technical sound, and is efficient. When support escalates to engineering, the issue gets stuck and takes months to resolve.
I think there was only a couple times I had to open a support case for SAM and one time they got multiple engineers on the phone to get a better idea what I was trying to monitor and was able to point me in the best direction to monitor that system.
It was good, Do the online training first and understand it and you will get the most out of the in-person training that way. This also takes you to an advanced level which is very good and the training as been overhauled once again along with new product coming in such as Zebruim / Skylar, worth going through again if it a while back that you first did this.
There are a lot of educational materials and courses on the SL1 training site (Litmos university). However the recording quality is sometimes not very good - screen resolution is low. There is a lack of professional rather than user-oriented documents and there are mistakes in documentation and education is not well structured.
Implementation is smooth if we are to just support the out-of-the-box features available in ScienceLogic. For any custom requirement, having to go to SL1 Professional Services is the worst part of procuring this suite. And more often than not, SL1 Professional Services also ask to raise feature request. So, you subscribe to Professional Services to only hear back from them that "This feature is not supported and needs to have a separate feature request". At times frustrating.
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".
Science logic SL1 is so user friendly and it's really easy to navigate between function. I would recommend Sciene logic SL1 to all of them who are looking for really useful monitoring tool and expecting easy way of managing it.
Nagios requires far more manual work to configure than SolarWinds does, though that also encourages customization and perfect-fit solutions. Nagios also requires far, far fewer resources to run than SolarWinds: SolarWinds wants great gobs of memory and disk, while Nagios is refreshingly humble. Nagios starts working from the first minute, too, whereas SolarWinds needs lots of set-up time.
Our deployment model is vastly different from product expectations. Our global / internal monitoring foot print is 8 production stacks in dual data centers with 50% collection capacity allocated to each data center with minimal numbers of collection groups. General Collection is our default collection group. Special Collection is for monitoring our ASA and other hardware that cannot be polled by a large number of IP addresses, so this collection group is usually 2 collectors). Because most of our stacks are in different physical data centers, we cannot use the provided HA solution. We have to use the DR solution (DRBD + CNAMEs). We routinely test power in our data centers (yearly). Because we have to use DR, we have a hand-touch to flip nodes and change the DNS CNAME half of the times when there is an outage (by design). When the outage is planned, we do this ahead of the outage so that we don't care that the Secondary has dropped away from the Primary. Hopefully, we'll be able to find a way to meet our constraints and improve our resiliency and reduce our hand-touch in future releases. For now, this works for us and our complexity. (I hear that the HA option is sweet. I just can't consume that.)
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
Once a powerpack is developed and configured for a device for one customer, it is easy to deploy the same powerpack on a second customer estate and configure specifically for that customer without having to reinvent the powerpack. This saves time and therefore money.
Once the customer estate tuning is complete, the Operations team have come trust the alerts. This is especially true when transient or self-correcting alerts are automatically cleared without ops team involvement, but a record is still available for audit and debugging purposes. This saves time and therefore money.
When setup correctly, it provides good visibility into applications, devices and whole customer estates. This saves time and therefore money when issues arise.
