LogicMonitor Reviews

My main use case for LogicMonitor is to monitor all the networking devices deployed in our on-premises network.

Whenever the network goes down, I receive an alert from LogicMonitor indicating that a node or device is down, which allows me to check and troubleshoot the device physically or review the logs to determine the issue, how many packets were dropped, and other relevant details.

LogicMonitor provides me with the total number of devices present in the network and allows me to see how it monitors the networking scenario.

LogicMonitor offers the best capabilities, including capturing the node status, checking whether the network is down or up, and seeing how the network is actually working.

I can create customized widgets in the dashboard, which helps me check on networking equipment whether they are servers, switches, Layer 3 devices, access devices, printers, or anything else. If any device goes down, it alerts me immediately.

In LogicMonitor, I can view the node, configure it, manage the bandwidths, and if a node is down, I can manually change the path.

After deploying LogicMonitor, I can get information about the device condition within one to two seconds and receive alerts. Yellow alerts appear first, and when they exceed a set interval of time, red critical alerts come through, which helps my organization check on critical issues.

The alerts and emails sent to customers could be improved and delivered more directly.

The interface is acceptable, and I do not have any suggestions for it.

SNMP configurations and deployment guides could be more user-friendly for engineers deploying the solution.

I have been using LogicMonitor for one and a half years.

The main challenge occurs when LogicMonitor goes down while the physical device is actually up. Sometimes physical devices are functioning properly, but LogicMonitor is unable to detect this, which results in unnecessary ticket generation that my team must address.

Occasionally, the monitoring does not function properly, and minor issue tickets are generated unnecessarily, requiring my team to resolve them.

LogicMonitor is a properly scalable solution.

Customer support is good and they respond on time, though they could improve their services further.

We were previously using SolarWinds, though I was not fully aware of its complete capabilities. My company switched to LogicMonitor with the decision that it would reduce downtime.

I have seen a return on investment for the employees involved. When manual work was being performed, downtime was very high and significantly impacting the business. After deploying LogicMonitor into the hybrid cloud environment, money was saved. Ultimately, LogicMonitor saves my organization time. Deploying LogicMonitor into the hybrid cloud in our setup achieves both objectives of saving money and saving time.

For licensing, I raise queries and take approval from the owner or client. They handle the licensing portion and manage pricing decisions. Clients care about the pricing, and they provide the license for us to work with.

I am still exploring the AI capabilities of LogicMonitor and learning about cloud solutions. Dynamic services does not interrupt my work, and I follow its processes accordingly.

LogicMonitor has helped me resolve issues faster. As alerts come through, I directly check the interfaces or nodes that are down, and I examine the mean time to resolution to determine how I can bring the device back up. I can also push configuration changes if a device is completely down, which is the best part.

When using LogicMonitor, I recommend creating customized widgets according to your specific problems and solutions, and placing all critical nodes on the same dashboard for proper monitoring.

LogicMonitor partners with us and checks everything including business support and customer satisfaction alongside the timeframes in which clients can be satisfied.

My overall review rating for LogicMonitor is nine out of ten.

Hybrid Cloud

Google

I work as a consultant providing solutions to customers, and I use cloud native services for monitoring. I primarily recommend CloudWatch, and if the customer has a preference for a third-party tool, I provide solutions for DataDog or other services.

I function as an architect in cloud services, particularly hybrid cloud. I need these tools and services that I always offer to customers. When I design solutions, I provide a monitoring solution and recommend these services.

I have multiple customers to whom I have recommended monitoring tools. I have worked on many projects including McAfee, CarMax, AMC, and American Media Corporation. I have recommended these services across different projects.

I have been using CloudWatch for more than ten years. I primarily recommend CloudWatch because customers do not want to spend additional money on other tools. I would recommend a native service so they can save cost. AWS is introducing synthetic monitoring for applications, which is crucial for precise monitoring. AWS X-Ray and Amazon QuickSight integration makes CloudWatch a centralized monitoring tool.

LogicMonitor is used for application insights monitoring, collecting, analyzing, and visualizing data from application infrastructure, and identifying errors. It boasts features including real-time alerting, log ingestion, and visualization dashboards. LogicMonitor offers microservices monitoring and more features in terms of alerting and support compared to CloudWatch, but it is costlier.

