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

ManageEngine Log360 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

ManageEngine Log360
Ranking in Log Management
19th
Average Rating
7.4
Reviews Sentiment
6.9
Number of Reviews
17
Ranking in other categories
Security Information and Event Management (SIEM) (18th), User Entity Behavior Analytics (UEBA) (10th)
Stackify
Ranking in Log Management
61st
Average Rating
7.8
Number of Reviews
6
Ranking in other categories
Application Performance Monitoring (APM) and Observability (61st), IT Infrastructure Monitoring (59th)
 

Mindshare comparison

As of August 2025, in the Log Management category, the mindshare of ManageEngine Log360 is 1.1%, down from 1.1% compared to the previous year. The mindshare of Stackify is 0.2%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Log Management
 

Featured Reviews

Md Abdul Hakim - PeerSpot reviewer
Integration capabilities impress while room for improvement exists in cloud compatibility
1. Enhanced Cloud Integration Current Gap: Log360 lacks native integration with Microsoft Intune and cloud-based Active Directory (Azure AD), limiting visibility for organizations transitioning to hybrid or fully cloud environments. Requested Improvements: Direct Intune Log Collection: Ability to ingest and correlate logs from Intune-managed devices to monitor compliance, device health, and security policies. Azure AD Deep Integration: Support for Azure AD audit logs, conditional access events, and identity protection alerts to provide end-to-end visibility. Cloud Workload Monitoring: Extend coverage to SaaS applications (e.g., Microsoft 365, AWS, GCP) for unified threat detection. Why It Matters: Many clients have migrated from on-prem AD to cloud-first setups this year. Without cloud-native log collection, critical security events (e.g., rogue Intune policies or Azure AD breaches) go unmonitored. 2. Improved Automation and Response Current Gap: Limited automated remediation (e.g., auto-isolating compromised devices) forces manual intervention. Requested Features: Playbook Automation: Pre-built workflows to auto-resolve common issues (e.g., disabling users after brute-force attacks). SOAR Integration: APIs to connect with SIEM/SOAR platforms (e.g., Splunk, Palo Alto Cortex) for escalated threat response.
Kalyan Somisetty - PeerSpot reviewer
Simple, easy to configure, and offers trial versions
In the next version, which I want to try, it'll show the comparison of the old responses of the APS. For example, how much time the old response and the new response with the changes. Right now, I cannot differentiate. The graphical interface should be able to capture nicely how much time it has taken and it should be very clear. Sometimes it confuses us. For example, what is this APA for? What were the average responses and how many requests have happened? It needs to give a clear picture. They should enable request and response capturing in the Stackify user interface to show what the request for the APA is. Then, it'll be very good. It should be able to capture the payload. For example, what is the request and what is the response? If it has a nice way of capturing everything then it would be easy. There is no need of using ELK again for logging. As of now, people will use Stackify or maybe Grafana for seeing the stats of the application or responses, however, it doesn't have the capabilities to show everything. People will go for any exception handling or checking the request and response in the ELK. If Stackify can do this future, then it'll be an easier single tool. It is anyway intercepting the logs, application logs. I don't think it's a big matter to capture extra data with the requested response. That requested response capturing also should be configurable since some people want the question response to be captured and for the people that don't want it, we can use that feature. It can be enabled as desired. Many people are using different monitoring tools like ELK, LogStash, and Splunk - many other tools. However, if you can make this kind of performance tool cover everything, then they will not shift to other solutions. It should be easily scalable and configurable in different instances. For example, if the same application is scaled up to differently, it should be easily integrable into Kubernetes pipelines. They should offer plugins to make it more easily integratable. For development enrollment, it should be free to use.

Quotes from Members

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

Pros

"The most valuable features for us are the application logs monitoring and the dashboard, which provides a single-pane view of all the ongoing activities."
"The deployment is quite simple and pretty straightforward."
"ManageEngine Log360 is not difficult to deploy."
"The Sharecon feature is the most valuable."
"The reports that you can run are really nice."
"My main objective for using ManageEngine Log360 is its powerful and real-time capabilities for managing security and other tasks efficiently."
"The product is very user-friendly."
"It is nice to be able to monitor and to have notifications."
"The solution is stable and reliable."
"The performance dashboard and the accurate level of details are beneficial."
"The deployment is very fast."
"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."
 

Cons

"While ManageEngine Log360 is a significant improvement, there could be enhancements in terms of integrating more user-friendly training materials and better deployment documentation."
"On the logging system, there's a local on-client side that is encrypted, and there's one that is not encrypted. It is only for diagnostical purposes. However, both being encrypted would be very valuable for some audits."
"We can log in as a local user, and it's fine, but when we login with an Active Directory user, we cannot."
"It is not expensive compared to other solutions."
"The integration with SharePoint and Teams should be improved."
"Log360 currently cannot gather information from Intune logs or cloud-integrated systems."
"Their technical support should be improved."
"The support needs improvement."
"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."
"It should be easily scalable and configurable in different instances."
"I would like to be able to see metrics about individual running containers on the host machines."
"The search feature could be improved."
 

Pricing and Cost Advice

"My client has a yearly license. I think the cost is not expensive compared to that of other SIEMs, given the service it is providing."
"Its pricing is definitely huge compared to some of the other SIEMs. Its price should be improved."
"Affordable pricing is provided by the solution."
"There is a cost for each feature used."
"ManageEngine Log360 is expensive compared to other products."
"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 Log Management solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Manufacturing Company
9%
Financial Services Firm
7%
Healthcare Company
6%
Financial Services Firm
15%
Computer Software Company
9%
Media Company
9%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for ManageEngine Log360?
The price is suitable from a perspective of different pricing options. We already have an ongoing project where some features analytics can be escaped, and companies can manage their budgets carefu...
What needs improvement with ManageEngine Log360?
1. Enhanced Cloud Integration Current Gap: Log360 lacks native integration with Microsoft Intune and cloud-based Active Directory (Azure AD), limiting visibility for organizations transitioning to ...
Ask a question
Earn 20 points
 

Overview

 

Sample Customers

First Mountain Bank, TRA, Citadel Group, OnPoint Financial Corp, Florida Dept. of Transportation
MyRacePass, ClearSale, Newitts, Carbonite, Boston Software, Children's International, Starkwood Media Group, Fewzion
Find out what your peers are saying about ManageEngine Log360 vs. Stackify and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.