Adobe Workfront, acquired by Adobe in late 2020, is a web-based project-management tool. It is designed for both IT and marketing teams, but can be implemented for any kind of project. Workfront offers all the features standard to project management platforms, as well as resource allocation, automation, and agile workflow.
N/A
Nagios Core
Score 7.9 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
Zabbix
Score 8.5 out of 10
N/A
Zabbix is an open-source network performance monitoring software. It includes prebuilt official and community-developed templates for integrating with networks, applications, and endpoints, and can automate some monitoring processes.
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 …
We chose Nagios Core over Zabbix and Zenoss because it was easier to get up and running and configure than the other two products. They required network scanning for assets and then required you to enter every little detail about the host. With Nagios Core, we just entered our …
Unlike SL1 and IBM NOI, you do not need to buy licenses or pay for support. You can begin deployment immediately. You don't need to purchase expensive equipment or study confusing manufacturer's manuals. Zabbix can also be used freely, but it is not so common and you may need …
We selected Nagios because of the size of its community. We've used some of the others in the field over the past few years, Nagios had the best features out of the box coupled with it's following made it an easy selection.
Nagios was the best in the past and why I chose it for many of the companies I've worked for. Also, coming in to a company, there is almost always a Nagios server installed and since everyone knows the software it's easy to write plugins for it. But, in 2015, Nagios is a …
Zabbix was adopted in our framework due to the value, the hardware requirements, the knowledge we had available and the vast documentation on the internet.
Although we still use Cisco Prime for network devices, when comparing Zabbix with Nagios, for example, you see that Zabbix is more robust, stable, easy to deploy and has an enterprise focus that other tools don't have. Also, the fact that the Zabbix community is very active is …
Zabbix was much better at handling traditional systems, and in ease of customization, both in the system itself, and customizing data sources, such as adding deep MySQL or JMX integrations. It's very good for organizing large-scale (hundreds or thousands of servers) systems; …
I personally prefer Zabbix over any other monitoring software that I have ever tried. Zabbix is so customizable that if there is a feature I need, I can easily implement it. I can then add that feature to a template in no time and have it applied to hundreds, or even thousands, …
More extensive and customizable than SaaS solutions. Much less learning curve than Nagios. Cost is very much lower than SaaS monitoring especially at scales over 1000 hosts ($15,000/month for SaaS!!) Templating systems allows for easy management and monitoring of groups of …
Zabbix had the best support for the devices I initially had in my network, its ability to adapt and change has made it my Swiss Army knife of monitoring tools. While it could benefit greatly from a moderated zabbix community, its support from the open source community has …
Nagios has some advantages over Zabbix like "flapping" detection and multiple alert levels - Error, Warning and OK. However, the disadvantages of Nagios like needing an addon (NRPE) to monitor remote system internals (open files, running processes, memory, etc), no charting of …
Nagios will always be at or near the top, but I really like how sleek Zabbix is. Also, once it's up and running its really helps keep things in order for you and your customers. As for PandoraFMS, it would have beat out Zabbix, but the documentation on PandoraFMS is really …
Having requests for immediate work being routed directly to the team members who perform the function. Proofreading needs to happen fast and turnaround quickly while retaining visibility everywhere. Through reporting and statuses, we can show progress at every stage. A large campaign organization means multiple requests and documents going between departments. By using requests alongside related rejects, we have everything in one place.
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.
Zabbix is great for monitoring your servers and seeing alerts when the system uses too much CPU or memory. This allowed the system Engineer to be proactive and add resources to these systems to avoid interrupting the services. Especially servers running operations applications and services. This is one of the best usages for Zabbix.
Collecting hardware data - CPU, Memory, Network, and Disk Metrics are collected and reported on.
Flexible design - It is very easy to build out even very large environments via the templating system. You can also start where you are - network monitoring, server monitoring, etc. and then build it out from there as time and resources permit.
Provides a "plugin architecture" (via XML templates) to allow end users to extend it to monitor all kinds of equipment, software, or other metrics that are not already added into the software already.
Very complete documentation. Almost every aspect of Zabbix has been documented and reported on.
Cost - Zabbix is FOSS software and always free. Support is reasonably priced and readily available.
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.
Workfront is sometimes a bit clunky to use, but overall it works well for our teams when it comes to project management and collaboration across multiple, involved teams. It also has flexibility that allows us to adapt it to diverse use cases, some of which aren't necessarily always the first things that one would think of using workfront for.
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 is free. It didn't cost anything to implement (other than my time and the cost incurred for it) and it is filling a badly needed gap in our IT infrastructure. Support is available if we have issues and can be done annually or paid for on a per incident basis as needed. Expansion, updates, and all other future lifecycle activities are likewise free of cost, so as long as someone is able to implement/maintain the software (and the OSS project is maintained) then I imagine the company will never leave it.
Workfront is overly complex, but it is functional as a tool to keep track of projects. It is a shame that sometimes it takes a lot of clicks to find anything. Workfront is slowly modernizing its interface but at the same time, hides certain information away thus making the experience feels worse.
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 think every organization, especially the IT department, needs a tool like this. I know of another product like Zabbix that gives a similar or the same solution, but its range makes it very useful. You can see almost all the device info in one place: disk usage, disk space, network usage, etc.
I have found that Adobe Workfront is a reliable resource, because in the post 6 years of using it, rarely has it been unavailable to our team. I think I could count on one hand the number of times the site has been down over my time using it with my team.
I think overall, Adobe Workfront performs well. There have been some times when it doesn't load or run as quickly as our team would like. This is frustrating when it is such a crucial tool that our team utilizes on a daily basis. It can show our workflow when it lags.
I know that this particular company has it's own Adobe Workfront employee that builds out things they need from the software, and meets with them regularly to troubleshoot. I'm not part of this process, but it's refreshing to see Adobe provide this level of customer service to people, and they're expedient.
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.
The setup is the most time-consuming portion of using zabbix. It takes a lot of effort to shape it into a usable format and even then it can get very messy. It's not exactly intuitive and as mentioned the UI seems a bit antiquated. If I was to roll out a monitoring solution from scratch, I'd probably look for alternatives which are easier to use and maintain.
The training is very easy to use and you can simply choose the topics included in the course(s) that are most important to your training needs. After each training course, you are tested on what you have learned. If you need a refresher course, they provide Course Catalogs as well as instructor-led courses & workshops.
Most people learn as you go, a lot of this stuff requires trial and error throughout so my suggestion is to provide as much information in the upfront and keep it as simple as possible. You can add other tools and features as you go but everyone should have the basics down so no bad habits can start to develop. Be persistent with everyone, and don't be afraid to correct and talk through steps again so everyone is on the same page
We are a mainly Windows environment, so it would be useful if we could have used Active Directory to deploy agents. As of version 4.2, Zabbix has announced a new agent MSI file to allow exactly that. Unfortunately, we didn't have that option. Also, for Linux and MAC deployments, there is no simple way to deploy that. Using remote scripts you may be able to create something, but most places will opt for either SNMP (agentless) or manual installation of agents to add to Zabbix. A way of deploying agents via discovery would go a long way to helping in the adoption of the tool.
Adobe Workfront blows the other systems out of the water. It just delivers more - out of the gate, and at every quarterly update. Innovation is top of mind, and meeting customers' needs is key. We have been extremely satisfied with Workfront and look forward to all the new features on the horizon, especially AI.
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].
We're using the Solarwinds suite as our global monitoring standard, but it is very complex and its licensing model makes it difficult to monitor a wide range of technologies. So, we're using Zabbix as a complement on our monitoring process. Zabbix is a way more flexible and has free integrations to a wide range of technologies. It is also more 'user friendly' and easy to manage.
As I stated earlier, I didn't have to pay for Workfront myself- I'm a user under a large organization. I know it's not cheap to implement, I don't know how the price scales for a small-business, but I do like the product enough that I'm going to look into it in the future for my own company.
Our organization has thousands of users that use Workfront and it seems to hold up very well. I have not encountered any issues using it and I think it makes it very easy for multiple people to be involved in a project and keep things organized and clear for everyone involved.
Resource Management - Year over year, we were able to validate time and money saved by the implementation of Workfront by more than 2%, saving in non-working dollars and 9% savings in working media dollars.
Organization Restructuring and Automation- We also restructured our teams and implemented automation based on our analysis of how and what we spend our time on and the ROI for our respective business units.
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.