CloudWatch's integration is very quick. Since these are all connected internally with the AWS backbone network, no significant integration is needed. I simply enable CloudWatch across AWS services. This centralized tool also offers logs query through Amazon QuickSight, creating visual alert dashboards.

Technical support is obviously good in LogicMonitor, rating it a ten. CloudWatch's support rates at eight to eight and a half.

LogicMonitor excels in performance monitoring, tracking performance, bolstering security, and real-time alerting. However, LogicMonitor can struggle with high ingestion costs, data retention limitations, delayed alerts, and missing critical security events.

There are several areas for LogicMonitor to improve. Overly sensitive real-time monitoring leads to too many alerts, which could be managed via AI to reduce false positives. Cost optimization by offering discounts to enterprises could help manage pricing concerns. LogicMonitor should become more centralized to handle heterogeneous environments, as plugins sometimes do not work across platforms like F5 firewall. Complexity and steep documentation also need simplification.

LogicMonitor might struggle with delayed detection, as alerts may not be immediate under high infrastructure load. Other weaknesses include ingestion costs, data retention limitations, missing critical security events, real-time analysis gaps, and delayed alerts.

I have been working with this solution for more than seven years.

Technical support is obviously good in LogicMonitor.

I have experience with AWS, DataDog, and CloudWatch. LogicMonitor offers logs monitoring capabilities. Integration-wise, LogicMonitor also has an agent that can be installed on a particular service, and all data gets populated on LogicMonitor. I can see all the documents and everything. I can also integrate with ServiceNow and other platforms. The choice depends on how the customer is using their infrastructure to monitor.

The main consideration is cost optimization. Some customers want to optimize their cost for their infrastructure, so I would recommend CloudWatch. For other customers who are open to spending additional funds, I would recommend LogicMonitor or DataDog.

LogicMonitor provides application dynamic monitoring and application insights monitoring. It collects, analyzes, and visualizes data from application infrastructure and identifies errors. I can track performance and bolster security with microservices monitoring using LogicMonitor.

LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support. However, cost is the only matter of concern. LogicMonitor has more features compared to CloudWatch.

I find a few weaknesses at the moment. Alert fatigue sometimes occurs when there is a peak load on the AWS infrastructure, and LogicMonitor takes some time to alert. High ingestion cost is another concern. Data retention limitations present challenges because sometimes I need to check alerts from six months back, but the data retention is only one week, maximum ten days, or one month. Missing critical security events is an issue where some non-critical logs get flagged as false positives. Real-time analysis is required but sometimes only works in a few services and not in all services. Some security breaches cannot be identified through LogicMonitor because those logs are not captured when something happens to a particular service. For example, if an application has vulnerabilities, the application acts like a legitimate service, but I do not know that. LogicMonitor hardly identifies these things. Even when I collect the logs, I cannot exactly know if the log is the faulty one. I think most service vendors are trying to implement AI models to identify this, but it takes some time to get this done. I think LogicMonitor is also trying to do this.

Delayed detection is a significant issue. Because of high load on the infrastructure, sometimes I will not find the alert immediately. It takes five to ten minutes, and after the impact happens, I get notified five to ten minutes later. This delayed detection is the main issue.

Real-time monitoring is required, and that means overly sensitive alerts with too many false positives. If LogicMonitor can use AI or other methods, they can remove those duplicates and maintain the actual alerts. They can identify false positives prior and prevent them by nullifying those things. Cost is another area where LogicMonitor can provide discounts to enterprise companies using most of their infrastructure to reduce their license cost. Complexity should be addressed because if a customer has multiple heterogeneous environments, LogicMonitor should be centralized to get all the data and do the log monitoring. Sometimes some plugins and agents do not work on few services. For example, on F5 firewalls and on-premises firewall physical servers where I want to get some logs, those do not get logged on LogicMonitor. A lack of context and understanding of the tool is also an issue. The documentation should be more clear and simple in simple language. When I first see the documentation, it is pages upon pages, and it is very difficult to understand everything until I gain some control of that tool. The documentation should be reduced so people can easily use that tool. Instead of going very complex, straightforward guidance should be required. My overall rating for this product is nine out of ten.

My main use case for LogicMonitor includes alert monitoring, infrastructure provisioning, website monitoring, and networking monitoring.

