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

LogicMonitor vs Stackify comparison

 

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
10th
Ranking in IT Infrastructure Monitoring
8th
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
46
Ranking in other categories
Network Monitoring Software (6th), Container Monitoring (4th), Cloud Monitoring Software (6th), AIOps (6th)
Stackify
Ranking in Application Performance Monitoring (APM) and Observability
60th
Ranking in IT Infrastructure Monitoring
66th
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
Log Management (57th)
 

Mindshare comparison

As of June 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of LogicMonitor is 1.6%, up from 0.7% compared to the previous year. The mindshare of Stackify is 0.7%, up from 0.2% 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.7%
Other97.7%
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.
IE
Senior Software Engineer at a tech services company with 1,001-5,000 employees
Has good filtering and rating features and helps with resource and load management
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.

Quotes from Members

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

Pros

"The initial setup is very simple."
"We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status."
"LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support."
"LogicMonitor helped reduce the length of an outage of a facility because of the identification of a fiber cut, so my company was able to be on top of that faster, so in that respect, the product gave us less than one year's worth of ROI."
"Since using LogicMonitor, I have improved infrastructure visibility, which has resulted in faster incident response, reduced downtime, better capacity planning, and a significant reduction in manual monitoring efforts, providing me with substantial benefits."
"LogicMonitor enables us to consistently really wow the customers by sorting that out."
"LogicMonitor really improved our workflow as a company."
"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."
"The performance dashboard and the accurate level of details are beneficial."
"It is very simple and very easy to configure."
"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."
"We switched from New Relic and Loggly as it provides us more info at a lower price."
"The deployment is very fast."
"My advice to anyone who wants to use Stackify is to go for it because my experience with it is good."
"Within few hours of install we've identify the source of issue we've been investigating for few days and couldn't pin point."
"What stood out to us were the metrics and granular details we received."
 

Cons

"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."
"Delayed detection is a significant issue. Because of high load on the infrastructure, sometimes I will not find the alert immediately."
"LogicMonitor has a few areas that need improvement, such as more simplified customization for advanced monitoring, better pricing flexibility for smaller organizations, improved reporting templates, and an easier onboarding process for beginners."
"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."
"While dynamic alerting is great, the overall alerting system can be complex to configure."
"This is one thing that is a pain and flaw with LogicMonitor."
"The reporting capabilities are within average."
"If you only want to use LogicMonitor in the cloud, there's a better tool available."
"One thing that happens as a new user on Stackify is when you install the agent it pulls everything and if you're not careful, your log allowance will just be exhausted as you are actually pulling too much data."
"Another improvement would be the agent memory utilization, which led to our recent reevaluation."
"It's not easy to set up. It's hard especially for juniors to understand."
"It should be easily scalable and configurable in different instances."
"Better mobile support."
"I would like to be able to see metrics about individual running containers on the host machines."
"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."
"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."
 

Pricing and Cost Advice

"In terms of pricing, I would rate LogicMonitor four out of five."
"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 features were very valuable to us because we could consolidate them into one platform and have a good user experience with the platform, our accounts, and the support team. That was the key driver for us. That was what we were looking for. We looked for a comprehensive solution that could provide advanced features all in one platform, and LogicMonitor was the solution that we chose. It definitely has a premium price. However, you are getting what you pay for in a very effective way. That was important in our decision-making.The features were very valuable to us because we could consolidate them into one platform and have a good user experience with the platform, our accounts, and the support team. That was the key driver for us. That was what we were looking for. We looked for a comprehensive solution that could provide advanced features all in one platform, and LogicMonitor was the solution that we chose. It definitely has a premium price. However, you are getting what you pay for in a very effective way. That was important in our decision-making."
"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."
"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."
"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."
"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.
902,270 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
12%
Financial Services Firm
11%
Computer Software Company
10%
Healthcare Company
7%
Construction Company
21%
Comms Service Provider
13%
Media Company
9%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise12
Large Enterprise27
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?
I do not manage the pricing, setup cost, and licensing for LogicMonitor.
What needs improvement with LogicMonitor?
LogicMonitor tends to continuously ping the servers and the environment, which can create a lot of false alerts. Another thing is that it is not very good for application monitoring.LogicMonitor ca...
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: June 2026.
902,270 professionals have used our research since 2012.