What is our primary use case?
We primarily use it for network-wide event monitoring and incident backtracking. It helps us identify what events caused certain incidents and understand how they happened.
It's also useful for incident tracking and investigating.
How has it helped my organization?
Having a functional event and log analyzer is crucial for any organization, especially considering ISO mandates. It has helped us meet those requirements and integrate all our functional-level needs. It has greatly facilitated our daily operations and compliance.
What is most valuable?
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, including printers. It's extremely useful for daily operations.
What needs improvement?
There is room for improvement, especially in the reporting aspect. The reports are not as good as those in Splunk. Another area that needs improvement is the integration of various technologies. Currently, they don't cover most of the major technology domains, leaving out significant coverage.
Moreover, there are many additional features I would like to see. One feature would be an automated workflow for report downloading and sending it to relevant individuals.
Additionally, there should be event triggers to identify and handle duplicated events. It would be helpful to have AI-driven technology to differentiate between real and false alerts, as we receive numerous false positives. Not every event is critical, so an intelligent analysis, such as behavior-driven or logic-based, should be incorporated to suppress unnecessary alerts.
So, I want to decrease false positive instances. I would like to see a significant decrease in false positives based on intelligent analysis. The analysis could be behavior-driven or based on any logical approach, but it should be incorporated into the system.
For how long have I used the solution?
We have been using this solution for three years. The version we use is the Logs and Event Log Analyzer.
What do I think about the stability of the solution?
It is a stable solution. I would rate it an eight out of ten.
What do I think about the scalability of the solution?
Scalability is purely license-based. So I would rate the scalability a six out of ten.
Moreover, it's not just the license; there are also some technological limitations. It doesn't support all brands of devices; only a limited set is supported.
If we need to add something new, we have to request it from the engineering team, and they assess whether it's doable or not. If it is, then it goes into a queue for development and gets added in a new update. So, it depends on that.
It's mainly monitored by one or two people as a tool that oversees the entire network. In our organization, it's primarily used for capturing information. If someone needs details about a specific duration, the admin of the tool can log in and provide the necessary information.
It can assist in investigations, incident analysis, trend analysis, and more. It's used 24/7. We utilize its maximum potential.
How are customer service and support?
Mostly, we are satisfied with the support. However, there are times when we require development for something that is not in the system, which can cause delays and require more coordination.
But the regular support is fast.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used SolarWinds. We switched to ManageEngine Log360 because there was a significant security incident worldwide related to SolarWinds. I believe it happened in the US Pentagon, and many organizations were affected. It was around 2018 or 2019.
We evaluated OP5 as well, but ManageEngine Log360 is comparatively cheaper. It is also simpler to use compared to OP5. In terms of features and meeting our specific requirements, ManageEngine Log360 offered a better fit than Splunk.
We needed multiple functionalities within the ManageEngine suite, and Log360 fulfilled most of our requirements. The only downside was the reporting feature, but overall, it provided the capabilities we needed. Splunk, on the other hand, is primarily focused on log management and reporting.
How was the initial setup?
The initial setup was not easy. I would rate my experience with the initial setup a three out of ten, where one is difficult, and ten is easy.
Even with a technical background, you would need expertise in each area to map it for their specific technology. Each technology has its own configuration process.
For us, it took around two weeks to deploy ManageEngine Log360.
What about the implementation team?
Software deployment is straightforward, but the configuration to meet our specific requirements took significant time. We had to work with individuals from different areas like applications, systems, networks, and databases. It took around two weeks due to the dependencies and customization involved. There is no way to bring a pre-installed solution.
The deployment required the involvement of around four to five people with different job roles, such as application admins, system admins, server admins, network admins, and database admins.
However, only the vendor provides maintenance under an active Annual Maintenance Contract (AMC). The vendor performs regular checks and upgrades and manages incidents. We have multiple applications in our suite, and the vendor manages the maintenance for all of them.
What was our ROI?
ROI wasn't an issue. The basic requirements are being met, so the returns on investment were already captured within the first two years of implementation.
The main concern is how advanced and competitive it is compared to other players in the market. That's where it falls short.
Otherwise, the return on investment is 80% within the two-year investment period.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing a four out of ten, where one is low price and ten is high price. It is affordable. The price is fixed, there are no additional costs to the standard license.
Which other solutions did I evaluate?
We were using SolarWinds. But, we moved to ManageEngine.
What other advice do I have?
I would suggest evaluating other solutions. I am not very happy with this solution.
Overall, I would rate the solution a six out of ten. There are some shortcomings in terms of technology that haven't been addressed yet, as well as reporting.
Additionally, there are false positives, and there's an accumulation of irrelevant data over time, which is not what we expect to see.
Which deployment model are you using for this solution?
On-premises