A specific example of how I use LogicMonitor for alert monitoring is that we have multiple dashboards, one of them being the NSI Level One Ready for Business daily checks. This dashboard is always opened on our monitors and we look for critical alerts. The most recent one was one hour ago when we had one site going down and we managed to catch that and see that it was a change issue. We managed to fix it within a few minutes instead of having colleagues from the site opening a ticket and writing to us.

We also use LogicMonitor for our WAN capacity reports, and we can find a lot of information on the usage. It is really easy to use its API to automate everything regarding this.

LogicMonitor has positively impacted our organization because it is extremely easy for us to monitor websites, devices, and APs all in a single place. We do not have to have multiple tools and get lost through them. Everything is in one place and it is easy to use and find.

LogicMonitor has improved our response time by a lot. Before LogicMonitor, colleagues would reach out to us, but after we started using LogicMonitor, all the critical alerts generate almost in an instant when the threshold is met. It is easy for us to have all the information about the device there and we can start troubleshooting as soon as possible. LogicMonitor has improved our response time by 70-80%.

The best features of LogicMonitor are really good API documentation and really good logic when it comes to alerts. Even the default logic is pretty good for us.

The API documentation and alert logic make my job easier because I like to pull data into our own Agentic workflow, and we use that data to make sure that we are proactive and we can overcome certain situations of bandwidth utilization. We can upgrade sites before they hit the threshold and things like that.

I really appreciate how easy it is to provision a site in LogicMonitor.

LogicMonitor's AI capabilities fulfill everything that we are looking for. The AI capabilities are pretty good, although they are pretty new, so I have not had the opportunity to fully test them.

LogicMonitor can be improved by having more AI Agentic information and more Agentic workflows in LogicMonitor.

I have been using LogicMonitor for the past three years.

I would rate LogicMonitor an eight out of ten overall.

I chose eight out of ten for LogicMonitor because I would like to see more AI and Agentic workflows in it. Other than that, I am really fond of LogicMonitor.

The advice I would give to others looking into using LogicMonitor is to go for it. It is a really great tool, and I think it is very easy to set it up and have it working in no time.

Private Cloud

Amazon Web Services (AWS)

My main use case for LogicMonitor is to monitor the computer systems and ensure that the digital services stay healthy for our clients who are running Meta ads for our services.

One specific example of how I use LogicMonitor for monitoring those digital services is when one of our clients recently launched a major campaign due to the Diwali festival, and user traffic increased significantly in a very short time, causing the landing website to start crashing. The computer monitoring system sent us an automatic warning, and we figured out the real-time performance and identified the issue.

Compared to past weeks, we have been finding repetitive patterns of how to handle heavy workloads because the festival seasons are coming.

LogicMonitor has positively impacted our organization by providing server health and performance insight, so we don't have to guess it. It helped our team communicate faster because we all see the live numbers.

The improvement from not having to guess server health means we can directly jump into the real fix without wasting time configuring the issues. The client has also experienced less downtime because we are spotting warning issues and addressing them when the system crashes or slows down.

The best features LogicMonitor offers in my opinion are centralized dashboards that let us see the computer servers and network health, the automated warnings, the instant alerts, and the past performance data.

Out of the features I mentioned, I find myself relying on the automated warning the most because I have to check every morning if there is any issue overnight since our ads are running in India and outside of India as well. We have to ensure that the performance landing page never crashes.

We haven't utilized the dynamic service insights feature for real-time visibility and mainly rely on the standard dashboard and automated warning to keep track.

LogicMonitor can be improved because the initial onboarding of a new system is a bit tough, and the automated scan can lack background details.

I found the user interface standard and good with solid basics. While I can see video tutorials on YouTube, we haven't contacted support during the five months of usage because they gave us the setup of the account and we just had to configure the things.

I have been using LogicMonitor for four to five months.

LogicMonitor is pretty stable in my experience. I haven't seen crashing, and it has been reliable for us.

LogicMonitor's scalability is effective. We have onboarded around seven of our premium customers on it, and we haven't seen any issues so far.

Before LogicMonitor, we were doing things manually and did not use a different solution.

The initial setup and configuration take too much time for a new dashboard onboarding, which is something I wish could improve.

