We performed a comparison between LiveAction LiveNX and LogicMonitor based on real PeerSpot user reviews.
Find out in this report how the two IT Infrastructure Monitoring solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The single dashboard is a valuable feature."
"We can manage the entire system across the network and troubleshoot the pain points."
"All in all, LiveAction LiveNX has become an indispensable tool for maintaining and improving our network's reliability and performance, ultimately supporting our organization's goal of providing timely and dependable delivery services."
"The alerting feature is very good because it allows you to set MOS alerts at various network junctures or data points."
"One of the valuable features is the ability to create CLI scripts on the fly to fix any issues. We were using it for QoS modeling to ensure that we were properly modeling QoS, and it basically said here is what you need to fix to get this QoS done, whether it is ACL or something else. It would either push or recommend. If you have the right credentials, you could also push. It is very good if you are a Cisco shop. It gives you reporting, latency, and bandwidth utilization for your applications, so you can do good capacity management planning. There are a lot of pieces that LiveNX can give you. It is a total NPM solution for SD-WAN."
"The product has a very good graphical interface."
"The intention and the idea of the filter is great."
"We don't have any complaints about the software. According to my team, it's a very good tool that's very intuitive."
"Its analytical capability is really good."
"Whenever we reach out to our customers, we give LogicMonitor as a dashboard to them so they don't need to monitor the hardware side separately. For example, if my service is running on their hardware X, that means they don't need to monitor hardware X and our services too. LogicMonitor has the capability of monitoring their hardware as well as our services. This is how LogicMonitor helps us."
"Another feature from the technical aspect, the back-end, is the ability to allow individual users or customers to have their own APIs. They're able to make changes using the plugins covered by LogicMonitor. That is a very powerful feature that is more attractive to our techno-savvy customers."
"It has improved our organization with its capacity planning. We have a performance environment that we use to benchmark our applications. We use it to say, "Okay, at a certain level of concurrency, we know where our application will fall over." Therefore, we are using LogicMonitor dashboards to tell us that we're good. Our platform can handle X number of clients concurrently hitting us at a time."
"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."
"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."
"The initial setup is very simple."
"LogicMonitor added AI technology to help understand what's normal and that has helped quite a bit, so that's the feature I found most valuable in the product. The product is also doing quite well with identifying devices and customizing a particular Cisco version or model number. LogicMonitor continues to be active in updating what is available to be monitored, and it's been very good with keeping those things current, so that's another valuable feature of the product."
"The breadth of its ability to monitor all our environments, putting it in one place, has been helpful. This way, we don't have to manage multiple tools and try to juggle multiple balls to keep our environment monitored. It presents a clear picture to us of what is going on."
"The technical support needs improvement."
"The Wi-Fi side needs improvement."
"They need to create a more simplified UI."
"Sometimes the solution does not register devices properly and that is a bug."
"The only downside to this software is the price."
"The tool crashes sometimes when we try to pull reports simultaneously."
"This is a horrible solution and I think everything needs to be improved."
"Improved documentation and more responsive customer support can help in addressing issues faster."
"It is not as robust as other NPM solutions. For instance, there is a problem while labeling specific applications. It works well with well-known applications, but when you have to put in new applications that are not very known and set them up with names, ports, URLs, or some protocols, it is not as intuitive."
"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."
"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."
"The topology mapping is all based on the dynamic discovery of devices that could talk to each other. There is no real manual way that you can set up a join between two devices to say, "This is how this network is actually set up." For example, if you have a device, and you're only pinning that device and not getting any real intelligent information from it, then it can't appear on the map with other devices. Or if it can appear, then it won't show you which devices are actually joined to it."
"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."
"The dashboards can be improved. They are good, but there is a pain point. To show things to management, to explain pain points to other customers, to show them exactly where we can do better, the dashboarding could be better. Dashboards need to show the key things. Nobody is going to go into the ample details of Excel sheets or HTML."
"One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting."
More Juniper Mist Premium Analytics Pricing and Cost Advice →
LiveAction LiveNX is ranked 54th in IT Infrastructure Monitoring with 7 reviews while LogicMonitor is ranked 14th in IT Infrastructure Monitoring with 25 reviews. LiveAction LiveNX is rated 6.8, while LogicMonitor is rated 9.0. The top reviewer of LiveAction LiveNX writes "Greta visual analytics and real-time monitoring but requires better documentation". On the other hand, the top reviewer of LogicMonitor writes "We went from nothing to full visibility across our internal and external estates of equipment". LiveAction LiveNX is most compared with ThousandEyes, SolarWinds NPM, Cisco Secure Network Analytics, OmniPeek and NETSCOUT nGeniusONE, whereas LogicMonitor is most compared with ScienceLogic, SolarWinds NPM, Zabbix, OpsRamp and SCOM. See our LiveAction LiveNX vs. LogicMonitor report.
See our list of best IT Infrastructure Monitoring vendors and best Network Monitoring Software vendors.
We monitor all IT Infrastructure Monitoring reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.