Freshping was a website uptime monitoring tool with free and enterprise editions, from Freshworks. The product is no longer available to new customers.
$11
per month, billed annually
Nagios Core
Score 8.0 out of 10
N/A
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
Pricing
Freshping (discontinued)
Nagios Core
Editions & Modules
Blossom - 60 checks (can add more checks)
$11.00
per month, billed annually
Garden - 80 checks (can add more checks)
$36.00
per month, billed annually
Sprout
Free
50 checks (none additional)
Single License
Free
Single License
Free
Offerings
Pricing Offerings
Freshping (discontinued)
Nagios Core
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Every additional 10 checks - $8/month billed annually
Freshing is well suited for user-facing systems, the systems they directly use. It also serves as nice eye-candy for them to look at. It does not monitor internal IT systems as well as we had hoped, so we use other tools to monitor those systems.
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.
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.
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.
It's perfectly easy and straightforward to use. There's no need to read documentation, you just register and will surely be able to configure whatever monitor you want to set up. It's also very easy to use other features like the status page, reporting, alerts, etc.
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.
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.
We use Uptime Robot, and also some internal health checks, which report directly to our emails and chat applications. They all work "pretty fine," but unfortunately all of them have had some false positives or missed some minor downtime, so as for us, it doesn't add too much overhead, and we prefer to use several. I would say all the ones mentioned are good for the job.
Because we get all we required in Nagios [Core] and for npm, we have to do lots of configuration as it is not as easy as Comair to Nagios [Core]. On npm UI, there is lots of data, so we are not able to track exact data for analysis, which is why we use Nagios [Core].
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.