LogicMonitor is deployed on-premises only because it has been deployed by the company itself.

We have seen a return on investment with LogicMonitor. When I joined the company, things were done manually, and now it is straightforward, indicating a healthy server.

On a scale of one to ten, I would rate LogicMonitor an eight out of ten.

I chose eight out of ten because it is a strong and helpful tool, but the main concern is that the server health and the automatic warnings can sometimes arrive later.

Regarding LogicMonitor's AI capabilities, I think of it as an AI tool. However, we haven't used the AI and are still relying on our side of AIs that we are using, such as ChatGPT and Claude.

We have used it in the on-premises environment and haven't used hybrid infrastructure, so I cannot comment on challenges related to gaining complete visibility across that.

I would advise others looking into using LogicMonitor to go for the product, as we haven't seen any downtime or issues.

On-premises

My main use case for LogicMonitor is alerts, which I rely on to review if systems are up or down and if any services have stopped that could be business impacting. We are a manufacturing company, so we have a very heavy reliance on our production servers. Dashboards are excellent and we rely on them a lot.

A specific example of how I use LogicMonitor for alerts is when one of our servers had a full disk. I would log in in the morning and open up my alerts page or we would have dashboards on the screens around the office. Either way, I would look at it and action that straight away, increasing the space or reaching out to that application or server owner, saying, 'Look, if you could decrease the space, great. If not, I would increase that.' This would be actioned by myself or my colleague.

I have found that we are very reactive with LogicMonitor, but I think we could probably benefit from being more proactive with it.

LogicMonitor has impacted my organization positively due to alerting. I have set up phone call and SMS alerts to my mobile phone. If there is an outage in the factory, no matter what time of day it is, I get a phone call on my phone. Other monitoring tools I used in the past do not actually provide the phone call functionality, so it is beneficial. Obviously, it is not great for me since it wakes me up, but it allows me to react quickly and help the business. Since we have had LogicMonitor, the alerting has really helped us. We used to use SolarWinds before and there was not as much noise from alerts, and people are taking alerts generated via LogicMonitor more seriously now.

I have noticed that downtime has definitely decreased with LogicMonitor. Just from that use case that I gave, we have more efficient alerting which results in us infrastructure engineers being able to react faster 24/7 and promptly resolve issues for the business.

In my opinion, the best features LogicMonitor offers are visibility, as it provides great visibility of all my resources. I also appreciate the support; LogicMonitor support is great.

When I mention visibility, the dashboard is the most helpful for me. Regarding support, if you use the live chat, the agents are really friendly and always know their material, so you get great service. In terms of the product, the dashboard itself allows you to create really cool widgets and some of the out-of-the-box offerings are pretty good, so there are lots of positives.

In my experience, I think LogicMonitor could be improved. I believe that at LogicMonitor events, there should be more tech time. It seems all focused on certification or what is new and the latest offerings, but I think it would be great to have some tech time where you could meet face-to-face with a LogicMonitor agent and they could review your environment and suggest benefits. It is almost like a health check. A nice walk-up bar with techs would create a more personal touch to support rather than having to call or jump on a live chat.

I have been using LogicMonitor for about two years.

In my experience, LogicMonitor's scalability could be improved. I have used a different monitoring solution in the past that had an automated function to start a service again if it stopped. Something like that would be great for LogicMonitor, where it could work for you and with you upon your instruction, but I do not currently see that feature.

I find the customer support of LogicMonitor is brilliant. I mentioned this earlier in our conversation. Customer support is outstanding, and I have no complaints. Every time I have jumped on a call, they have managed to resolve my issues, and they are pretty good on live chat as well, showing a clear understanding of the issues with a solid knowledge base.

I used a different solution before LogicMonitor, specifically SolarWinds, which is another big name in the business. The reason for switching was a lack of functionality. With LogicMonitor, you get a lot of options and more of a futuristic UI. Many alerts and other features in SolarWinds were almost abandoned and poorly neglected because they were managed by a different department. We wanted to go with a fresh product, so with only myself and my colleagues' input, we are doing pretty well with the alerts. I think we have five critical alerts outstanding out of over 600 resources. We just wanted something fresh to keep everything green, as they say, with no red.

I rate LogicMonitor a 10 out of 10.

