SolarWinds Remote Monitoring & Management (RMM) is a cloud-based system monitoring offering for Managed Service Providers. It provides a full monitoring and management suite, including automation and threat detection capabilities, and can integrate with other SolarWinds products.
N/A
ScienceLogic SL1
Score 8.6 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.
$7.50
per month per node
Pricing
N-able N-sight RMM
ScienceLogic SL1
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
N-able N-sight RMM
ScienceLogic SL1
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
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.
SolarWinds patch management has had issues over the years. Sometimes requiring manual intervention to get resolved. The UI [with N-able RMM (formerly Solarwinds RMM)] makes it easy to see status of systems and identify any alerts easily. Remotely monitoring the status of servers/computers. Managing the systems, patching, systems maintenance and remote support.
Appropriate if you are setting up a monitoring suite in new Infrastructure Environment. Definitely NOT suited for Migration Projects. ScienceLogic SL1 cannot cater to a lot of monitoring requirements which already would have been configured in old monitoring suite. Plus, limited support for customizations and having to go to "Feature Requests" route makes in extremely complicated.
It provides fantastic remote access capabilities. The Take Control tool gives us a robust platform that is capable of remote controlling almost any endpoint we need to and the chat, file transfer, and screen recording tools are all exceptionally useful.
SolarWinds RMM is particularly useful as a single pane of glass solution that allows us to monitor and manage thousands of endpoints across dozens of different clients. It does a solid job of allowing us to sort, organize, and filter based off of who and what we want to see at any given time.
Due to its client based nature, the platform excels at in-depth monitoring of services, event logs, and the functionality of systems with custom script checks.
More freedom to create custom dashboards as on the previous versions we could do much more
The Performance TAB windows is too small and cannot be resized or maximized when looking at reports for "Overview", "File System" and any of those items.
There are not enough widgets to create stunning dashboard in AP2
We migrated away from our 20-year-old homegrown solution and have no back-tracking capability. ScienceLogic is demonstrating new capabilities that we would not have been able to do on our own using our legacy system. We understand the capabilities of competitors based on our bake-off selection where ScienceLogic won on capabilities and future near-term potential (expandability, platform growth). We know that those competitors are not really close to where we have been able to push ScienceLogic (as a partner).
The interface is easy to navigate. Setting up policies is straight forward. The antivirus and web filter are simple and exceptions are easy to make. Upgrading the agent is made simple and creating scripts is made fool proof. (Well, almost)
We use ScienceLogic SL1 in our organization to serve effective monitoring solutions to our external customers. Our customers depend upon us for critical events/alerts related to their IT infrastructure gears and using SL1, we're able to provide them with a proactive monitoring solution that resolves an issue before an impact is noticed by the customer. There are very few monitoring solutions that can cater to a variety of Cloud platforms like Public Cloud (AWS, Azure) and private cloud simultaneously and SL1 addresses this business problem very well
Science Logic SL1 provides the option of Distributed deployment where multiple instances of each appliance can be deployed to manage the load and availability. SL1 provides a High Availability feature for Database Servers and Data Collection. If one of the Data Collectors in the collector group fails, it will automatically redistribute the devices from the failed Data Collector among the other Data Collectors in the Collector Group. The high availability feature for the Database server ensures that SL1 performs failover automatically to another server without causing the outage to the application.
The performance is entirely dependent on the complexity of the environment/network being used to host the platform. Outside of those factors, the platform runs very efficiently and quickly out of the box. We have integrations with other platforms and neither seem to take a hit from our moderate API usage. Any issues with performance would be experienced by choices made in infrastructure or complexity of things built by the customer to display in the GUI (overly complicated and cluttered dashboards for example)
The ease of use, full functionality, reliability and excellent support.[N-able RMM (formerly Solarwinds RMM)] gives users a full suite of tools with a single installable file. Unlike standard tools, you don't have to install several different executables to be able to have fully protected end points.
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.
When I joined our company, I did not know about the in person training at firts. Logging onto the SL University, I realised that there were different sessions being held at different times throughout the year. The training itself was good, but being in a different time zone, made it difficult to attend, but the sessions that I attended was great!
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.
Love to use Science logic tool as our first monitoring tool to provide services to the customer. Auto restart feature in Sl1 will allow us to get event when those crucial services has not started after server reboots and also minimize the P1's that we have as a result of that.
SolarWinds definitely is the the most ready out of the box as far as getting is up and running and you can start using it where other system go from need ing a little setup like importing MIBS to completely needing to configure the system. As far a performance once things are up and working I feel they all do a good job at basic monitoring and management. The difference is that SolarWinds does a good job at having things templated but allows you to customize some attributes. If you are want to make major customization for alerts and monitoring and other things SolarWinds is not the best option. But, then again, you will not need a team just to manage the system.
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.
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.)
The ROI is immediate for us. The advanced alerting alone makes this product an ace in our bag. The confidence you have in your network is wonderful.
Another big ROI we get from the advanced alerting is the peace of mind that our engineers feel. We are a 24/7 shop, so being on-call goes from being hectic to extremely manageable.
The only negative I can honestly say is when the time comes to patch the product. Micro-patches are easy enough, but jumping versions can be a bit taxing.
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.
