NinjaOne (formerly NinjaRMM) is a security-oriented remote monitoring and management platform. It allows for manual customization as well as scripting and automation.
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
NinjaOne
ScienceLogic SL1
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
NinjaOne
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
NinjaOne is a subscription service with a charge rate per month. For more detailed pricing information, contact NinjaOne directly to request a demo or to start 14-days free trial.
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.
NinjaOne has been amazing in getting patching done. What has put it above and beyond though is its scripting. It natively works with batch, powershell, and shellscript. This means custom scripting is simple and fast. Some times, especially with shellscripts, they do not run properly but in comes direct access to the different tools from the computer screen. Being able to connect to a system using powershell, CMD, or Shell means you can directly input commands and not rely on a script for those one off issues.
Before starting anything in the dashboards and indeed in the data collection, careful thought, design and planning is essential before starting. All that effort is worthwhile as developing powerpacks and dashboards is then much clearer and straightforward. 1. When we needed to monitor an application that comprised of several devices and network components, it was easy to set this up and, after a little training, easy for the operations team to use it. 2. When we needed to monitor part of a cloud it was not so easy to configure, but once that was done, it was very easy to use for the operations team as it followed the same style as the application monitoring.
Dashboards have limitations in a couple of large enterprise use cases. New UI appears to be addressing these as it matures and resembles techniques seen in other enterprise tools
Percentiles and baseline / deviation calculations on standard metrics are not what we've seen in the past from enterprise tools. However, more complex anomaly detection is now available as an advanced function
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).
Ninja's interface is clean and simple. Overall usability from an interface perspective is good. Some items, policies and scripting for instance, are a bit cumbersome and it's really not clear how to implement with a best practice mind-site. Ninja RMM got the job done for us but as we pushed our needs more into automation and efficiency we felt it wasn't keeping up with our speed of growth. There is definitely usability in the product, and it will get the job done, but there are other RMM's out there that fit better in our business.
Product is capable of monitoring different technologies like OS, MS Infra apps, cloud services, Databases, network etc... this can be a single solution for most of the technologies end to end monitoring
It is more flexible for customization and support is good
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)
Support has been very responsive and my account rep Brian K. has communicated with me continuously making sure we had everything we need. Not like other MDMs where they sign you up and that's the last you hear from them. NinjaOne makes sure you use the product to its best application and you are successful and continue as the product features grow.
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.
On our side (students), we had a number of teams who were provided the deep developer training. Of those students, the customized training provided a complete, 5 day training which enabled the deployed platform team to successfully deploy and mitigate user-experience issues for the vast majority of our end-users, including some of the teams who attended the developer training.
The knowledge kept pace with the class and sped up / slowed down (within the time constraints) as needed throughout the course.
This was developer to developer training and for those students who were developers the training worked well. For those who were just coders it probably worked less well as some of the topics still do not apply (a function of our course outline specification based on our knowing nothing).
Due to problems in sequencing we did the developer course BEFORE the admin course and realized that our requested ORDER was wrong.
The onsite admin course was much better received and led to deeper understanding of the developer course held a few weeks prior.
As far as Implementation is concerned, i think I never ran into any major trouble (whatever it is, it's just local infrastructure specific). Once all your NW ports and connectivity is in place, it won't take much of your time to install the product. configurations are also easy to complete. VM configuration takes no time, except the environmental configuration which is company specific. Onboarding is easy via SNMP based monitoring.
NinjaRMM was easier to work with, better on price, and had less complicated software. Install was simple and use is a breeze. All the other vendors cost more and didn't have everything I wanted all in one place. Also, I like to support local companies when possible or at least work with companies in the same time zone, which they are both.
As I stated earlier, SL1 seems to be best used for Servers and Network Storage devices. It doesn't seem to be a direct replacement as SL1 doesn't have a configuration management piece, visual maps are very crude and not user-friendly, and the building of the maps is not intuitive, nor has the functionality of Solarwinds Topology Mapper.
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.)
after all of our production devices are onboarded to SL1, we will be able to bring network monitoring in-house instead of it being outsourced as it is now
I am Engineer/SL1 user only, therefore I cannot comment on ROI or similar numbers
