It is stable and fit for purpose. Various plugins are available as per your need in the open source marketplace to use and customize according to the need.
Manager - Service Management ( Event & Capacity ) with 1,001-5,000 employees
It is stable and fit for purpose. Setup is bit complicated due to the large set of libraries it needs.
What is most valuable?
How has it helped my organization?
We use other enterprise products for most monitoring activities. However, Nagios has been the product to go to if we need a cost effective solution that can directly fit our needs. We use it in our business operations center to view dashboards (i.e. it provides a Google map view) of critical systems within stores.
What needs improvement?
Setup is bit complicated due to the large set of libraries it needs, but this may be because it's open source.
For how long have I used the solution?
We use only Nagios Core.
Buyer's Guide
Nagios Core
December 2024
Learn what your peers think about Nagios Core. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,053 professionals have used our research since 2012.
What was my experience with deployment of the solution?
We have had no issues with the deployment.
What do I think about the stability of the solution?
Stability wise it just works without any major maintenance.
What do I think about the scalability of the solution?
It's highly scalable and will scale according to your needs.
What about the implementation team?
It is an open source tool which provides capability to customize it according to the needs. So internally you need to have expertise to consume its servers unless you go for the paid options.
What's my experience with pricing, setup cost, and licensing?
You should be sure that you have the expertise to customize it, and I would recommend the paid-for Nagios XI for the additional support.
What other advice do I have?
This is a fit for purpose product which means that if you have a definite list of requirements and are not willing, or unable, to spend money on big enterprise tools, then Nagios is a tool to go to. Also, any changes to the customization means that you need to have the skill sets internally within the organisation to effectively use it. Otherwise it's a great open source product.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Linux System Administrator at Amity Software Systems Limited
A stable and easy-to-set up open-source monitoring tool
Pros and Cons
- "We mostly use Nagios Core to integrate with Python and Bash Script."
- "Nagios Core does not have a graphic display."
What is most valuable?
We mostly use Nagios Core to integrate with Python and Bash Script. If there is a requirement from the client to monitor these services, and Nagios Core does not have the features, we integrate Python and Bash Script with Nagios Core to monitor the services.
What needs improvement?
Nagios Core does not have a graphic display.
For how long have I used the solution?
My company has worked with Nagios Core for the last six years.
What do I think about the stability of the solution?
I rate Nagios Core ten out of ten for stability.
What do I think about the scalability of the solution?
I rate Nagios Core ten out of ten for scalability.
How was the initial setup?
Nagios Core's initial setup was not difficult for me.
What's my experience with pricing, setup cost, and licensing?
Nagios Core is a cheap solution.
What other advice do I have?
Nagios Core is a world-famous open-source monitoring tool. It is easy for us to showcase a Nagios Core demo to the client.
Overall, I rate Nagios Core ten out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
Buyer's Guide
Nagios Core
December 2024
Learn what your peers think about Nagios Core. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,053 professionals have used our research since 2012.
Notifications are received promptly; very easy to set up and manage
Pros and Cons
- "Provides timely notifications."
- "The UI is a little outdated and graphics could be displayed in a better way."
What is our primary use case?
Our main goal with Nagios is to keep a close eye on our servers and the services running in our AWS environment. We’ve got a mix of Windows and Linux systems, each running specific services, and Nagios alerts us whenever something isn’t quite right. It’s also great for monitoring the sites we host on IIS. We've relied on Nagios since 2013, and it’s been a real game-changer when you have so many moving parts to track.
How has it helped my organization?
I can say Real-time Monitoring and Alerts, Comprehensive Coverage, Cost-effective Solution, Historical Data and Analysis, and Reliability and Stability
What is most valuable?
The value of the solution is that we get timely notifications if there are any issues and they can be solved immediately. Nagios provides all the plugins required.
What needs improvement?
The UI is a little outdated so it's not as user-friendly as it should be and the graphics should be displayed in a better way.
For how long have I used the solution?
I've been using this solution for 10 years.
What do I think about the stability of the solution?
The solution is stable and reliable.
What do I think about the scalability of the solution?
The scalability of this solution is impressive, particularly because it allows us to expand our monitoring capabilities as our infrastructure grows. With Nagios Core, we can easily add new hosts, services, and devices as needed, ensuring that we maintain visibility across an increasing number of systems. While configuring additional checks can require some setup time, the flexibility it offers makes it well-suited for scaling. Additionally, the open-source community provides plugins and resources that help address scaling challenges, making it adaptable for both small and large environments.
How are customer service and support?
Because the solution is open source, there's no direct support from Nagios. We post our questions to the community and that provides sufficient support.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is easy and straightforward. Deployment probably took us an hour or two and was not implemented all at once. New areas come up all the time that require monitoring so we research which plugin will be useful and implement that. It's enhanced gradually whenever we have a specific requirement. The implementation was done in-house. There is some maintenance involved, including for the upgrades. I manage the solution but there's a development team to monitor the services, around eight to 10 people.
What's my experience with pricing, setup cost, and licensing?
The product is open-source, so it’s completely free to use. We have it deployed on an Amazon server, which costs us a small amount approximately $30 per month for AWS hosting
Which other solutions did I evaluate?
We tested ManageEngine and another open-source product like Zenoss but we found Nagios easier to set up and manage.
What other advice do I have?
I recommend this solution because it’s very user-friendly. There are excellent resources available online, and it provides everything we need to meet our requirements.
I rate this solution nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Nov 5, 2024
Flag as inappropriatePartner Technical Support & Escalation Manager at a tech vendor with 51-200 employees
We are using the free version, and we can monitor pretty much everything we want to
Pros and Cons
- "It is fairly easy to set up, and we can monitor pretty much everything we want to."
- "We're using the free version, which limits us in terms of the things that we can do. If we had the paid version, a lot of our issues would probably go away. For example, we can't isolate instances that are being built or updated with the production ones. When they're being built, on Nagios, they're showing in red. It'd be nice to be able to partition those off until they're all green, and then we can bring them into the environment. This is probably because we've got the free version and not the paid version. If we went for the paid version, it would probably allow us to do exactly what we want to or remove the restrictions that we have, but if we are able to isolate instances in the free version, it would make life much easier."
What is our primary use case?
It is used for monitoring services on a bunch of virtual machines.
In terms of the version, we're fairly up to date. We are perhaps not the most up-to-date, but we're fairly current.
How has it helped my organization?
It provides visibility of the platforms.
What is most valuable?
It is fairly easy to set up, and we can monitor pretty much everything we want to.
What needs improvement?
We're using the free version, which limits us in terms of the things that we can do. If we had the paid version, a lot of our issues would probably go away. For example, we can't isolate instances that are being built or updated with the production ones. When they're being built, on Nagios, they're showing in red. It'd be nice to be able to partition those off until they're all green, and then we can bring them into the environment. This is probably because we've got the free version and not the paid version. If we went for the paid version, it would probably allow us to do exactly what we want to or remove the restrictions that we have, but if we are able to isolate instances in the free version, it would make life much easier.
In terms of new features, we're just using it for what it is. We are using what we've got now. We don't have any additional requirements as far as I'm aware.
For how long have I used the solution?
I have been using this solution for four or five years.
What do I think about the stability of the solution?
It is fine. There are no concerns there. Our biggest challenge is that we get a lot of timeouts, but that seems to be because of our network setup. There are a whole bunch of spurious events being reported, but they're more timeouts in getting to the Nagios agents.
What do I think about the scalability of the solution?
It seems to be all right at the moment. We don't seem to be having any problems with that. We have upwards of 20 users, and it is being used on a daily basis.
How are customer service and support?
I have not contacted them for a long time.
Which solution did I use previously and why did I switch?
Nagios is the first one.
How was the initial setup?
From what I heard, it didn't seem difficult to set up. It was quite straightforward.
We're still rolling out and deploying new instances of VMs that we want to monitor. It's an ongoing process.
What about the implementation team?
We deployed it ourselves. Its maintenance is done by one or two people.
What's my experience with pricing, setup cost, and licensing?
We are using the free version.
What other advice do I have?
I would recommend it to others. It does what it is supposed to. It is pretty good.
I would rate it an eight out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Systems Architect at Rezgateway
It prevents disasters long before they can take place
Pros and Cons
- "It has made the life of the network operations staff more proactive in managing the resources of the infrastructure. It prevents disasters long before they can take place."
- "It is a bit slow due to latency."
What is our primary use case?
We use Nagios to monitor hundreds of CentOS cloud servers (and a few Legacy Windows servers). Nagios is monitoring well over 5000 service endpoints. Some plugins were handwritten in PHP, Perl, Python, Java and Bash.
How has it helped my organization?
It has made the life of the network operations staff more proactive in managing the resources of the infrastructure. It prevents disasters long before they can take place.
What is most valuable?
- Historical Alert records/data
- Plugins
- Data sources (MySQL)
- Grouping of services and servers
We use the Alerting and Graphing to minimize the downtime. The old RRD Graph module is now used by Grafana. We outgrew the old PNP4Nagios a few weeks back.
What needs improvement?
The GUI of the Core is still a long way off, but the features are 100 percent above average. It would be great to see better UI themes which could be configured by Netadmin or instructions that help combine graphs and Nagios.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
I have never had stability issues. Nagios has been stable for over 10 years. Although, we never left it running for more than two weeks without uploading new services, plugins, and threshold changes, then restarting it..
What do I think about the scalability of the solution?
No scalability issues, though it is a bit slow due to latency. However, after tweaking the Nagios and off-loading the graphing to NPCD, I was able to scale the Nagios to more than 5000 services checks with 0.5s latency.
How are customer service and technical support?
The end-users love quick alerting and Grafana dashboards.
Which solution did I use previously and why did I switch?
We did not previously use a different solution. Nagios was the first solution that we started using 10 years ago.
How was the initial setup?
Since its Nagios, it is a bit time consuming, but worth the effort. It took a few hours setting up the entire environment, including RRD, PHP, Apache, Nagios, PNP4Nagios, Perl, Python, OpenSSL, etc.
What about the implementation team?
We did an in-house installation.
What was our ROI?
We have saved a lot of time, money, and effort in reducing disaster times, which is owed to Nagios quick alerting.
What's my experience with pricing, setup cost, and licensing?
The Nagios Core (PNP4Nagios + Core) is free and can be setup by Netadmin within a few hours. The only additional cost is the cloud server.
Which other solutions did I evaluate?
10 years ago, there were not too many options.
What other advice do I have?
There are thousands upon thousands of plugins. This is a winning product. Nothing can match the plugins, even I have contributed about six plugins.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Monitoring & IT Service Automation Product Consultant and Team Lead at a transportation company with 10,001+ employees
Is stable and customizable, but cloud monitoring needs improvement
Pros and Cons
- "Our customers like that Nagios Core is an open source solution. It can be customized to our customers' specific needs."
- "Cloud monitoring is an area for improvement because there aren't too many plugins available."
What is most valuable?
Our customers like that Nagios Core is an open source solution. It can be customized to our customers' specific needs.
What needs improvement?
Cloud monitoring is an area for improvement because there aren't too many plugins available.
For how long have I used the solution?
I've been using Nagios Core for almost two years.
What do I think about the stability of the solution?
It is a stable solution, and I would rate the stability at eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability at five out of ten.
What's my experience with pricing, setup cost, and licensing?
Nagios Core is an open source solution, and there are no licensing fees.
What other advice do I have?
Nagios Core is a good tool overall, and I would rate it at six on a scale from one to ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Information systems manager at Golfera
It's a stable solution for infrastructure monitoring, but it's complex to set up and use
Pros and Cons
- "Nagios Core is stable."
- "The dashboard and monitoring features could be improved."
What is our primary use case?
I'm primarily using Nagios Core to monitor infrastructure like servers, virtual machines, and telephone usage like IP-DECT antennas. I don't use all of Nagios Core's data functionality. I only use the monitoring features.
What needs improvement?
The dashboard and monitoring features could be improved.
For how long have I used the solution?
We've been using Nagios Core for about five years.
What do I think about the stability of the solution?
Nagios Core is stable.
How was the initial setup?
The Nagios Core setup is complex, but I can handle it all myself.
What other advice do I have?
I rate Nagios Core seven out of 10. Nagios Core is not easy to use, so I don't recommend it for everyone.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Consultant at a tech consulting company with 51-200 employees
Everyone ends up using Nagios or a derivative just because everyone else does
Everyone ends up using nagios or a
derivative just because... well everyone else does. The size of your org
really matters a lot with what you are doing here as Zabbix might fit
you right or not at all.
Lately I've been setting up nagios with a graphite back end for people.
Then taking advantage of writing your own plugins for nagios to send
data to both systems. You can throw a lot of data at graphite and make
some super pretty graphs if that is what you are after. For example
imagine having all the contents of a vmstat/iostat every X seconds...
for ALL your servers that can be queried with less than a minute
latency. You can do that with nagios+graphite+yourownfixins. ... and
then you show Dev how easy it is to log data into carbon/graphite and
become a super hero.
When you start hoarding this much data you can start asking some really
detailed questions about disk performance, network latencies, system
resources, etc... that before were just guestimates. Now you have the
data and the graphs to back them up.
I'm also a big fan of Pandora FMS but I've never implemented it anywhere professionally and the scope it takes is pretty large.
(I should note, nagios is pretty terrible, it's no better than things we had a decade ago.)
The real truth here is that all the current monitoring systems are pretty terrible given that they are no better than what we had a decade ago. Every good sysadmin group makes them work well enough, but there is a lot of making them work. Great sysadmins go on to combine a couple of them with their own bits to make the system a bit more proactive than reactive, which is what most people expect out of monitoring.
Reactive monitoring is fine for certain companies and certain situations
and it is easily obtainable with nagios, zabbix, home-brew,
stupidspendmoney solution, etc... However reactive monitoring is just
the base point for most, it certainly doesn't handle big problems well,
or have the capacity to predict events slightly before they are
happening. This level of monitoring also doesn't give you much data
after an event to figure out what went wrong.
Great admins go on to add proactive systems monitoring and in some cases
basic logic monitoring. This is what a lot of us do all the time, to
avoid getting paged in the middle of the night, or to know what to pick
up at fry's on the way into the office. Proactive monitors a lot more
things than basic, and it is essentially the level where everyone works
at now, with nagios, etc... That's certainly fine for today and
tomorrow. But it doesn't tell you anything about next quarter, and when
you ask queries about events in the past they are often very basic in
scope.
The other amazingly huge drawback with current monitoring is that if you
want to monitor business or application logic, it is going to be
something you custom fit into whatever monitoring system you have. This
will lead to it being unwieldy and while effective for answering basic
questions like, "What's the impact on sales if we lose the east coast
data center and everything routes through the west?" That's a fine
question but it isn't a question that will get you to the next level,
better than your competitors.
So what's next? I'll tell you where I think we should be going and how I am sort of implementing it at some places.
Predictive monitoring on systems AND business logic, with lots of data,
and very complex questions being answered. This can be done right now
with nagios, graphite and carbon. Nagios fills the monitoring and
alerting needs. Carbon stores lots of numerical data, very fast from a
lot of sources. Finally with Graphite you can start asking really
serious questions like "How did the code push effect overall page
performance time, while one colo site was down? What's the business cost
loss? Where were the bottlenecks in our environment? Server? Disk?
Memory? Network? Code? Traffic?" Once you've constructed one of these
list of questions in graphite you can save it for the future, and not
only monitor it, but because of legacy data kept on so many key points
use it for future predictions.
That said, how do you all that now? Well you throw nagios, graphite and
carbon out there and then you CREATE a whole lot of stuff that is
specific to your org. This is a lot of work, a lot of effort and takes
time and real understanding of the full application and what your end
SLA goals are.
So how do we do all this?
You as an admin do this, by creating custom nagios plugins and data
handlers on your systems and throwing them in to carbon. As an admin you
measure everything, and I mean everything. Think all of the output from
a vmstat and an iostat logged in aggregate one minute chunks on every
single server you have and kept for years.
From the dev site you get the Lead Dev to agree on some key points where
the AppStack should put out some data to carbon. This can be things
like time to login, some balance value, whatever metric you want to
measure. The key here is to have business logic metrics AND system
metrics in the same datastore within Carbon. Now you get to ask question
across both data sets, and you get to ask them frequently and fast. You
are able to easily make predictions about more load impacting the
hardware in what manner, i.e. do we need more spindles, more memory,
etc...
This is what I have been doing with some companies in SV right now. It's
not pretty or fully blown out yet, because it is a big huge problem
and our current monitoring sucks. :D
but it IS doable with current stuff and is quite amazing to know answers to questions that were previously only dreamed about.
What's after that? The pie in the sky next level, would be having an app
box in every app group running in debug mode, receiving less traffic of
course through the load balancers, and loading all that debug data into
carbon. Then you get to ask questions about specific bits of a code
release and performance on your real production environment.
... so those are my initial thoughts. Any comments? :)
Further once you have all this, you can now write nagios plugins to poll
carbon for values on questions you have created and then alert not only
on systems logics and basic app metrics, but real queries that are
complex. Stuff like "How come no one has bought anything off page X in
the last two hours, is it related to these other conditions? Oh. It is.
Create me an alert in nagios so we can be warned when it looks like this
is about to happen again." With much more data across more areas you
can ask and alert on pretty much anything you can imagine. This is how
you make it to next level.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Nagios Core Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
Datadog
Zabbix
New Relic
PRTG Network Monitor
ThousandEyes
Nagios XI
LogicMonitor
Centreon
Icinga
Checkmk
ITRS Geneos
InfluxDB
Meraki Dashboard
IBM SevOne Network Performance Management (NPM)
Buyer's Guide
Download our free Nagios Core Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What is the biggest difference between Nagios Core and Nagios XI?
- When evaluating Network Performance Monitoring, what aspect do you think is the most important to look for?
- What is the best network monitoring software for large enterprises?
- What Questions Should I Ask Before Buying a Network Monitoring Tool?
- UIM OnPrem - SaaS
- Anyone switching from SolarWinds NPM? What is a good alternative and why?
- What is the best tool for SQL monitoring in a large enterprise?
- What tool do you recommend using for VoIP monitoring for a mid-sized enterprise?
- Should we choose Nagios or PRTG?
- Which is the best network monitoring tool: Zabbix or Solarwinds? Pros and Cons?
Chris, do you still find this to be true? Is Nagios still a default tool when people are searching for IT Infrastructure Monitoring solutions?