Infrastructure Monitoring and Observability Platform

LogicMonitor  is primarily used for observability and data collection.

As a service provider, I believe the biggest benefit from LogicMonitor  for my clients is that it provides full-stack infrastructure observability. It is a very robust solution that combines all types of telemetry in terms of infrastructure observability. In addition to that, the latest additions to their portfolio in the last couple of years, with the acquisition of what is now called Edwin AI for event management and subsequent enhancement of that very same part of the portfolio to increase event correlation and AI-based features, represent a very big benefit. Last year, they acquired Catchpoint , which is also a tremendous benefit in terms of addition to end user and digital experience. They are building a very strong suite that is not very commercially attractive from a service provider point of view, but definitely, if the customer is looking for premium infrastructure observability, it is one of the most mature solutions that I have seen so far.

In terms of functionalities, I do not work much with Dynamic Service Insights for real-time visibility. I understand what they want to do. The mapping of infrastructure and applications and cloud services, and aligning the dependencies to show the business services that the customer has is absolutely fantastic if it is an end user customer that is a medium SOHO or medium segment customer that does not have a very big environment. Personas such as CIOs or SREs can see at a glance the service health of their business services. It is an acceptable functionality.

I do see negatives and areas for improvement in LogicMonitor. Obviously, there is always space for improvement. First of all, I believe the commercial aspects require improvement. At the moment, if I subscribe to everything on the platform, it becomes quite a large cost. Although it has many benefits, an observability solution, even a full-stack observability solution, should not exceed a maximum of eight percent of the annual budget of the environment. If I buy everything, I will definitely exceed that percentage.

In addition to that, I believe one of the biggest drawbacks that does not make LogicMonitor stand out like Dynatrace  or DataDog is that they have not focused on the APM  side. Application Performance Monitoring  is crucial; if we have a customer with many applications needing instrumentation, or even SaaS platforms monitoring, this is where LogicMonitor loses ground. 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. I would very much like to see them invest in this area to start competing against DataDog.

The principal thing that differs LogicMonitor from Dynatrace  and DataDog is the APM side. Application instrumentation is essential, as only by adding that will you become a full-stack observability solution. At the moment, they are only an infrastructure full-stack and infrastructure-focused solution.

I started using LogicMonitor eight years ago.

LogicMonitor is ninety-nine percent stable all the time.

LogicMonitor is highly scalable. I would describe it as very scalable.

In terms of customer service, I would divide my answer into two points. Professionally, I think they have very knowledgeable staff in their environment, and support is good most of the time. To be specific, I have no concerns; I think they are doing a good job. Occasionally, we face some challenges, but overall, I see it as very good support. I have experienced far worse.

In terms of deployment procedure, I find it very straightforward. The main instance is up and running in twenty-four hours. Deploying collectors is also substantially easy, so I do not foresee much problem there; that is actually an accelerator.

The effectiveness of Edwin AI can be measured depending on what I am trying to achieve. There are several aspects of Edwin AI. One is event management, which is simple event management as they started, and it is quite robust. The measurement of the effectiveness is the reduction of the number of incidents that are created, so it involves basic root cause analysis in this case. Then I have the second part where the AI capabilities, or in other words, AI intelligence comes in, and they position their own LLMs to give an AI flavor of the analysis of the issue. In this case, they enhance the correlation based on ingestion of their own service graphs, either taking from the ServiceNow  topology maps or taking from the additional information from their own topology that they have in LogicMonitor, which they now call Envision , but it is LogicMonitor Core. They provide quite a substantial enhanced capability in terms of correlation. Subsequently, the generative AI algorithm that they have is useful to summarize the issue and provide outcomes. With the addition of the chatbot capability, it is quite robust and a good functionality. The last part is basically the ability to have, which they have launched very recently, the AI Control Tower , which gives me the ability either to use the AI agents that are already in place, to substantiate the agent AI point of view, or to create my own, which is a very good addition.