I choose a 10 for my rating because there are no negatives. All I gave in my feedback was that some tech time at your events would be great. Other than that, I have not really got a bad thing to say. LogicMonitor is a great tool with a great UI that is user-friendly, has enough material to learn what you need to do, and is pretty simple to use.

Regarding LogicMonitor's AI capabilities, I cannot comment on its governance and security because we have not actually upgraded to that plan.

We have not used LogicMonitor's AI features, so I cannot provide any thoughts on its accuracy and reliability of output.

The advice I would give to others looking into using LogicMonitor is to start with the new UI. When we started two years ago, there was an old UI and a new UI, and luckily for us, we started on the new UI. We appreciate it and are familiar with it. Other advice is that LogicMonitor has great alerting, is reliable, and you really care about your customers. We have a good relationship with our account managers.

My main use case for LogicMonitor is managing network and switches. We have set up our office in various sites around the world, and LogicMonitor helps us in monitoring the switches, the overall network, the ISP's state, and everything about the network. It's all managed by LogicMonitor.

If there are any alerts or if any switch goes down, we get an instant email through ServiceNow to our mailbox.

The best features that LogicMonitor offers include integration with various platforms and the UI. LogicMonitor has positively impacted my organization by reducing network monitoring time and the overall time spent on reviewing the switches and network-related concerns.

Now we simply rely on the alerts, the emails, the priority of those alerts, the warning, and the severity; everything is managed by LogicMonitor. We don't have to work extensively on it anymore. We rely on the tool and the triggers.

I think if LogicMonitor offered a desktop app or something that can be installed on the machine, it would be really helpful.

Additionally, it times out after every couple of minutes, perhaps 20 or 30 minutes. If there were a way that it could continue running, whether as an app or as a site in the background, that would be helpful.

I have been using LogicMonitor for 2.5 years.

LogicMonitor is stable.

LogicMonitor's scalability is good; it is something that we can work on, and as I already mentioned, we are still working on it.

My experience with pricing, setup cost, and licensing was all feasible; it wasn't that expensive.

My advice to others looking into using LogicMonitor is to go for it and use it; it's worth trying.

Dynamic Service Insights doesn't affect us in any way; it's just that the overall concept of managing the networks is working fine for us. LogicMonitor doesn't help in resolving MTTR; it only manages the network and gives alerts if there is an issue. Once there is an issue, if it's something that can be resolved onsite, we have to send engineers onsite. The ticket resolution is not managed by LogicMonitor. I'm not sure exactly how the cost was saved, but it has helped us in terms of viewing the network from one single tool. We don't have to keep switching from one to another. We have given access to more than 10 or 15 employees already, with two from network and the rest from the other teams.

My overall rating for LogicMonitor is 9 out of 10.

Private Cloud

Microsoft Azure

I am using LogicMonitor for accessing devices in real time to monitor any critical or major alerts. We use LogicMonitor to map alerts to ServiceNow to generate tickets on a real-time basis. This is one of the excellent applications and portals I have used in my career, and it is a strong product for any enterprise, small, or medium-sized company that needs to handle or monitor large-scale devices, cloud devices, or servers.

Regarding the use of Admin AI for diagnosing root causes and orchestrating remediation, I have not yet implemented this. My cloud AI team or ECI AI team may be working on this capability. I need to investigate this further in the future. Currently, I use LogicMonitor for real-time monitoring to check for any critical outages occurring in networks or system servers. I can also fetch reports from LogicMonitor to obtain all the data for a particular client as needed for my company's perspective during data preparation. I refresh reports from LogicMonitor regularly, and I need to check further with my cloud team regarding the AI functionality. As of now, I am not using that option.

I use LogicMonitor for accessing devices in real time and monitoring any critical or major alerts. We map alerts to ServiceNow to generate tickets on a real-time basis. This is one of the excellent applications and portals I have used in my career. It is a strong product for any enterprise, small, or medium-sized company that needs to handle or monitor large-scale devices, cloud devices, or servers.

I can also use the old UI, which is still available to me where the setup is almost the same, although the overall interface is a bit older. Apart from that, there are no issues. We can set up the time zone in the application according to standards, such as EST or any other zone we require.

