Nagios provides monitoring of all mission-critical infrastructure components. Multiple APIs and community-build add-ons enable integration and monitoring with in-house and third-party applications for optimized scaling.
N/A
ScienceLogic SL1
Score 8.9 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
Pricing
Nagios Core
ScienceLogic SL1
Editions & Modules
Single License
Free
Single License
Free
No answers on this topic
Offerings
Pricing Offerings
Nagios Core
ScienceLogic SL1
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
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.
More Pricing Information
Community Pulse
Nagios Core
ScienceLogic SL1
Features
Nagios Core
ScienceLogic SL1
AIOps Features
Comparison of AIOps Features features of Product A and Product B
Nagios is simply a very configurable and rock solid monitoring engine. For these reasons I would recommend it to any IT professional in any medium to large organization where creating custom checks and programming ones custom needs into the configuration is practical. I would be more hesitant to recommend it as a first monitoring solution for a small business which is usually accompanied by a less experienced and/or more time constrained admin.
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's built by engineers for engineers so setting it up and configuring it is relatively complicated. It could really use a simplified configuration approach, or a GUI to set it up instead of editing config files.
I'd like to see the option to have service notification settings inherited from the host setting notifications. They have to be set up separately but they are often the same, so it would be nice to have less redundancy.
Creating powerpacks from scratch for new devices may be straightforward but will rarely be easy. Rewarding when completed, but not easy.
Developer documentation needs a rethink. While the information may be there (it isn't always) it is not easy to find. This is not helped by using different terms for the same things.
A developer console/dashboard for monitoring data collection from powerpacks instances without having to switch webpages or have to monitor multiple webpages.
We're currently looking to combine a bunch of our network montioring solutions into a single platform. Running multiple unique solutions for monitoring, data collection, compliance reporting etc has become a lot to manage.
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 Nagios UI is in need of a complete overhaul. Nice graphics and trendy fonts are easy on the eyes, but the menu system is dated, the lack of built in graphing support is confusing, and the learning curve for a new user is too steep.
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)
I haven't had to use support very often, but when I have, it has been effective in helping to accomplish our goals. Since Nagios has been very popular for a long time, there is also a very large user base from which to learn from and help you get your questions answered.
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.
Along with the purchase of the solution, we purchased a statement of work with their Professional Services organization to meet our outcomes and fill our critical gaps. The PS team was outstanding, very professional and allowed us to screen share while they built our integrations. In many cases they would teach us how they did certain things within the platform.
We have tested several other monitoring products which were able to monitor the basic matrix (Memory, DiskUsage, CPU%, UpTime, Running Service Status, Port 80 Up/Down). Although some offered far better UIs, they lacked the ability to monitor ANYTHING. Zabbix, being the only contender worthy of competing, is a good alternative to Nagios. We also tried Zenoss Core & OpenNMS which were good enough for non-Linux engineers to get started with. OP5 was another service-oriented monitoring solution we evaluated. Apart from Nagios, Consul is heavily used to monitor & register the micro-service systems & end-point URLs. Due to the time invested (9+years) in Nagios, we were able to get more components installed/configured easily than alternatives.
We evaluated a couple of other competitive products in the IT infrastructure observability domain; however, we found that ScienceLogic has a slight edge over the others for us. We encountered a cost barrier, as managing too many customers with an MSP setup was a costly affair, and several solutions did not offer an MSP solution at that 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.)
With it being a free tool, there is no cost associated with it, so it's very valuable to an organization to get something that is so great and widely used for free.
You can set up as many alerts as you want without incurring any fees.
