Try our new research platform with insights from 80,000+ expert users

LogicMonitor vs Plixer Scrutinizer comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 10, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

LogicMonitor
Ranking in Network Monitoring Software
6th
Average Rating
9.0
Reviews Sentiment
7.1
Number of Reviews
34
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), IT Infrastructure Monitoring (8th), Container Monitoring (4th), Cloud Monitoring Software (7th), AIOps (5th)
Plixer Scrutinizer
Ranking in Network Monitoring Software
74th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
15
Ranking in other categories
Network Traffic Analysis (NTA) (12th)
 

Mindshare comparison

As of March 2026, in the Network Monitoring Software category, the mindshare of LogicMonitor is 2.3%, up from 1.9% compared to the previous year. The mindshare of Plixer Scrutinizer is 0.5%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
LogicMonitor2.3%
Plixer Scrutinizer0.5%
Other97.2%
Network Monitoring Software
 

Featured Reviews

Anshuman Thakur - PeerSpot reviewer
Site Reliability Engineer at a comms service provider with 501-1,000 employees
Monitoring has reduced downtime and now enables proactive alerts across cloud workloads
When it comes to the improvement of LogicMonitor, I think there are a few points that can be improved. The first one is alert tuning, which takes time. It requires effort when trying to understand it for the first time. The defaults do not always match our workload patterns, so I have to adjust the thresholds to reduce noise and avoid alert fatigue. While the dashboards are solid, I sometimes wish that the UI was a bit more intuitive when drilling down quickly during an incident. There are many options and finding the exact view where I can identify the exact problem takes a few extra clicks. When an alert comes and I click on a LogicMonitor alert, it takes time to understand what the alert actually is and to go through the data points. The alert page specifically could be better. The alert tuning part can also be made more simple. The first area that could be better is alert clarity and routing. Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views. Adding more actionable details directly in the alert would make the response even faster. LogicMonitor sometimes gives false alerts as well. For example, if an EC2 instance is down, it will not determine whether the EC2 instance has been deliberately turned off or if it is actually not responding. At that time, it will give false alerts. The clearing of alerts is also an issue. Once an issue is fixed, the alert should be cleared, but it takes a little time for that alert to be cleared. Another improvement that would be helpful is simpler customization for complex dashboards. It is powerful, but building highly tailored dashboards, especially across multiple environments, can feel heavy and time-consuming. I would also appreciate a stronger out-of-the-box AWS correlation, such as automatically grouping related issues across EC2, EBS, and ALBs in a way that reads as a single incident story. This would reduce the mental overhead during outages. Grouping incidents together, such as all the EC2 alerts, all the EBS alerts, or all the load balancer alerts would be beneficial. Overall, none of these are blockers, just some improving areas. There could be smarter anomaly detection out of the box that can catch unusual but important behavior without manual tuning of every threshold. Better tagging and dynamic grouping for EC2 instances would also be helpful. Cleaner alert de-duplication so a single underlying issue does not generate multiple redundant alerts would improve the system. More guided root cause workflows would be beneficial, such as providing the most likely causes based on correlated metrics. Faster search navigation across devices, dashboards, and alerts during incidents would also improve the platform.
Ira Mulyanti - PeerSpot reviewer
Sales Director at ARGA SOLUSI
An affordable product with great integration capabilities
Plixer Core Platform is a valuable feature and a good software. Plixer Scrutinizer uses NetFlow analysis to monitor whatever is there in a network. Price-wise, Plixer Scrutinizer is not an expensive product. Basically, Plixer Scrutinizer is an affordable product. Plixer Scrutinizer is a tool that allows for customization, especially in scenarios where customers need new product features. Plixer Scrutinizer is a tool that can integrate with any other brand or product in the market, so it is not an area of concern.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"LogicMonitor has positively impacted our organization by cutting down white noise and false positives, allowing our team to be more proactive than reactive, which cuts down on the SLOs and SLAs we are trying to meet at all times."
"The concept of developing a dashboard template for ourselves, then cloning it for every single customer, and only having to change one piece of information, is a godsend. That's one of the strengths. We can develop a template that fits every customer and just change the information that is presented."
"LogicMonitor has positively impacted our organization by allowing us to implement it for 1,200 clients or 1,200 endpoints within three months, which went very well."
"The most valuable feature is the visualization of the data that it is collecting. I have used many products in the past and they tend to roll up the data. So, if you're looking at data over long periods of time, they start averaging the data, which can skew the figures that you're looking at. With LogicMonitor, they have the raw data there for two years, if you are an enterprise customer. If you are looking at that long duration of data, you're seeing exactly what happened during that time."
"The dashboards are the big seller for us. When our customers can see those graphs and are able to interact with the data, that is valuable. They can easily adjust time ranges and the graphs display the data fast. We've used other tools in the past, where you'd say, "Hey, I want the last three months of data on a graph," and it would just sit there and crunch for five minutes before you'd actually see the data. With LogicMonitor, the fast reliability of those dashboards is huge."
"LogicMonitor improved on-premises infrastructure monitoring in several ways. One key feature was dynamic resource allocation, although we didn't utilize it much in our system. The main functionalities we benefited from were email alerts, network mapping, and dashboards."
"LogicMonitor has actually helped reduce our downtimes, helping us reduce downtime to about 40 to 50% by warning us before servers get heavy on usage or CPU load so we can take action in advance."
"The initial setup is very simple."
"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."
"There are other tools out there that will do what Scrutinizer does. But what I have found with Scrutinizer is that it does it very quickly. I've taken 25 million individual data fragments from the different sensors, and it has graphed that and mapped it and presented a picture within 30 seconds. It has a very efficient database algorithm that I am really impressed with."
"One feature I found most valuable in Plixer Scrutinizer is the very extensive reporting. Reporting is very flexible, though sometimes you need a little bit of support from Plixer Scrutinizer to create custom-made reporting in a very short time. Reporting is a very strong feature of the product."
"As a network engineer, the ability to identify what traffic on the link is consuming all the bandwidth at any given time, and provide immediate feedback to the business, is the most valuable feature."
"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."
"We didn't experience any bugs."
"It shows us the saturation of the network of devices. It gives us a clear view of the flows in the network to understand, for instance, planning upgrades in the network to get an idea of what's going on the network on traffic flows. It gives us insight, for instance, on what's going on on our VPN Client. There are a lot of things where it provides very helpful information. It also gives us our security reports with quite detailed information on what's going on in the network, and whether there are data exfiltrations and so on."
"Visualization of the network traffic is the most valuable feature. It allows you to drill into information quite quickly."
 