The only drawback is that I am limited to use the LLM from LogicMonitor. While the industry nowadays is more oriented for the user to choose which LLM they want to use, that is a current limitation. This is a capability in development. I know they will launch this because the market is demanding and their competition is already doing that. But I do not see a showstopper for the adoption. I do believe that they should launch this capability and enable us to use our own LLMs. For instance, if I have something like either Copilot from Microsoft or Bedrock from Amazon or Gemini  from Google, or even my own hosted, self-hosted option, I want to use that. Why would I need to pay for additional LLM tokens if I already have my own LLMs? This is a very concise standardization of the industry at this point in time. Many other players are already doing that and this will be no different.

Incident management is part of the Edwin AI point of view. All three functionalities that I have just described are part of incident management. Basically, what it is, is I create an incident in whatever ITSM  tool or solution that I am using, based on the correlation on the output of Edwin AI. I am referring to autonomous learning. Autonomous learning is basically the feature of Edwin AI. They have their own LLM which keeps learning the patterns, which I consider more a machine learning algorithm than actually AI. But it is sufficient at the moment; I think they are on a good path since they launched this capability about six or seven months ago. I would say that I have not seen many hallucinations, at least in the environments that we have deployed, which means I give a positive note on that.

Regarding LogicMonitor's impact on our mean time to resolve incidents (MTTR), I want to emphasize that where we have deployed Edwin AI, we see our MTTR decreasing substantially. I am talking about real numbers and not the numbers they provide. The statistics will circulate depending on the maturity of the environment, since that is a KPI that must be considered. The data foundation is the principle of the effectiveness of MTTR reduction with Edwin AI. In a normalized mature environment, I would say that I see a reduction in resolution times of forty-two to fifty percent. This happens because we substantially reduce the number of incidents that are generated. Therefore, there is an obvious reduction, but the industry standard is slightly higher or at least demands to be a bit higher. Again, it comes back to the point that I just mentioned; it depends on the maturity of the customer.

Regarding whether LogicMonitor's solution is rather expensive, I say that if I evaluate the value, it is substantial. First of all, you need to understand that I am speaking from a service provider point of view, not that of the end customer. Even for the end customer, it would be slightly difficult if they buy everything. However, the value drawn from it is considerable. If they have the budget to spare, it is a very good solution. From an MSP point of view, it becomes unattractive because it inflates our commercial proposals to the customer. The customer, in a managed services context, does not see the solution bringing cost XYZ; they see the overall cost of the service we are providing. Not to mention that nowadays, there is a lot of competition, especially with the trend towards open source, where customers sometimes choose to go open source instead of buying an enterprise product, even one as mature as LogicMonitor.

We do not purchase anything from LogicMonitor through the AWS Marketplace ; we buy licenses directly. Our labs, however, do run on AWS , so as an end-user consumer of AWS , we have many services there. There are some challenges in gaining complete visibility across my hybrid infrastructure and I observe that the Envision  platform addresses these challenges. Usually, I do not see many challenges onboarding the environment into the platform because it can adapt quite easily. If it is not there, we can always ask LogicMonitor to address these points, which they frequently do in the majority of cases, either in a quarter. So I do not encounter problems with that. My main concern nowadays is how to extract data from LogicMonitor. I need to combine data in a unified manner in the era of data lakes to mix operational and non-operational data outside them. However, extracting data is particularly difficult due to their low API rate limits. I understand the reason behind the low limits, ensuring no one overloads the platform, but it makes integration stressful. I would rate this review an eight overall.

My use case for LogicMonitor  is to create alerts, specifically to create PagerDuty alerts and Slack alerts for high usage of memory, high performance, and similar issues, ensuring the infrastructure is up to date.

I can say it has reduced my mean time to resolve by almost 30-35%.

The best features of LogicMonitor  are that the monitoring is excellent compared to other products in the market. The alerts are accurate, and it is agentless; you can automate it, and we don't need human intervention, as it automatically discovers the devices so you don't have to do it manually. It supports a hybrid cloud model and multi-cloud model monitoring.

I have used the Dynamic Service Insight feature for real-time visibility for one of my clients to monitor individual devices' health. They had a lot of devices, but they wanted to monitor them individually and automatically group the devices to check their alerts, check their service level score, and check the dashboards in real-time.

