What users are saying about
140 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Top Rated
214 Ratings
140 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.9 out of 100

ScienceLogic SL1

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
Top Rated
214 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.8 out of 100

Likelihood to Recommend

Nagios Core

Nagios monitoring is well suited for any mission critical application that requires per/second (or minute) monitoring. This would probably include even a shuttle launch. As Nagios was built around Linux, most (85%) plugins are Linux based, therefore its more suitable for a Linux environment.
As Nagios (and dependent components) requires complex configurations & compilations, an experienced Linux engineer would be needed to install all relevant components.
Any company that has hundreds (or thousands) of servers & services to monitor would require a stable monitoring solution like Nagios. I have seen Nagios used in extremely mediocre ways, but the core power lies when its fully configured with all remaining open-source components (i.e. MySQL, Grafana, NRDP etc). Nagios in the hands of an experienced Linux engineer can transform the organizations monitoring by taking preventative measures before a disaster strikes.
Shawn Brito | TrustRadius Reviewer

ScienceLogic SL1

Great for enterprise deployments where there is a single standard of devices and monitoring practices in place. Managed Service Providers have a harder time deploying the solution across multiple customers due to constantly changing customer requirements, device types and monitoring and security requirements and scenarios.
Rob Duram | TrustRadius Reviewer

Pros

Nagios Core

  • Monitoring of services is one of the biggest benefits for our company. Being able to respond in a timely fashion keeps business smooth.
  • Hardware and device monitoring are easy to set up with proper parameters.
  • Notification to key staff to be able to respond quickly makes issues go away faster.
Eric Krueger | TrustRadius Reviewer

ScienceLogic SL1

  • Graphing - Sciencelogic has highly configurable, high-quality graphs that make the display of mission-critical data very effective.
  • Customization - With a few exceptions, nearly everything in the system can be changed, modified, added or deleted to create your ideal monitoring environment.
  • "Power Packs" - The built-in packages provide a good level of out of the box functionality.
Britton Starr | TrustRadius Reviewer

Cons

Nagios Core

  • Nagios could use core improvements in HA, though, Nagios itself recommends monitoring itself with just another Nagios installation, which has worked fine for us. Given its stability, and this work-around, a minor need.
  • Nagios could also use improvements, feature wise, to the web gui. There is a lot in Nagios XI which I felt were almost excluded intentionally from the core project. Given the core functionality, a minor need. We have moved admin facing alerts to appear as though they originate from a different service to make interacting with alerts more practical.
Anonymous | TrustRadius Reviewer

ScienceLogic SL1

  • Taking the auto backup of the devices will be one feature I would like to see in it.
  • Running the script on the devices feature will be very useful.
  • Firing the command on set of devices will be an added advantage.
Aditya Dev | TrustRadius Reviewer

Likelihood to Renew

Nagios Core

Nagios Core 9.9
Based on 3 answers
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.
Anonymous | TrustRadius Reviewer

ScienceLogic SL1

ScienceLogic SL1 7.9
Based on 5 answers
We migrated away from our 20-year-old homegrown solution and have no back-tracking capability.
ScienceLogic is a Cisco Partner and we are supported in ensuring their success.
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).
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Usability

Nagios Core

Nagios Core 4.0
Based on 1 answer
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.
Anonymous | TrustRadius Reviewer

ScienceLogic SL1

ScienceLogic SL1 7.0
Based on 3 answers
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).
Further, the score is influenced by ScienceLogic being a Cisco Partner and while Cisco IT is a customer, we are also executing on internal expectations to make our partners successful by constructive (and sometimes pressured) criticism to better the platform.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Reliability and Availability

Nagios Core

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
For us, monitoring needs to degrade gracefully. That means that, by design, you allow your monitoring system to begin giving you less and less information until an ultimate failure point. Our motto is Last-Down / First-Up and our deployment architecture reflects specific design choices to minimize being part of someone else's failure-mode.ScienceLogic SL1 at 8.12 provides a wealth of monitoring data. This comes at a cost as you scale up.Can you consume the wealth of monitoring data?Can you consume the wealth of warnings and errors that being to get generated as you scale up?There are challenges, most of which are due to our deployment design choices and scale.We are working with ScienceLogic to introduce Priority as a first-class data element. We've added this as a Custom Attribute for all of our CIs. We use this to distinguish between the failure of a development host vs the failure of our production website.The score represents the known opportunity for improvement that we see on our joint roadmaps.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Performance

