We installed LogicMonitor as a SaaS-based solution, and we have an agentless approach. We are monitoring the overall interface and not just the network devices. I am looking after the network devices only.
Assistant Manager at a construction company with 5,001-10,000 employees
A feature-packed solution with excellent stability and a notification system
Pros and Cons
- "LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
- "LogicMonitor has good features, but the ease of use is a little bit confusing. Additionally, we are looking for workflow automation, which is a little bit tricky for LogicMonitor."
What is our primary use case?
What is most valuable?
LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure. They also have a great notification system. If something goes wrong, you'll be automatically notified. LogicMonitor also integrates with ServiceNow, so you can easily get alerts in those systems.
Another thing I like about LogicMonitor is their dependency metrics. This means that if one device goes down, you won't get alerts for other devices that depend on it. This helps you to quickly identify and resolve problems.
Overall, I think LogicMonitor has a lot of great features. However, I do have some concerns about the deployment process. It's not as straightforward as it could be. Additionally, some of the workflow automation features require scripting knowledge, which can be a barrier for some users.
What needs improvement?
LogicMonitor has good features, but the ease of use is a little bit confusing. Additionally, we are looking for workflow automation, which is a little bit tricky for LogicMonitor. But we are still exploring more and do not have detailed training in LogicMonitor.
Moreover, the deployment process needs improvement. The thing is the deployment or whatever the standard deployment should be implemented here. That is not fine-tuning.
In my personal opinion, for workflow automation and other stuff, we have Python or scripting knowledge, and that part is very tricky. Whenever we try to call the service or the LogicMonitor team, and we open a ticket, it is chargeable.
In future releases, we would like to see a configuration backup manager. A feature that automatically backups the device configuration will help us. So, instead of going with another third-party tool, this will be good.
For how long have I used the solution?
We have been using the product for two years.
Buyer's Guide
LogicMonitor
January 2026
Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
880,435 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability is very good. We have a SaaS-based solution and a cloud-based solution. We never experienced any kind of downtime from them. So, that part is very good.
What do I think about the scalability of the solution?
It will be good because whatever knowledge I have with LogicMonitor is limited. I have not been able to fully explore LogicMonitor because of the scripting and other overflow automation concepts. Even courses are not available on working data. So, basically, working on the courses is available for free. I really didn't deep-dive into LogicMonitor.
In our organization, the regional office, we have two major regional offices in the USA, Kansas City, and Mumbai. So, Mumbai's count is 2,000, and Kansas City's is 4,000.
Almost all use LogicMonitor, which would include branch offices as well. So, more than 100 branch offices. We are monitoring one key code universal, and the rest of the branches have separate networks and accesses.
I would rate the scalability of this solution an eight out of ten.
How are customer service and support?
The technical support is very good. But the only thing is that if you have some issues with the particular script writing and some customized reports, we have to open the case with them, and that is chargeable. That is what the subscription part is, and what the agreement between our organization and LogicMonitor is, I don’t know. Our dedicated SME handles it in the USA office.
So, if we want to open a case with them, we go to our SME, and they will try to resolve the issue. If not, then it will be chargeable. Last time, we raised some queries, and my management told me that if the query is not solved, open a case, and it will be chargeable.
Which solution did I use previously and why did I switch?
I have been working with SolarWinds for more than four years. So, I can talk about SolarWinds. SolarWinds is good for network monitoring. It has reporting of topology diagrams and all this stuff that we can get over there. Also, a bandwidth analyzer is available, which is a very handy tool. There is also configuration management, which is like an add-on basis. So that is good. But with the recent incident with SolarWinds, it is no more secure. If you wanted an on-premises solution, then probably go with ManageEngine or SolarWinds. But when looking for cloud-based, we thought LogicMonitor will be good for us. We only have to check and gain some knowledge on whatever they provide, the knowledge portal or training. So, that is part training for us.
How was the initial setup?
The team in the USA or the partner who implemented LogicMonitor earlier is not in the proper shape of architecture or deployment. So, it's got some issues with the network device group and servers. So, all are messed up. We decided to fine-tune the hardening of this LogicMonitor.
Personally, the way we implement it here. I feel it is not easy to use.
The solution is deployed on the cloud.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing for LogicMonitor a six or seven out of ten, where one being cheap and ten being expensive.
What other advice do I have?
The thing is that some features are there, but we have, like, incompetency to add up that feature. So, the product is feature-packed. But some of the features we have to explore still.
Overall, I would rate LogicMonitor an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Network & Telco Lead at a energy/utilities company with 501-1,000 employees
An easy-to-use solution for network monitoring
Pros and Cons
- "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."
- "LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations."
What is our primary use case?
We use the solution for network monitoring.
What is most valuable?
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 most useful feature we've found in LogicMonitor is its ability to deploy templates automatically. It's quite smart in this regard. When we add a device, it detects the type of device and deploys the appropriate template for it.
The tool's alerting system has been pretty good for us. We receive SMS alerts if we're not in front of our screens, which has improved our response time to potential issues. The escalation chains feature has been particularly useful in this regard. Overall, it's easy to use and simplifies our alerting process.
The tool is highly integratable.
What needs improvement?
LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations.
For how long have I used the solution?
I have been using the product for more than two years.
What do I think about the stability of the solution?
I rate the solution's stability a nine out of ten.
What do I think about the scalability of the solution?
I rate the product's scalability a ten out of ten.
How are customer service and support?
The response time for support needs to be better. They're pretty fast in responding, but there are many areas they won't cover; it often falls out of scope. While they're good at getting back to us, they're not owning the issue and assisting.
How would you rate customer service and support?
Neutral
How was the initial setup?
The tool's deployment is very simple.
What's my experience with pricing, setup cost, and licensing?
The solution is not expensive.
What other advice do I have?
We use Datadog for cloud monitoring. I rate the overall product an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
LogicMonitor
January 2026
Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
880,435 professionals have used our research since 2012.
Systems Engineer at a tech services company with 10,001+ employees
They have an active community of users who are willing to share their experiences and how they have extended the solution to do unusual things.
Pros and Cons
- "It is easy to set up and monitor an entire facility. This is crucial because we have around 80 facilities that require monitoring. LifePoint is a hub-and-spoke environment, so it is essential to understand all of the WAN interfaces."
- "LogicMonitor can easily easy to pull data from one item at a time. I have yet to find a good way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity."
What is our primary use case?
We are a network of hospitals using the solution to monitor our network devices and all of the interfaces connected to them. It's predominantly instances of applications running on Windows Server. We use the Windows WMI for Windows Server stats.
The IT directors at our hospitals use it, so we have around 90 end-users Some of them have extended the monitoring capabilities to printers to stay on top of toner supplies. In the past, we've had admin people freaking out because the printer is out of toner, and we have any in the closet. Nobody was watching that, and some people would be hoarding supplies.
How has it helped my organization?
LogicMonitor replaced SolarWinds after a security breach. We work with a network service provider that owns all of the network devices, and we had some issues with total inventory control. We're a monitoring site, so we're not necessarily on the operational side and we're out of the loop sometimes when things are changing.
What is most valuable?
It is easy to set up and monitor an entire facility. This is crucial because we have around 80 facilities that require monitoring. LifePoint is a hub-and-spoke environment, so it is essential to understand all of the WAN interfaces.
What needs improvement?
I'm a learn-by-example person, so it would be nice to have a cookbook for enterprise management. They have a rich API process, but there aren't many examples of how to do enterprise-style work. It is peculiar about how to do it for one device, but not necessarily thousands.
LogicMonitor can effortlessly pull data from one item at a time. I have yet to find an excellent way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity.
For how long have I used the solution?
I have been using LogicMonitor for 18 months.
What do I think about the stability of the solution?
LogicMonitor has been stable so far. There has been a learning curve, where we had to allocate more resources to a collector doing work. At the same time, it has been relatively easy to stand up more of them.
What do I think about the scalability of the solution?
Scaling is a matter of adding more collectors to the environment. If you've discovered too many devices, you have to rebalance the collectors. However, if you add more collectors into a sphere, you don't need to worry about doing the load balancing by yourself. You let the mechanics do it for you.
How are customer service and support?
I rate LogicMonitor support nine out of 10. They have a button on all of the webpages that says "Contact Support," so you can do that online or submit a ticket. Both have worked well.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I was a big user of SolarWinds before. It was easy to pull data out of SolarWinds and then put it into other tools for big-picture analysis across the entire enterprise as opposed to an individual device.
How was the initial setup?
Setting up LogicMonitor isn't very complex. We quickly learned that we could do some collector load balancing. As we're adding devices to a series of collectors, it can do its own load balancing to ensure you don't have too much on one server doing S&P polling.
What about the implementation team?
We did most of the work ourselves.
What was our ROI?
We've certainly seen a return. One of the features we use extensively is Netflow, which helps us better understand what is consumed in the WAN environment. For example, we can determine that the DICOM processing is unnecessarily using up the WAN. It can go over a Meraki network, which is an encrypted process going over the general internet. We have highly secure Opt-E-WAN environments that most traffic goes over, but we also use the public internet to send other encrypted data.
What's my experience with pricing, setup cost, and licensing?
The license is annual, and I'm not fully aware of what it costs. We have a through-cycle that we go through, and they've been generous with us going above our limit. They're not strict on it. At the end of the year, they got us to renew. We always add some cushion for what we expect. Also, if you need custom monitoring or design work, you can pay them for consulting services.
What other advice do I have?
I rate LogicMonitor eight out of 10. It's easy to add new features to LogicMonitor. They have an active community of users who are willing to share their experiences and how they have extended the solution to do unusual things.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Technical Director - Cloud Services at a tech services company with 11-50 employees
We went from nothing to full visibility across our internal and external estates of equipment
Pros and Cons
- "We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor."
- "Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on."
What is our primary use case?
We use it to monitor the performance and health of all our internal IT systems in our data center as well as our customer equipment that we have out on customer sites. We have our own stuff in our own data center, but we also have hundreds of devices out on our customer sites where we need to monitor and manage the health and performance of them.
How has it helped my organization?
Before we were using LogicMonitor, we didn't really have visibility on a lot of things. We went from almost nothing at all, e.g., no visibility on things, no good monitoring, and not being alerted or aware of problems when they would arise, to putting in LogicMonitor across our whole estate and customers' environments now. This has meant that we have been able to centralize that function. When something goes wrong, we can react to it quickly. We can resolve it before it impacts our customers. That is massively important.
We went from nothing to pretty much full visibility across our internal and external estates of equipment, which has been massive for us in terms of being able to resolve problems faster and provide better customer service to our customers. At the end of the day, our customers pay us to be on top of their stuff. LogicMonitor helps us do what we are supposed to do for our customers. So, it is very good from our perspective.
We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor.
We monitor stuff that is on-prem and in the cloud. It is very good comprehensively for that. It is brilliant. I could probably only count a couple of times where there has been something I have needed to monitor that hasn't had a data source or something in LogicMonitor. It is only niche products where I guess it wouldn't necessarily make financial sense for them to actually develop something for this at the moment. For example, we started using a fairly new product, which we rolled out for a lot of our customers, and noticed when we first started using it that there were a limited amount of data sources in LogicMonitor for it. Over the last couple of months, that has been developed significantly. Generally, if it doesn't do something that we want it to do, there is a chance that it will do it at some point and that process is usually quite quick.
We are very happy with it from a future-proofing perspective. With the amount of updates that LogicMonitor pushes out, I have no concerns that LogicMonitor won't be able to keep up with them as the IT environment changes for our customers and ourselves going forward. It will be great for that.
What is most valuable?
There are a lot of valuable features. The product is probably one of the best-featured products in terms of its usability. It is brilliant. The in-depth graphs are really good for visualization. Remote access to devices through the LogicMonitor portal is really good from an ease-of-use perspective. Also, it is very secure.
LogicMonitor bought a company called Unomaly and integrated their log analytics into the LogicMonitor portal, which has been very good for us. Although we have a very big technical team, our internally facing IT team is quite small so having a product that is very easy to use is really important for us. We don't have loads of people who are experts in every individual product that we have. We have people that need to be skilled across a large number of products. So, the usability is very good for LogicMonitor.
We definitely use the Dashboards feature. We generally construct the dashboards ourselves, so we don't use the template ones that LogicMonitor provides by default, but we do use the Dashboards feature for our own dashboards. The templates are good examples of what you can do with dashboards, but they don't tend to meet a lot of our requirements, so we tend to do them from scratch.
We use the Dashboards feature for some of our service reviews and things for customers. We will present a dashboard to a customer when we do a review with them to show them graphs and stats on their solution.
We use dynamic thresholds within the AIOps functionality. It is good because there are a lot of times when our customers have things fluctuate. This means that we are not getting alerted for stuff all the time, e.g., every time it just goes slightly over a threshold. So, the dynamic thresholds means that we're just able to react a bit more appropriately rather than just logging issues with customers when they are not really issues.
LogicMonitor has given us visibility into issues that we didn’t even know existed. It picks up on things, like failed power supplies or disks running out of space.
What needs improvement?
Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on.
For how long have I used the solution?
I have been using it for three or four years. I used it across two different companies. So, I used it at a previous company, then I moved to my current company. We have had it in my current company for two or three years.
What do I think about the stability of the solution?
Stability is pretty much perfect. I don't think I have ever seen a problem with it. I don't think I have ever had an issue where I needed to roll anything back or tried to log in and it has not been available. It is pretty spot on there.
What do I think about the scalability of the solution?
For what we have done so far, it has scaled perfectly. We are by no means one of their larger customers, 100 to 450 devices, and we have not really had any issues with scalability from that perspective. I don't know what it is like if you are monitoring tens of thousands of devices, but scalability has been perfect for us.
We probably have about 20 or 30 internal users who log into LogicMonitor and do things within the tool. They are largely hands-on technical staff, and there are probably a couple of more management or service delivery roles in there. Service delivery is customer success, doing reviews with customers to make sure they are happy. Usually, they just use the dashboards feature for that. As a service provider, the majority of our staff are technical engineers who either support customer environments, therefore looking at alerts and things within the tool, or they are using it to access customer solutions. 90% to 95% of our technical staff are using it.
It is used across our entire business. It is probably one of the tools that we centrally revolve around. It's becoming a pretty core part of our business, and we do have plans to increase our usage.
At the moment, we have a commitment of 350 devices. We are slightly over our commitment, but I just had a quote from our account manager to increase to 450 or 500 devices. We just wanted to see a quote just to see what the volume discounts would be on each level.
It depends on the sort of customer that we win as to how many devices that we might need. For one customer, we might end up needing five devices, but for another, we might need 50. At the moment, we are looking at ramping up to 450 to 500, but that scales every time we win a customer. Over time, I suspect it will keep going up. Hopefully, it doesn't go down. If it goes down, we are losing customers.
How are customer service and technical support?
The technical support is brilliant. You get different types of tech support people at different companies, and LogicMonitor got it right in terms of the type of people they have and the way they operate. They have good channels for how to communicate with their support staff. Every time that I have dealt with someone from support, they have been really helpful. If you ask a question, you generally get quite a comprehensive answer. It will not only answer your question but also provide information on how they came to that conclusion. So, next time, if you see something similar, then you are able to resolve it yourself. I think their support staff is very knowledgeable. I have had no complaints about any ticket that I have ever logged with them.
Which solution did I use previously and why did I switch?
One of the things that I did when I came into the company was to put this solution in place because they didn't have something.
It is one of those tools where you start using it and see how nice the graphs are. I have used other monitoring tools in the past, and their graphing has just been awful. Once you see LogicMonitor and start using it, you realize how easy and nice the application is to use.
How was the initial setup?
The initial setup is straightforward. There are not too many steps. The process for doing it within the portal is very easy. It is step by step. It is very simple to do and understand. The steps are very clear and well written. It doesn't take long. The installation of the collector does not really have any settings to put in. It is just opening the installer and clicking "Next" a few times. Deploying a collector to a site takes five minutes.
The initial deployment is a gradual thing. Our IT estate has grown considerably since we started using LogicMonitor. When we put LogicMonitor in, we probably had less than 100 devices. Now, we are already looking at uplifting our commitment to 450 to 500 devices. We have gradually grown it, so we haven't necessarily had to do a complete rollout for 500 devices in one project. We have been adding 10 to 20 a month. It doesn't take long at all. It's not something that we are looking at how to streamline, because it is already so quick.
LogicMonitor reduces new customer onboarding time because the collector rollout process takes us a couple of minutes.
What about the implementation team?
We can drop a collector onsite for a customer, and we can pick up everything or select things that we need. It is very easy deployment-wise. This is really important to us. One of our current goals as an MSP is to always reduce the amount of time that it takes us to roll out solutions for customers. The quicker that we can deliver something, the quicker that we, as an MSP, can bill it. Also, the quicker we can get the cash into the business, the better for the business. Being able to drop something on a customer site and very quickly get everything added massively reduces the time it takes us to roll stuff out, which is really good for our business.
The way that we use LogicMonitor is probably a bit different to how some customers use it. We configure, install, and roll out appliances to customer sites. Installing LogicMonitor on the appliances is part of our build process. As we build the appliances in our lab, we install the LogicMonitor agent on something, then it gets shipped out to the customer's site. So, it is built into our build processes. Strategically, it is part of that. Our general strategy for rolling out is nothing special because we have done it over time.
General maintenance of the solution deployed on a customer site is pretty much nothing. Because we auto-upgrade all the collectors on customer sites, so we don't have to do anything.
This does not really have anything to do with LogicMonitor, but we spend quite a lot of time just generally maintaining alerts within the tool, because we constantly need to change the thresholds of things. We get an alert for something, then we realize, "Actually, no. We don't need to monitor that," so we have to turn it off or change when we are alerted to something. From experience, that is something you have to do with any monitoring tool. You can't expect to install it and then never have to do anything with it. It is probably where we spend most of our effort maintaining it.
What was our ROI?
If we had other tools that were more complicated, we would need to hire more staff, and then our staff costs would be higher. Therefore, the costs of the products or services that we sell to our customers would then, naturally, have to be higher. Having a wide number of features under one product, which are very easy to use, means that we don't need to have highly skilled expert people running the solution. It can be run by more junior members of staff, and we don't need to have a lot of different products and software, which would increase our overall costs, which we would then have to pass on to our customers.
LogicMonitor saves us time. If there was a problem and we didn't know where the problem was, we would potentially spend hours of time trying to locate where the problem was. Whereas, LogicMonitor helps us pinpoint where problems are. Instead of spending hours looking at something and finding out if it is an issue, we might spend minutes instead.
LogicMonitor reduces mean time to repair. If we didn't know where a problem was or weren't able to pinpoint it, we could spend hours or days, potentially, looking for the cause or source of a problem. Whereas, with LogicMonitor, we can do it in minutes or hours, depending on how complex the problem is. It probably halves, if not more, the length of time it takes us to get resolutions.
What's my experience with pricing, setup cost, and licensing?
We include costs in our pricing for the monitoring and management, but the LogicMonitor name probably doesn't have too much to do with that, but that's just because of the way we work.
We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month.
There is another feature of LogicMonitor that we would quite like to use, but it is quite expensive for our use case. It is called LM Config. We would have a very light use case for it. Therefore, I don't think that we could justify the cost of that at the moment. It is something that we would like to use, but it is just a bit expensive.
It is definitely not the cheapest tool. As we scale, as a relatively small business, there are times when I think, "Should we monitor that?" or, "Should we do that?" because of the price of the devices. However, it is so good that we are not really looking at doing anything else.
Which other solutions did I evaluate?
I had evaluated LogicMonitor at a previous company, which was a much bigger company. It was a company where it was a lot harder to make purchasing decisions. When I moved companies, I had already seen LogicMonitor and how good it was, so I didn't look at anything else. I just knew we wanted to use LogicMonitor.
If people are comparing something based on price alone, I would still say, "Do a trial. Look at some of the extra features that LogicMonitor provides," because we have found that it does more for us than just monitoring. We use it as our remote access solution to things as well, which means that we were able to get rid of another product that we were paying for in favor of LogicMonitor. So, we have consolidated two requirements into one. Even though LogicMonitor might be more expensive than another solution, we have saved overall.
What other advice do I have?
Go with LogicMonitor. Definitely, do a trial and test out the functionality.
We don't really use that many legacy tools. We are a fairly modern company in that pretty much everything we use is software as a service. So, LogicMonitor fits very nicely into that for us. We don't use products where we have to install them on servers. Everything that we use is cloud-based, and LogicMonitor is cloud-based. So, it is great from that perspective. We don't really have legacy apps, so LogicMonitor fits very nicely into that.
We actually don't use a large number of the integrations, and that's not necessarily because we don't want to. It's because we don't have some of the products that it integrates with, but we are looking to put some of them in largely because LogicMonitor has integrations with them. A good example of this is our support desk system at the moment is a certain product, but we're looking specifically to put something like ServiceNow in because LogicMonitor integrates with it. Doing that would mean that we can reduce the amount of effort on our support teams having to manually pick up things and log them, instead it could be done automatically.
I think actually having LogicMonitor and their integrations is affecting our buying decisions for other products. This ability to integrate with other products is becoming increasingly more important. As our business grows, we are looking at how to become more efficient. Also, being able to integrate LogicMonitor with other systems is becoming increasingly more important as we look to streamline our work processes.
We are looking at LogicMonitor's collectors along with the templated integrations and dashboards to enable us to automate our onboarding process and roll it out to new customers> It is on our roadmap, but a little bit further down the line. We are quite a small team and have a lot of stuff on our roadmap. This is just one of those things that we haven't gotten to yet.
It probably indirectly affects our ability to win customers. For some MSPs, if they are specifically selling their customers LogicMonitor, then it may be a bit more relevant. Our customers don't necessarily see LogicMonitor behind the scenes. It indirectly affects our ability to win customers in that we are able to be very responsive to problems and resolve things that may happen with their solutions. So, it allows us to react quickly, which affects our general ability to win customers when they ultimately get references from other customers and those customers are able to feed back that we are very responsive and able to rapidly resolve issues for them.
We don't tend to advertise to our customers that we use LogicMonitor. We don't push it as a premium product because of the way we use it. We bundle it within our service, and it is just a tool that we use internally to manage our MSP customers.
The biggest lesson that I have learned: No matter what tool you use, you still have to spend a lot of time tweaking alerts. You can't expect to put a tool like LogicMonitor in, just leaving it alone and never having to do anything. So, it is important to have a tool that is very user-friendly because you will still have to use it on a daily basis.
I would rate it a nine or 10 out of 10. It is probably one of the best tools that we have used.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Senior Architect at a tech services company with 1,001-5,000 employees
Reliable with good monitoring features and excellent support
Pros and Cons
- "The initial setup is very simple."
- "I'd like to see more automation in the tool, especially around remediation."
What is our primary use case?
It is a complete infrastructure monitoring tool. It can be used to monitor your network devices, your servers, et cetera. It is a good tool, actually.
How has it helped my organization?
We didn't have a monitoring tool previously, so we monitored via independent components. Once we implemented LogicMonitor, we gained a centralized dashboard for everything. Now, we have a complete view of infrastructure in one pane of glass.
What is most valuable?
Its monitoring features and the support on offer are pretty good.
It offers one centralized view of everything.
The initial setup is very simple.
It is stable and reliable.
The product can scale.
What needs improvement?
I'd like to see more automation in the tool, especially around remediation.
For how long have I used the solution?
We have been using it for almost one year now.
What do I think about the stability of the solution?
I've never had issues with stability. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable.
What do I think about the scalability of the solution?
The scalability is excellent. I would rate it eight out of ten in terms of being able to expand as needed.
We have an environment that covers around 2,000 servers. We may increase usage in the future, although there is no plan in place as of right now.
How are customer service and support?
Technical support is very good. They are knowledgeable and helpful.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not previously have a different solution in place.
How was the initial setup?
The initial setup is pretty straightforward. It's not overly complex. I'd rate the ease of setup eight out of ten.
The deployment took around 30 to 40 days. One or two people handled the initial deployment process.
There were prerequisites, and we made a plan on how to proceed and followed that roadmap during implementation.
What about the implementation team?
The solution provided support during implementation. After that, our team took over and handled the rest of the process.
What's my experience with pricing, setup cost, and licensing?
I'm part of the technical team and do not directly deal with pricing.
Which other solutions did I evaluate?
Other tools may have been evaluated; however, that process was handled before I arrived at the company.
What other advice do I have?
This is a SaaS-based solution. We have URL access to it.
I'd rate the solution eight out of ten overall. I'm happy with its capabilities.
I would recommend it to others as it is a very good tool.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Systems Engineer at a tech services company with 10,001+ employees
Has AI technology and helpful technical support
Pros and Cons
- "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 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."
What is our primary use case?
We're using LogicMonitor as a software as a service subscription to help us manage and monitor all of our network devices, as well as a lot of our Windows environments.
LifePoint has around eighty different hospitals that we manage, and they all have network devices and connectivity to our corporate data centers where the applications are hosted. We're constantly monitoring the state and health of their network and just making sure that if a fiber seeking backhoe cuts a fiber, that we can know about it and get the respective vendors involved as quickly as possible.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We've been using LogicMonitor for about a year and a half.
What do I think about the stability of the solution?
LogicMonitor is a very stable product. We've not had outages on their part of the environment, though we've had some outages from some of the collectors because they're running a scripting process, and like any other monitoring tool, we need to be careful that we're not overloading those devices gathering the data.
What do I think about the scalability of the solution?
LogicMonitor is a scalable product. My company has been able to deploy more devices on the collectors versus the old SolarWinds environment. LogicMonitor does a much better job for the collector environment than SolarWinds.
How are customer service and support?
Technical support for LogicMonitor was very helpful. On a scale of one to five, with one being the worst and five being the best, I would rate the support team a five.
Which solution did I use previously and why did I switch?
We were using SolarWinds for the last eight years, but when they had the data breach, we said we were not going to continue using it, and we had to find something else to use instead, so we did our evals and we decided on LogicMonitor as being one that we didn't have to support ourselves. We could count on their software as a service process and their support staff has always been very helpful with us in terms of looking at devices that are not in the standard stream such as Silver Peak. We've been able to ask for their help to better understand what we could see from the solution, including how we can monitor and keep it current.
How was the initial setup?
The initial setup for LogicMonitor was somewhat complicated for us because our network management was done by a third party. They had to add some ACL rules in the configuration of the network devices to give us access because they had it fairly locked down.
What about the implementation team?
We implemented LogicMonitor via a third party. We had eighty different hospitals and each one of those required time because the network management company we worked with did not always have everything well-documented, and that required a bit of working with them to get things identified. It wasn't a shortcoming on LogicMonitor, but more of a shortcoming of the network management company not having good documentation.
What was our ROI?
LogicMonitor helped reduce the length of an outage of a facility because of the identification of a fiber cut, so my company was able to be on top of that faster, so in that respect, the product gave us less than one year's worth of ROI.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, I would rate LogicMonitor four out of five.
Which other solutions did I evaluate?
We did look at different options before choosing LogicMonitor, but I'd rather not say which ones.
What other advice do I have?
I can't remember the version of LogicMonitor I'm currently using, but I know that my company continuously upgrades the solution as new releases come out, so it would be the most updated version.
In terms of deployment, it's on-premises, specifically for the collectors that do the polling, but those collectors in turn talk to the HTTPS-protected public environment, though my company just needs the address.
Two people from the headquarters and one to two people at each of the facilities in charge of monitoring devices use LogicMonitor. One network engineer takes care of the deployment and maintenance of the product.
More than four thousand elements are being monitored now, and my company is continually looking to expand that.
My advice to others looking into implementing LogicMonitor is that it has exceeded requirements and has continued to do so.
My rating for LogicMonitor is eight out of ten, just because the team has been very responsive to suggestions that my company made to improve the product, especially in terms of usability. Because there's always room for improvement, I'm scoring the product an eight.
My company is an end-user of LogicMonitor, specifically a very active end-user.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Account Architect at a comms service provider with 201-500 employees
Highly scalable cloud-based infrastructure monitoring tool which is easy to integrate
Pros and Cons
- "The plugins are easy to integrate, and LogicMonitor provides these add-ons for vendors like VMware. It becomes very easy to integrate them and take the data sources."
- "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."
What is our primary use case?
We use it as a primary monitoring tool for our cloud offerings. I work for one of the largest service providers in Australia and their cloud solutions. We monitor the entire cloud solutions using LogicMonitor.
How has it helped my organization?
What is most valuable?
The plugins are easy to integrate, and LogicMonitor provides these add-ons for vendors like VMware. It becomes very easy to integrate them and take the data sources. One does not need to configure everything individually. It automatically detects all the resources by their type and starts monitoring them almost immediately.
What needs improvement?
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. I hope it will be there in the future.
My colleagues feel the ease of use is a concern because to implement the granularity of the product, you need some programming knowledge and understanding of code development.
So, it becomes a challenge for everyone in your company, especially administrators who might not know how to code. Otherwise, there is no problem with LogicMonitor.
For how long have I used the solution?
I have been using the solution for the past four years.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
It is highly scalable. We have never seen any issues regarding resource crunch. It's an everyday thing. All of our services use it as a primary resource for monitoring infrastructure. So in my department, we have fifty-odd people, and the service desk is around twenty-odd people. Our company is significant. We are on the verge of deciding whether You want to use this for the entire organization because a bigger company has acquired us, and that company does not use LogicMonitor. And we are pushing that LogicMonitor is a good resource for us, and we should use it across the company. Right now, it is in one department, but we want to push it across the organization, then it would become really big. We would have around two thousand end users using it. So, currently, we have two, and if this goes organization-wide, then there would probably be more people getting on board for this.
How are customer service and support?
It's very good. They were there when we required some assistance from LogicMonitor. I personally dealt with those cases, and I was extremely satisfied with the kind of response I received. I rate it ten out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I worked with NETGEAR and other internal tools, but nothing was as elaborate, extensive, graphically oriented, and well-informed as LogicMonitor. It is one of the best product analysts.
How was the initial setup?
The initial setup is straightforward. It took us around a week to thoroughly architect the solution deployment. The collectivity takes hardly five to ten minutes to install on any machine you want to be a collector and a monitoring resource. It doesn't take more than ten minutes. And installation of an architect is just a one-time job. You don't do it every day like we did it four years back. After that, we didn't look at it. We only spent some time, like, ten minutes creating new collectors, and that's it.
What's my experience with pricing, setup cost, and licensing?
The pricing can be a little aggressive. Right now, it's a bit much for smaller organizations to adopt it. But comparatively, it also provides good features. So it's a give and take.
Which other solutions did I evaluate?
We did evaluate it, and we saw pros and content. Looking at the cost structure, everything, and business requirements, this was the best fit for us.
As I told you, this bigger company has acquired us. The other departments use that product, and the cost structure is not as high as LogicMonitor. But I am researching it. I still need more information. But with my initial research, I found a gap in how Icinga takes care of necessary components of our infrastructure, especially IBM web infrastructure, and how LogicMonitor incorporates that versus how Icinga does it. I still need profound information, but the preliminary research shows a LogicMonitor is better.
What other advice do I have?
They have to first evaluate their options, consider their business requirements, use cases, and fix the purpose. If it is to process, LogicMonitor is definitely a tool to go for.
I rate it ten out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Teamlead at a tech services company with 11-50 employees
Provides real intelligence about what you are seeing and makes it easy to monitor and troubleshoot
Pros and Cons
- "One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot. Other products don't provide you with such information. You see a value going up, but you don't know what it means. LogicMonitor provides such information. For instance, if a value goes up, it says that it is probably because your disk area was too low."
- "One thing that could be really better is the mapping. Auvik is really good at it. They have a really nice way to give you a visual representation of your network, but in LogicMonitor, this functionality is not as powerful and as good as Auvik."
What is our primary use case?
I use it every day. We are a small MSP in the Netherlands. We have about 90 customers, and they have a lot of on-prem hardware such as servers, switches, voice systems, and devices. We monitor their environments making sure that everything is working fine. We monitor the hardware and the software performance, basic use, and things like that.
It is a cloud product. You have your on-prem LogicMonitor agents called collectors, and they send all the information to the cloud of LogicMonitor. You can view the state of everything there.
It seems Amazon hosted on the backside, so it should be a public cloud, but I am not sure.
How has it helped my organization?
When we have a new customer onboarding or when a customer visits us, we can show them how far we are able to monitor their systems. It is very easy for us to deploy it for a new customer. Most of the time, we go to the customer, and we deploy the collector. After that, we can tell them where the issues are. For instance, we can tell a customer that their main performance issues are related to their disks, servers, or memory usage on their SQL Server database, which helps in getting a sales conversation. We are able to say that if they are going to be a customer of ours, we will deploy the solution, and we will be monitoring it 24/7, but for now, they can do this. That's an easy selling point for us while engaging new customers. We can really help them with technical issues by using this solution.
What is most valuable?
One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot. Other products don't provide you with such information. You see a value going up, but you don't know what it means. LogicMonitor provides such information. For instance, if a value goes up, it says that it is probably because your disk area was too low.
The other thing that's very well done is the implementation of the product. When you are buying the product, you get a product manager from them who leads you towards the end result.
What needs improvement?
One thing that could be really better is the mapping. Auvik is really good at it. They have a really nice way to give you a visual representation of your network, but in LogicMonitor, this functionality is not as powerful and as good as Auvik.
What do I think about the stability of the solution?
We sometimes have glitches with the updates. You can opt-in or opt-out for the updates. LogicMonitor makes an update for a new device, such as a new device from Fortinet, so that you can monitor that. There could also be an update for the LogicMonitor collector.
When you do an update, you might get a warning that you shouldn't have got, but it is pretty easy to roll back your update so that you don't have it anymore. You can wait for the next update, or you can ask a technician to help you in a chat. They would need to look at your products, so you have to allow them to go live with you. They mostly solve the problem for you within a day.
What do I think about the scalability of the solution?
If I need 1,000 more servers, it is just plug-and-play. There are no problems with that at all.
We are an MSP in the Netherlands, and we have a lot of small companies that we are managing. They mostly don't have their own IT persons, so they're all managed by us. We also have customers who are able to log into their own monitoring software and see their own environment.
How are customer service and support?
They're really fast. I can chat with an engineer. It's not a bot; there is a real engineer. They help me with the product. If it is something difficult, it might take them two days, but most of the time, they're pretty quick.
Which solution did I use previously and why did I switch?
We previously used Zenoss, which is an open-source monitoring software, but there is no intelligence behind it to give you the answers about the things that you get on your dashboard. It is a different product. They have a free version, and they have a paid version. The paid version that they do has good support, but the intelligence behind LogicMonitor is what I like the most about it.
How was the initial setup?
When you are buying the product, you get a product manager from them who leads you towards the end result. They make a real project of what you want to use it for so that you have complete monitoring access up and running with event logs and the ticketing system, which is a good thing. They really help you with that. If you are transitioning from one product to another, they ask you what you want to transfer and how long do you think you are going to need to prepare everything for the switch over and even turn off the old system. They want to be involved in that.
It is very simple to set up for technical people. It is not a problem at all. We have finished 1,000 devices in about three months. The first month was to deploy the collectors and to make all the credential settings at the company site on all devices. You have to log into the device and configure some settings. In the next month, we added all the equipment. We got a lot of alerts because everything was new in LogicMonitor. We used the last month for alert tuning. You have to tune down the number of alerts and solve some problems to see what's going on. When you get more than 1,000 alerts a day, you're not able to look at them all, and it is necessary to get a good view of the system. So, it took us three months to switch from one system to another, and we did that with three people.
The setup is pretty straightforward, and it can be easily done by one person. For a small environment or a small company, it will take one or two days to set up the product to be able to log in and see things.
Its management, of course, can't be done by one person. That's because there are a lot of views and alerts, and there are a lot of things you need to do and manage every day. It needs maintenance. When you get a disk warning, you have to get an engineer to replace the disk. When you get performance issues, you have to contact that customer because they need more licenses or more hardware. It is not a product that you just look at; it is a product you have to use every day. It gives you information about the things that you need to do. For example, when you're driving your car and you get a maintenance warning for your engine, you have to plan maintenance at the garage. The car only gives you the information. Similarly, LogicMonitor only gives you the information.
What was our ROI?
We are able to provide help with a lot of last moment troubleshooting. If a customer says that they have a problem, we ask them when did they have it last. We can go back in time, and we can look at the logs and say that it was this server that was doing something, which makes troubleshooting easier.
We have bought Unomaly functionality, and we can search across all event logs from our customers. We can search with a name, or we can search for the last 12 hours. It gives us every event of every server and its time. It is a very fast way to look at a log file. It even has some intelligence in it, but that's a different story.
What's my experience with pricing, setup cost, and licensing?
It is pretty expensive, but we now need one less full-time engineer. With on-prem, we used to have one more engineer in our department. That engineer has now moved to another department. Our capacity is better with this product than the previous one. It is easy for us to manage the sites.
You have to choose between the standard account and the premium account. With the premium account, you get a lot more than the standard one, and you can also buy some extra features. It is a good thing to look at them because you would probably want to buy them. You should take your time and negotiate the price. They are easy. Like all cloud providers, they are able to discuss the price and if necessary, change the price.
Which other solutions did I evaluate?
We reviewed other solutions. One of the key reasons for going for it was the knowledge of the things that they put in the product. The other products we reviewed give you a lot of things for monitoring, but when something is happening, they don't give you the information about if it is good or bad.
For the test management software for server environments, we have used a product called Kaseya, which is not a big company. They have Kaseya Traverse that's a very intelligent program for monitoring. It is the next best thing for me to look at. It is a real competitive program for Kaseya Traverse.
What other advice do I have?
They are adding features faster than we can implement them. They have a very good development team. They have also made some acquisitions. They acquired Unomaly that did log analysis. It was from a Swedish company. That product is now completely integrated with LogicMonitor, and we bought that extra piece of software because one package doesn't fit all. It is a package that we are using to enhance our product catalog for logs, and it is a very useful one.
I would advise making a good project plan for migrating. That's the most important thing to do. Make a good choice while buying, and take your time. Don't rush into anything. When you're looking for monitoring software, you need to know what you need and what is nice to have. There are always things that you want to have, but they are not really necessary. You should choose products that can fit them all. As a system engineer, I want to have one pane of glass to look at everything. I don't want to switch screens to look at another log file or another system. I want to have it all visible in one system. That's the most important choice you can make as an engineer.
I would rate it a nine out of 10. Its price makes it a nine for me because it is pretty expensive. Otherwise, I would choose it over everything else. I will look at another product, but I'm sure I will come back to LogicMonitor.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free LogicMonitor Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
IT Infrastructure Monitoring Application Performance Monitoring (APM) and Observability Network Monitoring Software Container Monitoring Cloud Monitoring Software AIOpsPopular Comparisons
Zabbix
Datadog
Dynatrace
New Relic
Splunk AppDynamics
Azure Monitor
IBM Turbonomic
SolarWinds NPM
PRTG Network Monitor
Elastic Observability
NinjaOne
Splunk Observability Cloud
ThousandEyes
Cisco DNA Center
Nagios XI
Buyer's Guide
Download our free LogicMonitor Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Do you recommend LogicMonitor?
- Any experience with Event & Incident Analytic engines like Moogsoft?
- Windows 10 - what are your main concerns about upgrading?
- When evaluating IT Infrastructure Monitoring, what aspect do you think is the most important to look for?
- What advice would you give to others looking into implementing a mid-market monitoring solution?
- Zabbix vs. Groundwork vs. other IT Infrastructure Monitoring tools
- Anyone switching from SolarWinds NPM? What is a good alternative and why?
- What is the best tool for SQL monitoring in a large enterprise?
- How do you plan for a security review for infrastructure monitoring software?
- What are the advantages of using a paid (vs open source) IT Infrastructure Monitoring solution?



