Based on my experience with LogicMonitor, I dislike a particular design aspect, and I am uncertain whether this design was created by my company or if it is a global configuration. For any particular client, we use network and system or server devices, and these are mapped in the resource or resource mapping group. For those resources of a particular client, we can access all the details, including all thresholds and real-time monitoring. For example, for a client using five network devices and five servers, they may have some ISP circuits or WAN circuits being used by that same client. Whether there is a single circuit or dual circuit depends on the environment or the client setup. We have to search in a different option within the same resource tab to access only those circuit details for all clients. It would be beneficial if there were an option available to add ISP circuit details for a particular client within the same platform, as that would save time accessing it.

When we open a particular monitoring tab in LogicMonitor, we have to open a duplicate LogicMonitor window in the same browser. Based on my understanding, this may be by design, but if it were possible to add those details within the same client environment or client setup in the same tab, that would reduce the time required to access or troubleshoot during any outage. Additionally, I found that LogicMonitor needs some improvement in threshold monitoring. For example, when we monitor a particular device with a temperature issue or high-temperature problem, sometimes I observe that in real time when I log into the device, the temperature shows something that does not accurately match what is displayed on the LogicMonitor platform. That needs fine-tuning.

I have been working with LogicMonitor for the last eleven months.

I have not experienced significant lagging, crashing, or downtime with LogicMonitor during the last eleven months. When I first started using this application, I used it for approximately one to one and a half minutes, and during that time LogicMonitor became unresponsive after refreshing the window. However, it returned to normal operation after that. That is my only experience with such an issue.

I have already mentioned that LogicMonitor is very scalable and useful for large enterprise networks and large enterprise companies. I can confirm that it can be very helpful for all companies.

I have not had to contact technical support yet. I completed a certification through my organization as part of the LM Getting Started Batch 2025 LogicMonitor Basic Training. I learned a lot from that training, including basic modules about LogicMonitor, which was helpful for gaining knowledge. I did contact my company's technical support or Enterprise Tools team when I found some issues such as multiple alerts flooding from LogicMonitor or if an alert had already been removed from the system but still appeared in LogicMonitor, and those issues were resolved. I have not yet contacted any LogicMonitor technical team directly.

Regarding alternatives to LogicMonitor, I can say that in my previous organization at Unify CX, I used PRTG as a monitoring tool, the PRTG Network Monitor. I have also used SolarWinds as a real-time monitoring tool. However, I can confirm that LogicMonitor is one of the best platforms for any organization to use for network, cloud, or system monitoring. It is user-friendly and the overall structural setup is very strong.

Regarding the initial deployment of LogicMonitor, I found it not very difficult, but the setup was quite new to me because I was using it for the first time. Within one or two days, I understood most of it, and as I continued using it more, I gained knowledge about everything, including the setup, access, how to check alerts, alert tuning in this setup, how to check if any alert is in SDT, checking graphs, and all the configurations we have in this setup. It is truly impressive.

LogicMonitor does not require any maintenance on my end. We do not involve ourselves in the maintenance, but there is a team in my organization called the Enterprise Tools Team (ETT). They handle the maintenance portion of the application. We do not have much involvement in it currently.

Regarding pricing, I do not know much about it. I do not have much knowledge about the pricing or how much it costs to a particular organization because I work as a NOC engineer, so my focus is to monitor the network and system components from LogicMonitor on a twenty-four-seven basis. I wish to know more if you want to share that information with me, but I do not have that knowledge currently.

Currently, there is a new UI option that is an advanced UI version for monitoring the application.

Regarding dynamic service insights for real-time visibility, I apologize, but I do not understand what you mean by dynamic service. Could you please elaborate a bit further? As of now, I am not using that service, so I cannot tell you elaborately about this topic. On a scale from one to ten, I would rate LogicMonitor as a nine overall because I cannot provide a ten, as there is always a chance to improve. My overall review rating for LogicMonitor is nine out of ten.

LogicMonitor is used to monitor all security network appliances and system appliances, including servers, Linux systems, networks, appliances, firewalls, routers, and switches. It also monitors cloud infrastructure, including VNet, cloud services, and cloud connectivity solutions such as Azure ExpressRoute, and extends down into individual configurations such as BGP sessions and IPsec tunnels. This monitoring capability serves multiple sectors through a managed service provider model, providing services to finance, real estate, and other industries.

