Plixer Scrutinizer vs Zabbix comparison

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

"We have had many requests to understand in the network which devices are connected to others. Most people don't have this information or are able to establish a map of data flow everywhere around the network. Scrutinizer can really help with this. We are using it to understand who is talking to what, how, and which protocols can help us to improve security and analyze flow."

"The most valuable features of Plixer Scrutinizer are its ease of use, accessibility, and UI."

"The solution helps to enrich the data context of our network traffic. It allows me to see what applications are most in use on a slightly historical basis, going back a day or week at tops. It allows me to tune QoS or traffic shaping around what's being used. It saves me from having to unnecessarily upgrade, if I don't need to."

"I honestly don't think there are many areas where Scrutinizer could be improved; it's a pretty robust, out-of-the-box solution."

"I really feel, after reviewing three at one time and knowing some other ones, the bang and performance for the dollars, and the capacity and the flexibility; it's really second to none in those situations."

"The internal reputation of our IT to resolve historical bandwidth problems has 100 percent improved."

"My boss and I have been very happy with the product."

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

"The product is very stable."

"The template system in Zabbix is very beneficial as it saves time in configuration."

"The most valuable features in Zabbix are those that help us overcome bottlenecks in CPU usage, as well as reduce memory delay."

"I'm supervising all the IT departments, and Zabbix seems quite good for them. It provides graphics and information in real time. We get alerts about crashes on the system, enabling us to quickly repair issues. We can easily find devices with problems."

"It's the best solution. Great. I would rate the overall solution ten out of ten."

"During my testing, the features that I like the most are that it can be integrated with my system, and it provides me with reports of all of my servers."

"Zabbix is scalable."

"For updating the Scrutinizer platform, when we have the actual data, it never happens in one day."

"The visual acuity of how it presents data can sometimes be confusing."

"From what I understand it is that the solution is not very scalable in a high volume traffic environment with a large number of flows."

"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."

"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."

"The reporting structure, the front-end GUI, also needs some work."

"They're working on the security areas, so it can provide more insight. What they have is still pretty much IP-concentric. If they were to make it IP and URL, they'd be a little bit ahead on that."

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

"Cloud monitoring can be a bit easier, and the Zabbix dashboard can be developed a little bit more."

"If Zabbix had a better dashboard then it would be nice."

"There are some features of Zabbix that are not good for reporting. The DX Spectrum solution has better reporting."

"The graphical user interface could be customized a little bit more, and also the dashboard could be more friendly."

"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."

"The solution needs to add remote features."

"As far as improvements, sometimes I get a bit frustrated when I move from a previous version to a new one because some configuration has changed—I need to investigate the documentation to deal with some configuration."

"The event correlation could be better."

"Our entire solution, amortized over five years, is in the vicinity of $40,000 to $50,000 a year."

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

"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."

"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."

"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 just renewed. The pricing is 5,000 euro per year. This is the final price. All tax (20 percent) is included."

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

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

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

"I was using the free, Community Edition."

"Zabbix is open-source so if one wishes to implement it in-house, they must have qualified professionals to set up and optimize databases, Linux/Unix OS, PHP, Apache, and depending on what is monitored, a full-stack network and systems administrator may be needed."

"It is freeware. We still use the free version of Zabbix."

"We’re using the free version, which covers all our current needs."

"We use the open-source version of Zabbix."

"This is an open-source solution that can be used free of charge."

"It is reasonable."