Nagios Core

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
Care should be taken when creating dashboards which present all of the collected data available to you.We have many routers at work.Almost all of them have 10K interfaces on each one.Creating dashboards which present many different views of many different, large routers can create undue database load. (We're actively discouraging their use as a long-running process because each dashboard widget gets its own database connection, not a shared database connection.) We will kill all long running queries in the database if they run longer than 30 minutes.The database schema design makes interesting trade-off decisions (optimizing for ease of write at the expense of complex / cross-device reads). The new GraphQL schema model looks promising, but we're still waiting for that to begin to appear in the SL1 core functionality.Given enough hardware and budget, you can go a long ways before you start pushing the boundaries of the platform architecture.Being conservative in what you monitor for the vast majority of your CIs allows you to retain compute capacity for dashboards, runbook engines and the like.Having large routers or vCenters will require an upscaling of your data collector sizings just to complete the Device Component Map data collection.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Support Rating

Nagios Core

Nagios Core 8.0
Based on 9 answers
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.
Chris Saenz | TrustRadius Reviewer

ScienceLogic SL1

ScienceLogic SL1 5.6
Based on 8 answers
We are working through the reproducibility cost-of-entry issues.
There is room for improvement, but I also clearly want to commend the support team for their responsiveness and remediations when our stacks have significant problems.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

In-Person Training

Nagios Core

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 9.1
Based on 1 answer
On the Cisco IT 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 Cisco IT 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.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Implementation Rating

Nagios Core

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 5 answers
Know your use case.
Know which inherent use case ScienceLogic approaches you with. (They still have a long history of Managed Service Provider that influences their thinking and they are learning to be self-aware and thoughtful about you rather than your deployment being just a templated deploy that they've done many times before.)

They are making progress, but your clear and persistent insistence on deployment according to your use case will help minimize problems.
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Alternatives Considered

Nagios Core

I have been using Nagios for 10+ years, so I am very familiar with it. The learning curve with SolarWinds was more difficult for me to pick up than Nagios and it wasn't as easy (at first) to duplicate, edit, etc. in SolarWinds. I genuinely think Nagios is a great product for many reasons, one of which is the unbeatable price.
Anonymous | TrustRadius Reviewer

ScienceLogic SL1

We vetted many other platforms and continue to do so (SolarWinds, Prognosis IR, Zenoss, etc.) and find ScienceLogic to be the most well-rounded and extensible platform. That means that unlike other platforms that are limited once you roll out the standard offering, ScienceLogic can continue to evolve to handle those other platforms and situations while still providing a solid base functionality for the more common solutions.
Tim Reaves | TrustRadius Reviewer

Scalability

Nagios Core

No score
No answers yet
No answers on this topic

ScienceLogic SL1

ScienceLogic SL1 7.3
Based on 1 answer
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.)
John &quot;Frotz&quot; Fa'atuai | TrustRadius Reviewer

Return on Investment

Nagios Core

  • Much better network device performance metrics allowing to troubleshoot and do before/after changes comparisons
  • Has helped us to integrate with our Service Management tool (through other 3rd party tools)
  • Important part of our overall network health dashboard providing granular details at the device level (not end-to-end performance)
  • Cost is very convenient
Manuel Ayala | TrustRadius Reviewer

ScienceLogic SL1

  • Flexibility in multi-tenancy allows us to tweak individual customers to allow us to properly alert and avoid SLA penalties for over-ticketing.
  • Provides performance data to reduce overall ecosystem costs in various platforms, such as over or undersized AWS resources.
  • Helps to maintain uptime and detect issues before they can become a full-blown outage, causing loss of faith from customers which ultimately hurts the bottom line.
Matthew Carter | TrustRadius Reviewer

Screenshots

Pricing Details

Nagios Core

General

Free Trial
Yes
Free/Freemium Version
Yes
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
No

Nagios Core Editions & Modules

Additional Pricing Details

ScienceLogic SL1

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Required

ScienceLogic SL1 Editions & Modules

Edition
SL1 Infrastructure Health$01
SL1 Application Health$02
SL1 Service Health$03
SL1 Incident Automation$03
  1. per device
  2. per node
  3. per device
Additional Pricing Details

Add comparison