I have used LogicMonitor's Edwin AI for diagnosing root causes and remediation to reduce the noise alerts that come in. It reduced the noise alerts significantly, almost close to 90%.

Areas that have room for improvement in LogicMonitor include that the product should be a plug-and-play system. The dashboards should be customizable, as there are products in the market such as Grafana  which are quite customizable. I think the product is expensive when looking at products in the same segment in the market. The reporting should be customizable and more advanced when looking at Edwin AI. Log management should be easier, similar to Splunk or Elastic.

I have been using LogicMonitor for around two years.

Regarding stability, I can say there is mostly no downtime, so I rate it a 10; I think 10 would be a good number.

The solution does require maintenance, such as checking the devices, discovery of the devices, and checking if any ports are blocking, but usually it is agentless.

I would rate the technical support of LogicMonitor as eight.

I estimate that the return on investment for me and my clients is around 90%.

I compare LogicMonitor mostly with Grafana  and Splunk. Splunk has strong analytics capabilities, Grafana is more of a cloud infrastructure application, and Nagios is legacy software in the market for network monitoring. Since LogicMonitor performs much the same job, I expect it to do the core job better.

I would suggest DataDog, but if the budget is good, DataDog would be a good option or Splunk. However, looking at the organization level and budget, LogicMonitor is also a value for money product.

Regarding the autonomous learning feature, I have not used it much.

The challenges I face in gaining complete visibility across my hybrid infrastructure involve discovering the devices, as it's somewhat challenging and sometimes it misses a couple of devices.

My clients include small, medium, and enterprise businesses, as I work with all three of those types.

In my organization currently, I can say the entire team, which is almost 40-45 members, works with LogicMonitor.

I am providing this review with an overall rating of 9.

My main use case for LogicMonitor  is monitoring the network devices in the environment.

For example, I monitor switches, UPS, routers, network devices like internet service providers, and all kinds of network devices.

I also segregate sites and devices by adding them into user groups and checking if any specific site went down to monitor it through LogicMonitor . I also check the configuration of the devices and have multiple uses for the platform.

The best features LogicMonitor offers are real-time updates on the devices and their health status, with all information available at one site. I can log in on the device from the tool only.

When I mention real-time updates and being able to log into the device from the tool, it gives a full view of the devices so that I can rectify issues quickly.

LogicMonitor has impacted my organization positively by reducing the troubleshooting time and providing real-time monitoring of device health to keep the devices up and running.

There is a significantly decreased response time. Before using LogicMonitor, it used to take 20 to 30 minutes to rectify an issue, but now it takes around 15 minutes.

I think LogicMonitor can be improved by including AI capabilities and putting suggestions such as if a UPS is down, there might be a power issue, or if only a switch is down, maybe check the cable. The platform could check routing issues and add suggestions on the device itself about what the issue might be to summarize the problem.

Regarding LogicMonitor's AI capabilities, I think its governance and security are in initial phases, so reliability is low.

Regarding the accuracy and reliability of LogicMonitor's AI output, I would rate it at 80 percent.

I have been working with LogicMonitor for two and a half years.

I had a great experience with LogicMonitor, and I found the review questions to be insightful. I give this product a rating of 8.

I am a customer of LogicMonitor  and have handled B2B business. My usual use cases for LogicMonitor  involve our cloud resources and on-premise resources. I have used LogicMonitor for monitoring devices, servers, and websites. I have around 11 collectors and 1,000 devices onboarded for my client account, Welsh Water. I am from Infosys and used LogicMonitor for Welsh Water, so basically it is B2B.

The impact of LogicMonitor solution on my team's mean time to resolve incidents involves automated ticket polling. When we set a limit, it automatically closes the ticket if it is resolved. This saves a lot of time and I don't need to go through piles of unwanted errors. Automated error recovery is something I really appreciate.

