We performed a comparison between Elastic Observability 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 ability to ensure that the data is searchable and maintainable is highly valuable for our purposes."
"The product has connectors to many services."
"The Elastic User Interface framework lets us do custom development when needed. You need to have some Javascript knowledge. We need that knowledge to develop new custom tests."
"Elastic APM has plenty of features, such as the Elastic server for Kibana and many additional plugins. It's a comprehensive tool when used as a logging platform."
"The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization."
"The solution is open-source and helps with back-end logging. It is also easy to handle."
"Machine learning is the most valuable feature of this solution."
"For full stack observability, Elastic is the best tool compared with any other tool ."
"LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
"We have very fine-tuned alerting that lets us know when there are issues by identifying where exactly that issue is, so we can troubleshoot and resolve them quickly. This is hopefully before the customer even notices. Then, it gives us some insight into potential issues coming down the road through our environmental health dashboards."
"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."
"LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical."
"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."
"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."
"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's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that."
"The auto-discovery isn't nearly as good. That's a big portion of it. When you drop the agent onto the JVM and you're trying to figure things out, having to go through and manually do all that is cumbersome."
"The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities."
"If we had some pre-defined templates for observability that we could start using right away after deploying it – instead of having to build or to change some of the dashboards – that would be helpful."
"They need more skills in the market. There are not enough skills in the market. It is not pervasive enough on the market, in my opinion. In other words, there isn't a big enough user base."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"The cost must be made more transparent."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"The price is the only issue in the solution. It can be made better and cheaper."
"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."
"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."
"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."
"Role-based permissions could be better and updating modules could be smoother."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
"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 drawback of LogicMonitor is its licensing model, which requires an additional license for each module. For example, if you need to use Azure monitoring, you'll need an additional license on top of the base license."
"There are some very specific things that need improvement in LogicMonitor. One is the lack of formatting for customized alerts, particularly the delivery of them to our email channel. We'd also like to see further customization of dashboards. Finally, something that is specific to us as an MSP that uses LogicMonitor, is white-labeling or skinning of the product, so we can make it look more customer-focused for our customers."
Elastic Observability is ranked 10th in IT Infrastructure Monitoring with 22 reviews while LogicMonitor is ranked 15th in IT Infrastructure Monitoring with 25 reviews. Elastic Observability is rated 7.8, while LogicMonitor is rated 9.0. The top reviewer of Elastic Observability writes "The user interface framework lets us do custom development when needed. ". 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". Elastic Observability is most compared with Dynatrace, New Relic, AppDynamics, Azure Monitor and Sentry, whereas LogicMonitor is most compared with SolarWinds NPM, ScienceLogic, Zabbix, SCOM and OpsRamp. See our Elastic Observability vs. LogicMonitor report.
See our list of best IT Infrastructure Monitoring vendors and best Cloud 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.