Cons

"Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure."
"One thing that could be really better is the mapping. Auvik is really good at it. They have a really nice way to give you a visual representation of your network, but in LogicMonitor, this functionality is not as powerful and as good as Auvik."
"LogicMonitor should always improve AI because we are always striving for real intelligence. An additional feature we'd like to see in the next release of LogicMonitor is more in the area of identification of when the dominant workload is working. There are certain devices and applications that have cycles of their own. Some are used primarily during prime time, and some are used during the overnight timeframe, and better identification and classification of those workloads would be helpful. For example, we could then do some more planning about, for this particular set of devices, as it has a prime time environment, and we don't want to see a 24-hour average, as we want to see what is the 75th or 90th percentile utilization during the prime time when it is being used, whenever that prime time is."
"LogicMonitor has a very steep learning curve."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
"One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child." For example, If I know that a top gateway is offline and I can't talk to it anymore, and anything that's connected below it or to it is also going to be offline, there is no need to alarm on those. In that situation it should create one ticket or one alarm for the parent. I know they're working towards that with their mapping technology, but it's not quite to that level where you can build out alarm logic or a correlation logic like that."
"Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views."
"It needs better access for customizing and adding monitoring from the repository. That would be helpful. It seems like you have to search through the forums to figure out what specific pieces you need to get in for specific monitoring, if it's a nonstandard piece of equipment or process. You have to hunt and find certain elements to get them in place. If they could make it a bit easier rather having to find the right six-digit code to put in so it implements, that would be helpful."
"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."
"I wish the reporting side was easier to work with, but it does a decent job. I also wish the reporting side was a little more intuitive or they offered more reporting examples."
"The reporting structure, the front-end GUI, also needs some work. It needs some getting used to. It works fairly well, but it's a technical tool rather than a user tool. You have to understand the structure of the databases before you can really use it."
"In Plixer Scrutinizer, scalability is an area with minor concerns where improvements are required."
"The visual acuity of how it presents data can sometimes be confusing. It takes a bit for people to spin up how to look at the graphs."
"For updating the Scrutinizer platform, when we have the actual data, it never happens in one day. Every time we have the data, we are obliged to install a new server in order to integrate the old data, and every time it has a problem. Most of the time, we were obliged to scrap all the data because we couldn't transfer it to the new server. So, it would be very good if they could improve this part."
"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."
"We couldn't get it set up properly."
 