Another thing is the scheduling of reports, which saves most of my time and energy. The error handling mechanism comes with a scope, and we have RBAC enabled. Those who know can approach it and nobody else is going to see what is happening in the other team. It helps the team directly resolve errors. Half of the errors which are invalid go away, and half of the errors which just need to be acknowledged can be scheduled as a report and solved by each individual team. This reduces time and energy significantly.

The feature and capability of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

The Partner Academy supported by LogicMonitor is a feature I could highlight and really liked. Learning about the tool is possible through this platform. I can see an instructor teaching me the implementation of LogicMonitor. We don't have many other resources to study about the tool, and we have very limited resources available. The partner portal is one such feature I appreciated.

The latest version has features that satisfy me greatly. I am impressed with the look of the new version, the design, and the dashboard options. It has more tabs but is very easy to navigate with everything on one page. The UI and UX design made as a new feature in LogicMonitor is something I appreciate. I usually use one feature where I can see the resources in a hive structure. All the resources can be seen in a hive manner, with everything color-coded basically in three colors for error, warning, and good status. If anything is coded in red, I can go to that and easily see it. I have seen this feature on the resources page or maybe in the dashboard page where every service and website is shown. My usual health checkup is much easier with this feature.

The collector was really good and I had a good experience with it, especially on load balancing. There exists automatic load balancing which I really appreciated.

LogicMonitor's 24/7 monitoring is a feature I really appreciate. It saves me from the night shifts and I don't need to worry about it. It handles both business time and off-business time without my consent in an automated manner.

LogicMonitor can be improved when we go to the settings page. In the earlier version, it was pretty simple where I had to navigate individually to the individual settings. In the new version, the navigation is easier but the buttons are very close to each other. Sometimes when I'm clicking on something else, I'm clicking on the next button. I need some good alignment to happen on the settings page.

I have been using LogicMonitor for about five years.

I evaluate how stable and reliable LogicMonitor is, and I don't find it unreliable because even the chat is happening very confidentially. I don't think it is unreliable from my end. I have never felt any power issues or power backup issues from LogicMonitor. Whatever I have made for my collector as a backup always stayed in place.

One day I made a mistake by shutting down all the servers at once and I haven't touched anything with it. I went to see the mistake after some 12 hours. When I clicked it on and gave access again, making everything active, every alert was there. Whatever happened within that 12 hours was recorded there. Even if it was not kept in active mode, it somehow gave me all the data. That is the stand-alone stability of LogicMonitor.

I can rate the stability of LogicMonitor from one to ten as eight because it is not classified properly. Though we have the common three classifiers of warning, error, and critical, I expect some classification if it happens for piles of emails or piles of errors. However, I can give it an eight.

I evaluate how scalable LogicMonitor is and I can give it a nine because of its very good UI, except for the spacing in the buttons. It is very navigable and we can navigate to anything very easily and quickly. I can give it a nine. When I am about to learn something, the interface presents it in a way that is easy to understand. When I look at the resource page, I can learn all the cloud resources we are having and the number of devices we are having very quickly. In order to understand the architecture, it is very easy for me. When it comes to adaptability, I can give it a nine as well.

The features and capabilities of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

My communication and interaction with technical support shows they won't make anything out of the league. They maintain their confidentiality between us and the client very well. They also have a corporate approach and what we have discussed will be released via email, which is very perfect. We have quick assistance where they go into the server, look for the issue, and if they find anything, they report to us immediately and within 10 to 15 minutes it is resolved. Rapid problem solving is what I would say in one word. It is very fast.

I can rate technical support from one to ten as nine, definitely nine.

Before LogicMonitor, I used a different solution for the same use cases, and it was SolarWinds. The reason I decided to stop using SolarWinds is that SolarWinds requires agents, as basically all other monitoring and observability tools have this agent to be used, and there is no built-in API with that. LogicMonitor is having REST API and is also agentless, which makes it more advanced.

The challenges I faced in gaining complete visibility across my infrastructure involve especially working with the syslog and the tags. There are many tags for a particular server which I am not confident about which ones we are using and for which purposes we are using them. That is something I really stuck on, but as we don't use them much, I am comfortable with the current setup.