No more typing reviews! Try our Samantha, our new voice AI agent.

LogicMonitor vs Stackify comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 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 Application Performance Monitoring (APM) and Observability
8th
Ranking in IT Infrastructure Monitoring
8th
Average Rating
8.8
Reviews Sentiment
6.8
Number of Reviews
54
Ranking in other categories
Network Monitoring Software (7th), Container Monitoring (4th), Cloud Monitoring Software (5th), AIOps (6th)
Stackify
Ranking in Application Performance Monitoring (APM) and Observability
62nd
Ranking in IT Infrastructure Monitoring
68th
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
Log Management (56th)
 

Mindshare comparison

As of October 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of LogicMonitor is 1.6%, up from 0.8% compared to the previous year. The mindshare of Stackify is 0.8%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
LogicMonitor1.6%
Stackify0.8%
Other97.6%
Application Performance Monitoring (APM) and Observability
 

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.
Moses Arigbede - PeerSpot reviewer
Head of DevOps at Partsimony
Easy to set up with great custom dashboards but needs to improve non-.NET infrastructure
They need to improve non-.NET infrastructure. We always had difficulty when it comes to reporting or metrics that come from Linux operating systems and Docker containers. For anything that runs within the Unix environment, we always had problems with them, however, if it was a document-based application, Stackify was 100%, it gave everything. Now, the aggregation agent, the metric agent for Stackify for Linux, collects everything. When I say everything, I mean, everything. It collects so much information that we now started to term it as useless data as all that ingestion will just come in and overwhelm your log retention limit for the month and really this spike up your cost at the end of the month. You'll need to do a lot in order to train down the data coming in from all your Linux environments, to get to what you really need, which actually takes some time as well. I would like to be able to see metrics about individual running containers on the host machines. Stackify has not really gotten that right, as far as I'm concerned. Netdata has done a better job and New Relic has also done a better job. They need to improve on that. We need to be able to see the individual resource usage of containers running within a particular host.

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 allowing us to implement it for 1,200 clients or 1,200 endpoints within three months, which went very well."
"LogicMonitor saves time in terms of its ability to proxy a connection through a device. For example, if you are troubleshooting a device, which you may want to connect to, you can proxy this connection through the platform. As a support resource, I don't need to use multiple platforms to connect to a device to further investigate the issue. It is all consolidated. From that perspective, it saves time because a resource now only needs to use one platform."
"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."
"LogicMonitor has helped our team to reduce the time needed to resolve incidents."
"LogicMonitor has a very highly talented support team that can answer the questions and help the customer right away."
"It is easy to set up and monitor an entire facility. This is crucial because we have around 80 facilities that require monitoring. LifePoint is a hub-and-spoke environment, so it is essential to understand all of the WAN interfaces."
"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."
"This is one of the excellent applications and portals I have used in my career, and it is a strong product for any enterprise, small, or medium-sized company that needs to handle or monitor large-scale devices, cloud devices, or servers."
"We switched from New Relic and Loggly as it provides us more info at a lower price."
"My advice to anyone who wants to use Stackify is to go for it because my experience with it is good."
"What stood out to us were the metrics and granular details we received."
"The filter feature on Stackify is one of the features I found valuable. It's awesome. When I want to get the application logs, the solution gives me many filters. For example, if I want to get logs from my test environment, the option is there for me to select the environment from Stackify, and you can also select the particular application, and you'll see the information you need there. The filter feature alone and the fact that Stackify offers a lot of different filters is what I like the most about the solution because I've used other tools with the filter feature, but the filtering was very difficult, versus Stackify that has good filtering. On Stackify, you can filter the information by the last one hour, or the last four hours, and you can also select the date range and specify the timestamp, then the solution will give you the information based on the date range you specified. Another feature I found valuable on Stackify is its rating feature because it tells you how your application is faring. For example, a rating of A means excellent, while a rating of F means very bad, or that your application is not doing well at all. The ratings are from A to F. I also like that Stackify helps you in terms of load management because the solution gives you information on overutilized resources. These are the most valuable features of the solution."
"The performance dashboard and the accurate level of details are beneficial."
"Within few hours of install we've identify the source of issue we've been investigating for few days and couldn't pin point."
"The solution is stable and reliable."
"It is very simple and very easy to configure."
 

Cons

"Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved."
"The one thing we've had issues with is that, when it comes to certain widgets on the dashboards, there are limitations on how many instances can be displayed through a widget."
"There is a lack of automation, especially in terms of remediating problems. The problem is seen and identified, but there is a need and a gap where LogicMonitor can help us automate the remediation of the problem."
"The APM part is somewhat lacking; they have made some attempts, but it is very rudimentary and I would not even categorize it as a solution to be honest."
"LogicMonitor tends to continuously ping the servers and the environment, which can create a lot of false alerts."
"LogicMonitor can be improved when we go to the settings page. In the new version, the navigation is easier but the buttons are very close to each other and sometimes when I'm clicking on something else, I'm clicking on the next button."
"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."
"LogicMonitor could be improved by making the initial setup a little easier and giving users more control over alerts."
"When I redeploy my solution and the application starts, I don't see the logs immediately, and it would take two to three minutes before I see the logs."
"I would like to be able to see metrics about individual running containers on the host machines."
"I'm looking to see more performance tools, but heard that they are going to release some."
"I've not used Stackify for a while, and I'm currently using a solution now that's not as good as Stackify. Among the solutions I've been using so far, Stackify has been one of the best for me, but there's always room for improvement. For example, I don't know if it's just me, but when I try to get the log from Stackify, sometimes it doesn't appear in real-time. It takes a few minutes before the logs appear. When I redeploy my solution and the application starts, I don't see the logs immediately, and it would take two to three minutes before I see the logs. I don't know if other customers have a similar experience. It's the wait time for the logs to appear that's a concern for me, could be improved, and is what the Stackify team should be looking into. In terms of any additional feature that I'd like added to the solution, I'm not sure if Stackify has a way to export logs out. I've been trying to do it. On the solution, you can click on a spiral-like icon and it shows you the entire error, and I'd prefer an export button that would let me download the error and save that into a text file, for example, so it'll be available on my local machine for me to reference it, especially because the log keeps going and as you're using the solution, the system keeps pushing messages on to Stackify, so if I'm looking at a particular error at 12:05 PM, for example, by the time I go back to my system and would like to revisit the error at 12:25 PM, on Stackify, the logs would have gone past that level and I won't see it again which makes it difficult. When you now go back to that timestamp, you don't tend to see it immediately, but if the solution had an export feature for me to save that particular error information on my local machine for reference at a later time, I won't have to go back to Stackify. I just go to that log, specifically to that particular export that I've received on my local machine. I can get it and review it, and it would be easier that way versus me going back to Stackify to find that particular error and request that particular information."
"Another improvement would be the agent memory utilization, which led to our recent reevaluation."
"It should be easily scalable and configurable in different instances."
"It's not easy to set up. It's hard especially for juniors to understand."
"The search feature could be improved."
 

Pricing and Cost Advice

"They are expensive for the cloud."
"We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month."
"As a managed services provider, the licensing model that LogicMonitor provides us is excellent. We are able to scale up and scale down as needed. The pricing is reasonable for the amount of features and support that they provide."
"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."
"The pricing can be a little aggressive. Right now, it's a bit much for smaller organizations to adopt it. But comparatively, it also provides good features."
"The license is annual, and I'm not fully aware of what it costs. We have a through-cycle that we go through, and they've been generous with us going above our limit. They're not strict on it. At the end of the year, they got us to renew. We always add some cushion for what we expect. Also, if you need custom monitoring or design work, you can pay them for consulting services."
"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."
"The licensing side of things with LogicMonitor, is quite simple. It is one license per device. Recently, you have additional licenses with things, like LM Cloud, which does confuse things a bit. Because it's very hard to estimate how many licenses you're going to need until you're monitoring it, so it's quite hard through that process to give a customer price to say, "This is how much this services will cost.""
"The price is variable. It depends on how much data we have received in that particular month. Usually, it goes up to $2,000, or, at times, $3,000 USD per month."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
917,403 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Outsourcing Company
10%
Financial Services Firm
9%
Computer Software Company
8%
Comms Service Provider
19%
Construction Company
19%
Outsourcing Company
8%
Performing Arts
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise13
Large Enterprise33
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise2
 

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 is your experience regarding pricing and costs for LogicMonitor?
My experience with pricing, setup cost, and licensing is that the licensing model has changed and is very confusing as it currently stands and overly complicated.
What needs improvement with LogicMonitor?
I think LogicMonitor can be improved by having alert prioritization. Sometimes important alerts get delayed while unimportant alerts come through, so prioritization would help address this issue. A...
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about LogicMonitor vs. Stackify and other solutions. Updated: September 2026.
917,403 professionals have used our research since 2012.