Plixer Scrutinizer vs Zabbix comparison

"We didn't experience any bugs."

"The ability to view the status of the top-10 at a glance is helpful. We immediately know which link is over-utilized or heavily used... and it's all in real-time."

"It's agnostic as far as what your network gear is. As long as it supports an sFlow, JFlow, NetFlow, some kind of flow monitoring, Plixer will support it very well."

"It helps us determine what is going on with our Internet and who is hogging it all up. If we get a real high throughput or a throughput that's going over and getting dropped fairly quickly, we can tell who (or what device) is consuming that traffic."

"Plixer Scrutinizer is an affordable product. Plixer Scrutinizer is a tool that allows for customization, especially in scenarios where customers need new product features."

"One of the most valuable features of Plixer Scrutinizer is the reporting, particularly how easy it is to drill down into the reports. Another valuable feature of the solution is its overall visibility. It's great. I also liked Plixer Scrutinizer in terms of deployment time and that it's very simple to set up. Once you get the appliance set up and connected, the customer starts to see results immediately, versus other solutions where that could take a while."

"Visualization of the network traffic is the most valuable feature. It allows you to drill into information quite quickly."

"The reporting and generating troubleshooting reports would be the best feature; our host-to-host conversation reporting."

"Templates are good. We download them from the official Zabbix site or the community. If the information we need isn't available, we create custom templates based on client requirements."

"The solution is quite mature and very stable."

"There are lots of great features and functionality within the solution."

"The best thing about Zabbix is the integration and the APIs that are included are very fast"

"I really enjoy network traffic triggers that allow us to check traffic threshold from ISP."

"It can send messages to our ticketing system."

"SNMP monitoring, source discovery, and alert triggering are most valuable."

"Every new asset placed in the environment can be automatically detected, predicting human failures."

"We couldn't get it set up properly."

"There is room for improvement around the data that they have on the website about solutions... they should have more templated solutions on their website. Going out and identifying how to do RTP performance with a Cisco router, or how to do application response times in an Arrista data center deployment was where most of the work was... They should spend some more time documenting solutions and putting together white papers."

"It would be useful if there was a way to back up the configuration information. E.g., if you wanted to deploy a new instance or disaster recovery, you could quite easily deploy and restore the config, as opposed to having to restore all the NetFlow data. If there was just a button that said "backup config information", that would be good."

"Data retention needs improvement. Data retention is a thing where we are looking for a better way to collect flow data for a longer time to do forensic research on security incidents. By default, data retention is quite low. We need detailed data in safe storage for a longer time, e.g., for a couple of months. An improvement would be a way to export data into a secure long-term storage."

"In Plixer Scrutinizer, scalability is an area with minor concerns where improvements are required."

"There was a price lift because previously the product was privately owned, and now there is some external capital in the organization, so pricing could be lower, though, for Plixer Scrutinizer, there is almost no competition at this price point."

"Knowing that they're coming out with a new user interface, that is an area where there is room for improvement. There are so many variables. They should limit the variables in the user interface and create some classes, like "simple," "novice," and "expert" to narrow down the variables within it."

"The solution creates a visual map of a particular location and how the network flows. You need to spend time to generate all those maps. If they could figure out a way to reduce the time needed to generate the maps, that would be great."

"I think the reporting part of Zabbix can be improved in terms of more user-friendly graphics to display the collected data. Many simple users who don't know how to use Zabbix properly might get confused by the reporting, although at the same time it is very versatile for my company."

"Zabbix isn't very good at automation just yet."

"Even though it’s such a powerful monitoring system, it would be more helpful if it had a flexible UI."

"Its UI needs to be improved a little bit more so that an end-user is also able to handle it. I can handle it, but others should also be able to handle it in a better way. It becomes complex when we are growing and need to add proxies. We need more scalability features and documentation for different use cases. A lot of articles are available, but they need to be in proper documentation. For example, when you have thousands of servers that have to be monitored in different regions of the world, there should be some kind of documentation to describe how you can create proxies and add them. Sometimes, when you are using the database, it can get overloaded. When the network is growing, the number of transactions becomes very high, and the database gets overloaded. There should be information about how to reduce the load on the MySQL database, which is what Zabbix is using. The market is growing a lot, and it should be enhanced for a lot more things. We are currently bringing enhancements at our end for different use cases. For example, when dockerization is going on, how can we check the logs inside the Dockers. We should also be able to monitor and check the number of logins and add features such as SSO login and two-factor authentication as a protocol. These are the security features and concerns that we have to deal with. Currently, we are developing modules to add features to Zabbix, but they should also work on these features."

"When using this solution in enterprise monitoring, you are able to see that there are some issues with equipment that could be causing a problem. Sometimes you want to make a root command that you do not want to be executed automatically. What we have tried to do is open an SSH session directly from the solution's interface but it is not possible."

"For us, the initial setup was complex"

"Zabbix is powerful, but it is difficult to understand initially. There are many things that can be improved, but we might not be using Zabbix to its fullest extent. The software has more features than we need."

"There's a small module of APM, however, it is not an enhanced version. People usually ask for a full-fledged APM solution."

"I rate Plixer Scrutinizer's price a three on a scale of one to ten, where one is low price or affordable, and ten is high price or expensive."

"Compared to some of the other tools we have, it's incredibly reasonably priced."

"It's about €10,000 a year for initial license and yearly maintenance costs. In addition, the hardware costs are about €10,000 once every five years."

"There is a recurring maintenance fee after the initial purchase or if we want the license upgrade."

"Currently, the license for Plixer Scrutinizer is subscription-based and at a yearly fee. The price would depend on the amount of traffic you pull in. For example, there are several blocks from a 10K flow, a 40K flow, and a 100K flow, and based on the number of devices that you receive the flows from, that's the license, and it is not a per-interface pricing model, so that is a very strong, very competitive pricing feature of Plixer Scrutinizer. Licensing for the product is also not based on the number of storage, compared to some competing products that are priced based on the amount of storage you need, particularly based on the retention and the amount of data. Plixer Scrutinizer licensing is based on the device, and it's more in the direction of $10,000 because, with just $1,000, you don't have anything."

"We pay our one-off cost for the licenses, per device, in blocks of 50. And then we pay an annual maintenance fee of about $15,000 Australian, which is, at this point in time, about $9,000 US, for those 250 devices. The upfront costs for the 250-license use, were about $50,000 Australian, which is about $32,000 US."

"The license is per device. We have 50 devices."

"We recently bought a license upgrade, so we will integrate more exporters. We upgraded from a 25 exporter license to a 50 exporter license. Therefore, there will be more flows, and this will be an extension. I don't know when we will purchase a faster server, because the server that we have is quite new."

"It is reasonable."

"For pricing, it's free. We don't pay anything for it. They open-source the code, and people pay for support."

"The tool's licensing is good."

"I use the tool's free version."

"We were searching for an open source solution and Zabbix fit the bill because it is free and open source under the GPL license."

"Zabbix is a free solution but the support contact costs money."

"If you have 20,000 hosts, the support costs around €95,000 for a year."

"The tool's licensing costs are yearly."