The LogicMonitor alert UI is valuable because it correlates alerts, preventing unnecessary panic by allowing me to review the alert dashboard instead of logging into each individual device or relying on unreliable monitoring tools. LogicMonitor is very reliable compared to many other monitoring tools I have used. Each individual BGP session, IPsec tunnel, and interface is captured accurately, and the logs are highly reliable.

The impact of LogicMonitor on management of service health and business risks is significant. In my previous company, after implementing LogicMonitor, most issues were resolved within one hour without requiring senior engineer intervention, as junior engineers could resolve issues by reviewing the alert information and understanding what occurred.

The remediation functionality could be improved. Given the power of the tool, implementing a one-click option to change configurations via SSH or API access to appliances would be beneficial. The remediation component could also include automation capabilities.

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

Before LogicMonitor, I used a different tool for log search, though I cannot recall the name. The main differences between previous tools I used, such as SolarWinds, and LogicMonitor are that previous tools do not display everything in one dashboard. They typically show a number of devices and alerts, and to see alert details, I had to click through to see more information. LogicMonitor displays everything in one comprehensive dashboard, which prevents me from forgetting what I see when navigating away from a link.

I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free resources but not as powerful as LogicMonitor. For small businesses that want to utilize LogicMonitor and are just starting out with limited customers, a pricing model targeted to this segment would be beneficial, perhaps at three or two dollars per device per month.

LogicMonitor has advanced AI and AIOps capabilities for diagnosing root causes that I have not yet utilized. LogicMonitor has positively impacted my team's MTTR for incidents. When one switch goes down, multiple alerts trigger not only from that switch but also from peer switches. Suddenly, a hundred alerts may appear, but the issue can be narrowed down by identifying the down device instead of processing all the noise. One switch showing as red means I can ignore the other alerts coming from other switches, which is very helpful as the entire team can see this information in one dashboard. I rate this product a ten out of ten.

Public Cloud

Microsoft Azure

My main use case for LogicMonitor is network monitoring. Whenever we see an alert in the network, we go to LogicMonitor, access the specific host, and identify the parameter or reason causing the alert. LogicMonitor uses SNMP to pull data from devices, and as a network engineer, SNMP is a valuable tool. There are other tools available that are better than SNMP and can also be used in LogicMonitor.

LogicMonitor is integrated with ServiceNow. Whenever a device has a certain problem, we define what the problem is. For example, if a particular device has multiple interfaces and one critical interface is down, LogicMonitor generates an alert through SNMP polling from the devices and sends that alert to ServiceNow through the CI/CD pipeline, which is integrated with ServiceNow. ServiceNow generates an incident, sends it to the specific support queue, and support team members are assigned to the specific ticket to help resolve it.

Additionally, LogicMonitor's dashboard is essential for monitoring, allowing us to see high bandwidth utilization or instances where someone in the network is using bandwidth improperly, such as watching a Netflix video and impacting the network. We can see these metrics on the dashboard in LogicMonitor.

Integrating LogicMonitor with ServiceNow has made things much faster. Whenever there is an alert, it automatically triggers an incident to the queue, and we have a response SLA time for ServiceNow, which requires engineers to assign incidents within 15 minutes according to the current rule set. LogicMonitor reduces business impact because it works as a monitoring and alerting tool, while ServiceNow is a support tool. When integrated, they work exceptionally well and help keep the business running smoothly.

LogicMonitor offers several best features, which include the dashboard, alerting, log analysis, and some AI features that create automatic network diagrams. These are the main key features that LogicMonitor has.

I rely the most on alerting as the best feature because it creates tickets in ServiceNow to resolve problems. The dashboard is my second choice because it provides an overview of what is going on in my network.

Currently, I do not see any improvements needed for LogicMonitor. Improvements depend on how the user engages with the tool, and this completely depends on the person using LogicMonitor.

I have been using LogicMonitor since January 2024, so it has been more than two years.

LogicMonitor is absolutely stable and has no downtime.

LogicMonitor's scalability is great.

I am confident that LogicMonitor's customer support is good because our client team has never been dissatisfied with customer support whenever needed for any issues or version upgrades.

I work on multiple projects where previous ones used SolarWinds, while others used ThousandEyes. The current project is using LogicMonitor. It is not up to me; it depends on what the client wants and what tools they choose to use in the network.