Pricing and Cost Advice

"The solution is not expensive."
"It can handle scaling. It is like any other cloud service. There is a cost associated with scaling, so we currently don't monitor all of our environments. We monitor just the customer-facing production environments. It would be nice if we could monitor our dominant environments, but we will have to pay a lot more due to the scaling issue. So, there's a balance there between what we would like and what we are willing to pay for."
"It is pretty expensive, but we now need one less full-time engineer. With on-prem, we used to have one more engineer in our department. That engineer has now moved to another department. Our capacity is better with this product than the previous one. It is easy for us to manage the sites. You have to choose between the standard account and the premium account. With the premium account, you get a lot more than the standard one, and you can also buy some extra features. It is a good thing to look at them because you would probably want to buy them. You should take your time and negotiate the price. They are easy. Like all cloud providers, they are able to discuss the price and if necessary, change the price."
"We pay for the enterprise tech support."
"They are expensive for the cloud."
"It's affordable. The price we get per license is a lot cheaper than what we were getting with some of the other tools. There are other monitoring tools out there that are cheaper, but what you get with LogicMonitor, out-of-the-box, makes it worth the cost."
"As a managed service provider, we have the highest level of licensing that they offer, so we don't have any extra fees. I believe there are some add-ons for some of the lower tiers of LogicMonitor service, but that's not something that we use with our agreement."
"It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise."
"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."
"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 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."
"There is a recurring maintenance fee after the initial purchase or if we want the license upgrade."
"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."
"The licensing cost for Plixer Scrutinizer is in the middle. It's not the cheapest, but it's not the most expensive. Its licensing model is based on how many exporters, how many devices export information to the system. Plixer Scrutinizer has different modules you could add such as the security module which would cost extra."
"We have increased the license over time. We have added more licenses as the network has grown."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
884,012 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Computer Software Company
10%
Financial Services Firm
9%
Healthcare Company
8%
Financial Services Firm
11%
Government
9%
Manufacturing Company
8%
Real Estate/Law Firm
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
Large Enterprise11
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise8
 

Questions from the Community

What is the best network monitoring software for large enterprises?
It actually depends on the exact purpose or requirements. Some tools are better for only network devices while others are better from a cloud monitoring or APM monitoring perspective. You can check...
What do you like most about LogicMonitor?
LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These ...
What is your experience regarding pricing and costs for LogicMonitor?
I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
Oxford Networks, Squaw Valley Ski Holdings, UltiSat, Wipro, West Aurora School District 129, SUNY Geneseo College, Bloomington Public Schools, First National Bank of Pennsylvania, Kitsap Credit Union, Metropolitan Transit Authority of Harris County Houston Texas, Carilion Clinic, Banner Health, IDEXX Laboratories, Phibro Animal Health Corporation, Goodwill Industries, Parmalat, Armstrong Coal Company, Flybe, James Walker
Find out what your peers are saying about LogicMonitor vs. Plixer Scrutinizer and other solutions. Updated: March 2026.
884,012 professionals have used our research since 2012.