LogicMonitor has positively impacted my organization by making our business run very smoothly. Whenever there is a problem, it triggers an alert that goes into ServiceNow, which then generates an incident. This entire process happens within just two to five seconds, which allows the support team to jump into the problem and be ready to resolve the issue.

I do not have positive answers regarding the governance and security of LogicMonitor's AI capabilities. We do not utilize AI very much in LogicMonitor, so I may not be able to answer questions comprehensively because everything we create operates automatically. Therefore, we are not dependent on LogicMonitor's AI at this time.

We purchased LogicMonitor through the AWS Marketplace.

LogicMonitor is absolutely stable and has no downtime.

Everybody should use LogicMonitor based on the reasons I have already provided. The overall rating I would give for this product is 9 out of 10.

Private Cloud

Amazon Web Services (AWS)

My main use case for LogicMonitor is real-time monitoring, alerting, performance tracking, and infrastructure visibility.

In LogicMonitor, I can create a dashboard to monitor proactively, manage alerting, capacity planning, and operational visibility. Our network team monitors bandwidth utilization, device health, and server availability to prevent outages, making this one of the best use cases with LogicMonitor.

LogicMonitor is good for dashboards and reporting, allowing us to easily track the real-time performance of servers and network devices, as well as create custom reports for operational visibility, representing the main cases we are working with.

Day-to-day, I rely on real-time monitoring, which includes monitoring network devices such as routers and servers for CPU utilization and server memory use. Alerts are triggered when server disk usage reaches 90%, which is beneficial for monitoring alert management.

In addition to the aforementioned features, LogicMonitor provides log and event correlation, helping to correlate logs, alerts, and metrics for troubleshooting. It aids in investigating application slowdowns by checking logs and CPU spikes together, supporting day-to-day operations through real-time monitoring, alerting, dashboard, reporting, auto-discovery, topology mapping, and proactive infrastructure management.

In our organization, LogicMonitor is deployed to provide centralized monitoring of infrastructure, network devices, server applications, and cloud resources, allowing us to monitor routers, switches, and servers from a single platform while enabling proactive alerting and operational visibility across hybrid IT environments.

The best features of LogicMonitor include alerting and escalation, triggered when CPU utilization exceeds 90%. Additionally, topology mapping provides visual dependency mapping of infrastructure, mapping relationships between servers, network devices, and applications, leading to faster issue detection and troubleshooting, along with centralized operational monitoring.

LogicMonitor has positively impacted our organization by allowing early detection of memory spikes on production servers, enabling the team to resolve issues before they affect service, and making day-to-day work much less stressful for us.

LogicMonitor helps improve outcomes, including improved infrastructure uptime, faster issue resolution, and better visibility across servers, network devices, and cloud resources. In terms of metrics, I can point to uptime percentage, availability of servers and network devices, and faster incident resolution times, as well as a reduction in the number of monitoring-related incidents.

In terms of improvement, I suggest that the pricing could be on the higher side for smaller organizations, advanced customization has a learning curve, and alert tuning may require initial optimization to avoid too many alerts.

Areas for improvement include optimizing alert noise, enhancing dashboard customization, increasing pricing flexibility, and reducing the learning curve for new users.

I have been using LogicMonitor for 24 months.

LogicMonitor is a stable and reliable monitoring platform that supports continuous monitoring of infrastructure, networks, and clouds with strong uptime and consistent performance. Specifically, my team uses LogicMonitor daily to monitor servers, routers, network devices, applications, and cloud resources with minimal operational disruptions.

The customer support is very good.

Previously, we used SolarWinds, and the reason for switching was that we could not access real-time dashboards or monitor servers, routers, switches, and CPU utilization effectively, which is why LogicMonitor has proven to be a much better platform for our needs.

The use of LogicMonitor significantly helps save time and reduce downtime in our organization.

Our pricing and setup costs are organization-specific and based on company deployment across network areas. The pricing model is subscription-based.

Before choosing LogicMonitor, we evaluated SolarWinds.

I advise others looking into LogicMonitor that it is a very good platform.

LogicMonitor is a strong choice for any organization seeking proactive monitoring, centralized observability, and improved operational visibility across the IT environment.

I would rate this review 9 out of 10.

Hybrid Cloud

Other