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.
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?
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.
Buyer's Guide
LogicMonitor
July 2026
Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: July 2026.
908,834 professionals have used our research since 2012.
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.
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 LifePoint Health
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 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."
- "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."
- "LogicMonitor should always improve AI because we are always striving for real intelligence."
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.
Buyer's Guide
LogicMonitor
July 2026
Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: July 2026.
908,834 professionals have used our research since 2012.
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 of the key reasons for going for it was the knowledge of the things that they put in the product."
- "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."
- "One thing that could be really better is the mapping. Auvik is really good at it."
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.
Director at TerreCom Pty Ltd
Gives our customers significant value in meaningful, real-time information about their networks and businesses
Pros and Cons
- "The concept of developing a dashboard template for ourselves, then cloning it for every single customer, and only having to change one piece of information, is a godsend. That's one of the strengths. We can develop a template that fits every customer and just change the information that is presented."
- "LogicMonitor gives us visibility into issues that we didn't even know existed."
- "There are some very specific things that need improvement in LogicMonitor. One is the lack of formatting for customized alerts, particularly the delivery of them to our email channel. We'd also like to see further customization of dashboards. Finally, something that is specific to us as an MSP that uses LogicMonitor, is white-labeling or skinning of the product, so we can make it look more customer-focused for our customers."
What is our primary use case?
We are a managed service provider and deploy LogicMonitor to support our customer base and monitor assets in the network.
We use it for monitoring our customers and alerting them when something happens. We also use it for dashboard reporting, both performance reporting and end-of-month reporting. We are now moving to use the platform with API connectivity to our new billing solution, to enable both-way billing updates. What that means for us is the ability to create an order, have the monitored endpoint in LogicMonitor created, and also feed back into the billing system so that we can invoice our customers correctly.
LogicMonitor is a cloud-based application and there is a small appliance installed on-premises to act as a collector. It's the device that talks to the cloud and is the intermediary talking to all the devices inside the network.
How has it helped my organization?
The benefit for us of LogicMonitor is the scalability of the solution to support many customers with a large number of devices. As our business scales, we are not having to go back and strap on more infrastructure or re-patch this or do that. It's a cloud-based platform that gives us all the benefits that come with consuming SaaS-based offerings.
Our customers are not necessarily aware that we use LogicMonitor in the background. They're buying a managed service from us and we choose to use LogicMonitor to deliver our services. But what they like about it is the ability to see information in real-time. Information that is presented in a way that they can gain value from it.
The solution enables us to pretty much drop a collector and automatically pick up everything in the target IT environment and map relationships. There is still tweaking that needs to happen after that. There can be devices that aren't configured correctly, and therefore you've got to go and do them, but it will at least tell you that some attention is needed. In some instances, there will be devices that it won't find because they're not running any of the necessary protocols to be found. But in our case, we're a little bit different because we know specifically the devices that we want to monitor. Generally we limit what to look for because we know exactly what we're expecting to find. But from a deployment point of view, the ability to drop a collector certainly saves a lot of time and effort, and the tools that are available make it quite easy to deploy and set up a customer quickly.
The collectors, along with templated integrations and dashboards, enable us to automate our onboarding process and rollout for new customers. When we onboard a new customer, we obviously want to be able to do it as quickly as possible. Building up everything based on templates allows us to save on effort and cost. We have invested a fair bit of effort into developing our own templates based on those included in the system. They allow us to deploy our look and feel in the solution we provide to our customers. That's a particularly important part of it because we really could not afford to be doing a custom deployment for every single customer type.
And when it comes to future-proofing our business to support our customers, we're quite comfortable with what the product offers today, and what Logic Monitor has been rolling into it for the last eight to 12 months. It is in line with what we would be expecting to offer our customer base. We want to see continued investment by LogicMonitor in AIOps, application performance management, logging, and enhanced dashboards. Their continuous product development is vital because we can't offer what we provide today in two years. We must evolve what we offer our customers, and that means we need our vendors to do the same thing: better capabilities, more capabilities, things that we couldn't offer before.
In terms of the functionality and capabilities of LogicMonitor, while it is only a small part of what we do through our managed service offering, it's a strong enabling tool to make that part happen. We'd like to think that it gives us "customer stickiness". In the end, it's part of an overall offering, albeit a very integral part of it. Could we do it without LogicMonitor? Maybe, but it would be a lot harder, and we would need another tool that does it as comprehensively as LogicMonitor does today.
In addition, LogicMonitor gives us visibility into issues that we didn't even know existed. That is the key aspect of the solution. It uncovers underlying issues before they require a full, reactive response. That's the value of this style of solution: understanding predictive behavior that might be symptomatic of something more serious occurring or failing.
I can imagine that if we didn't have the tools from LogicMonitor, it would take a much longer time to sort out some of the issues we see. The tools simply throw up an alert and we can go straight in and start resolving.
What is most valuable?
One of the features I consider most valuable is the flexibility it gives us to configure the solution to do what we need to do and what our customers are asking us for.
We use the solution’s templated integrations to get instant visibility into all the technology we monitor. That's an integral part of the solution, in that we don't want to be writing code and having to develop new connectors to talk to new appliances. There's a strong community, along with information provided by LogicMonitor, to keep the tools up to date for talking to all those different network devices. There's a massive library of all the potential devices that we might find in a network, information that is sitting there and ready for us to use should we come across a customer that has something that we've never seen before. The likelihood is that there is already a template built for it that we can leverage.
We started out using the solution's templated dashboards, but we have built a number of customized dashboards as well. The templated dashboards are a good starting point. In terms of customizing dashboards, there is a steep learning curve, but once over that hurdle and you understand the way the dashboards work, how to extract the information and display it, and what's possible, it becomes very easy. The concept of developing a dashboard template for ourselves, then cloning it for every single customer, and only having to change one piece of information, is a godsend. That's one of the strengths. We can develop a template that fits every customer and just change the information that is presented. The templated dashboards save us time getting up and running with visibility into our customers' environments and help our customers because we present some of those dashboards to them.
What needs improvement?
There are some very specific things that need improvement in LogicMonitor. One is the lack of formatting for customized alerts, particularly the delivery of them to our email channel. We'd also like to see further customization of dashboards. Finally, something that is specific to us as an MSP that uses LogicMonitor, is white-labeling or skinning of the product, so we can make it look more customer-focused for our customers.
For how long have I used the solution?
I've been using LogicMonitor for nearly 18 months.
What do I think about the stability of the solution?
We have not had an issue since we installed the solution, at all. It has been rock-solid.
What do I think about the scalability of the solution?
We're still a small business, but we've had no issues with scalability. We have added many new customers without any impact on performance. One of our key reasons for choosing this solution is the scalability when consuming a cloud-based product. We don't have to worry about our scalability. If we double, triple, or quadruple in size, we simply consume licenses as required. We're not worried about platform hardware and all the security challenges that go with that.
Apart from the scalability, the security of the platform, and the functionality that's rolled into it, comes with scale. That includes connecting more customers, more devices, more collectors, and through more API calls. It gives us the ability to do that without even thinking about the impact of adding another block of 500 devices to it. It is fantastic. We just look after our customers and don't have to worry about the platform in the backend.
How are customer service and technical support?
We've had excellent support, both tech support and account support.
How was the initial setup?
From the outset, as a brand new user when we first started, there was a fairly steep learning curve to LogicMonitor. However, now that we understand how to get good value out of it, we find it quite easy. We are at the point where we're starting to automate the configuration so we don't have to spend anywhere near as much time as we did when setting up our first couple of customers.
For organizations picking up LogicMonitor for the first time, I would suggest they take advantage of the onboarding teams from LogicMonitor, their success manager and their account manager, to get from start to operate as quickly as possible.
What was our ROI?
The solution gives us the ability to charge a competitive price for a premium product. The cost of LogicMonitor is built into our service offering. From our point of view, it's a cost component for delivering our service.
What's my experience with pricing, setup cost, and licensing?
For us, LogicMonitor is now value for money, but we are still on a plan from a few years ago. The challenge for us in Australia is the billing from LogicMonitor is done in U.S. dollars. The exchange rate between the Aussie dollar and the U.S. dollar has not gone in our favor over the last 12 months. A number of the other big players in this space will bill in your local currency, and that is of value to us. We've raised the issue with LogicMonitor.
That said, they're generally quite open and flexible to a discussion around licensing. We're on the the full Enterprise offering. We've pretty much got everything turned on. From our point of view, they've always come back to the table when we've had to grow and move to the next level, and they've given us advice on the best way to do that.
Which other solutions did I evaluate?
We evaluated six solutions at the time. We then narrowed it down to a short-list of three, and we ended up buying two systems. We still operate two systems today because there are a couple of things that LogicMonitor doesn't do that the other systems do extraordinarily well. That's the way we've chosen to run our business. The specific lack in LogicMonitor is the real-time, live network map. It has basic functionality, but it's nothing like the competitive offers from SolarWinds or Auvik.
What other advice do I have?
Like any good project, spend plenty of time upfront working out precisely what you want out of LogicMonitor, before you race off and start deploying it. Otherwise, you'll end up doing a lot of reworking. Take advantage of the onboarding resources, and even pay a little bit of money, if needed, to give you that leg up and the headstart in understanding how the platform works. If you know what your customers want to get out of it, and what you want to get out of it as a business, the platform will most likely be able to give you what you want. From there, you'll end up in a comfortable operational place where you can look at taking the next step into process automation with all the API functionality to improve business efficiency.
The strength of LogicMonitor is in the dashboards and the information that's available. Every customer likes a dashboard, so if we can give them dashboards that provide meaningful, real-time information about what's happening in their network and across their business, they see significant value in that. Most solutions don't have that today.
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.
Solutions Engineer at Black Box Network Services
Reduced our false positives significantly, improving our reliability, SLAs, and uptimes
Pros and Cons
- "The dashboards are the big seller for us. When our customers can see those graphs and are able to interact with the data, that is valuable. They can easily adjust time ranges and the graphs display the data fast. We've used other tools in the past, where you'd say, "Hey, I want the last three months of data on a graph," and it would just sit there and crunch for five minutes before you'd actually see the data. With LogicMonitor, the fast reliability of those dashboards is huge."
- "We have definitely seen return on our investment with LogicMonitor, especially once we showed how we could replace that Prognosis tool with it."
- "One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child." For example, If I know that a top gateway is offline and I can't talk to it anymore, and anything that's connected below it or to it is also going to be offline, there is no need to alarm on those. In that situation it should create one ticket or one alarm for the parent. I know they're working towards that with their mapping technology, but it's not quite to that level where you can build out alarm logic or a correlation logic like that."
- "One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child.""
What is our primary use case?
We use it for alarming on Cisco Voice systems, the Unified Communication stuff. We monitor all the gateways, trunks, SIP trunks, servers, and make sure all of the application is functioning, calls are being completed, and that there are no performance issues on the network or the voice system.
How has it helped my organization?
We used a different monitoring tool to do the Cisco Voice monitoring and our customers were very unhappy with us. It was missing stuff when monitoring, meaning it wasn't fully knowledgeable about checking all the OIDs and other things. It wasn't robust enough to allow us to customize it and build it out. Customers were getting very unhappy with that and they didn't like the dashboards, the graphs, and the reporting that came out of the other tool. When we moved over to LogicMonitor and we were able to show everything that we could actually deliver, a lot of our customers that were leaving came back to us or have provided us more services. We now have a proper tool that can deliver the services that we actually need, and that we've actually quoted and have contracts for.
The solution's ability to alert us if the cloud loses contact with on-prem collectors means we get alarms when a customer's collector isn't calling home anymore. That allows our engineers to know that there's some sort of serious outage. Either there's a power outage, the server crashed, or the internet's down. That's something that triggers our engineers to look at the customer and figure out why the monitoring solution is down. Is it the monitoring solution itself, is it the customer, or is it an act of God?
In addition, we had a lot of false positives before because we used a lot of VPN tunnels with other solutions. Moving to a SaaS solution and using LogicMonitor and the cloud has helped us a ton because it's improved reliability, SLAs, and uptimes. We've seen a 70 to 80 percent decrease in false-positive alarms.
Another benefit is that we went from three monitoring systems down to one. The first solution was Prognosis, which was developed by Integrated Research. The other tool was N-central, which is now provided by SolarWinds. We consolidated those two tools down into just LogicMonitor.
We've also been able to automate things such as cleaning up disk space or restarting a service. If the monitoring system catches a service not running, instead of initially sending off an alarm and creating a ticket, it's going to do some self-healing, to try to restart that service or run a script that cleans up some disk space. If that still doesn't fix the issue, it then passes the alarm on to create a ticket for a human to look at.
That saves us time because, obviously, it doesn't disrupt an engineer and force him to try to log in to that customer and try to start the service or look at logs. It just says, "Hey, we restarted it. Everything's up and running," and there is no real impact to the company or business. It didn't take time for an engineer to look at it, respond to a ticket, and close the ticket. If a single service isn't running, that's about 15 minutes, at least, of an engineer's time. If an engineer doesn't have to do that three times a day, he's saving about an hour.
What is most valuable?
The dashboards are the big seller for us. When our customers can see those graphs and are able to interact with the data, that is valuable. They can easily adjust time ranges and the graphs display the data fast. We've used other tools in the past, where you'd say, "Hey, I want the last three months of data on a graph," and it would just sit there and crunch for five minutes before you'd actually see the data. With LogicMonitor, the fast reliability of those dashboards is huge. Allowing our customers and nontechnical people to see what is happening in their environments in an easy, friendly way is huge for us. That's the big feature we use and push on our customers.
I have two favorites when it comes to dashboards. I put together a few dashboards for the voice systems that allow the customer to to see how the performance is going: green light/red light. They see green and everything looks good. Being able to click into that and interact with the dashboards to then drill down and get more info is awesome. The other thing that I really like is their Google Maps widget that goes inside of a dashboard. That is great for customers that have multiple locations across the country. They can see, "Oh, hey, I've got a regional outage in St. Louis, or the West Coast has a power outage, or everything is green. I see all my sites in my countries are green. Everything is good in my environment."
Another valuable feature would be their logic modules. They are little scriptlets or settings so you can say, "Hey, I want to monitor this OID or these services," etc. That's huge in terms of customizability and having the system be robust. Out-of-the-box, monitoring solutions don't always have everything you need. You might say, "Hey, I know that there's this new OID for this new firmware," and you need to be able to write something to call that and pull it into the monitoring system. The logic modules within LogicMonitor, being so robust, is awesome because I can easily go into the tool, add something and push it out to all my customers and, boom, I'm off running with all this monitoring. And it took me five minutes to put it together.
In terms of the solution's reporting capabilities, I look at it in two ways. One of the ways is the dashboards. Being able to take all those dashboards and say, "Hey, I want a recurring report every quarter for QBRs," is awesome. On the technical side, for all the back-end stuff, being able to use reports to export information so that I can use it to inventory or check properties of stuff in the environment — do assessments — I really like those as well.
In addition, the solution's ability to customize data sources was big and something I did a lot of to build out the Cisco Voice monitoring, so that we could deliver what we've been contracted to do.
Another big thing we use a lot is LogicMonitor's granular alert tuning for devices. A customer might say, "Hey, we know this SIP trunk is going to have this utilization, so tweak the threshold for that one interface or that one SIP trunk at this level, but leave everyone else at the default." Or, "Hey, we're going to be doing maintenance on a power supply, so we'll need to set downtime or suppress alarming for that power supply, but let everything else that we're monitoring for that system go through." Using that granular ability is great for that. It's also great for adjusting alarming. They'll say, "Hey, we want this specific interface to be a priority-one alarm," but it's default is priority-two. Being able to tune that within the alert rules and get that granular and say, "This specific interface is going to be different, it's going to go somewhere else," or "it's got a different priority," is important.
What needs improvement?
One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child." For example, If I know that a top gateway is offline and I can't talk to it anymore, and anything that's connected below it or to it is also going to be offline, there is no need to alarm on those. In that situation it should create one ticket or one alarm for the parent. I know they're working towards that with their mapping technology, but it's not quite to that level where you can build out alarm logic or a correlation logic like that.
I would also like them to expand more on their resources view, which is their tree structure of all the devices and what's being monitored. I'd like to see some logical type of grouping of services. If I know I've got this web application which is using this SQL database and this service from this web server, it would be helpful if I could create a special view for those kinds of services and instances.
For how long have I used the solution?
I used LogicMonitor about six years ago at a different company. It was brought in there and I used it for a few years. Then I transferred to a different employer at which time I brought LogicMonitor in. It was in about 2014 when I first got exposed to it. With this new company, we've been using it for about four or five years now.
What do I think about the stability of the solution?
I am happy with the solution's stability. I haven't had any issues with reliability, with the service going offline or not being available.
What do I think about the scalability of the solution?
LogicMonitor will be able to scale to many more devices, if we need it to.
We're monitoring about 1,200 devices currently. That's a bit of a misleading number because there's so much more stuff we monitor, like virtual machines that don't really count as licenses, or even phones. We're also monitoring Meraki devices and cloud stuff. We're monitoring almost 30,000 phones with the tool, but they're not really devices in terms of licenses.
How are customer service and technical support?
Their support is fantastic. They're always there to answer your questions and they're very knowledgeable.
How was the initial setup?
The initial setup was very straightforward. Installing the collector at a customer site is super-easy. You do a basic default install, "next, next, next, finish," and it's calling home.
Adding devices and getting customers set up, whether they've got one device or 1,000 devices, is easy. I can import a CSV and it starts going out, scanning, setting up everything, and auto-discovering all the different services. There is a lot of automation that makes it easy for us. Before, with other systems, if I knew there was a Windows server and it had SQL, I would have to add these special SQL packages and then add this other package. And then I might forget: "Oh, hey, there's a special service I was supposed to monitor." Having all those data sources and automation within LogicMonitor makes it easier for us to set up and deploy.
The solution's automated and agentless discovery, deployment, and configuration is that ease of use. No matter how many devices there are, being able to easily import and add them in is great. Having it automatically know it's scanning SNMP, for example, when it finds this name in this one OID it knows it's a Dell Storage unit and that it needs to automatically apply all of these special Dell Storage unit monitoring services. It will scan how many hard drives there are. If it finds there are 12 hard drives instead of 24, then it only monitors 12. Or instead of having two power supplies in this unit, if I'm only seeing one power supply, I should only monitor the one. That automation is awesome.
LogicMonitor also monitors most devices out-of-the-box. For us, it's a lot of the Nexus switches and VSS, which are the Cisco Virtual Switching System. There was so much stuff and we didn't know what we could monitor with our other solution. We saw only the basic stuff. When we installed LogicMonitor for this one customer, and added the Nexus switch, all of a sudden we saw module stuff, a lot more interfaces, and different hardware things. All of that was out-of-the-box and we were blown away by that. We didn't realize we were missing 70 percent of what we could monitor on this one device until we switched to LogicMonitor.
That was actually the big savior for us for this very large, high-profile customer. We were using N-central for them and it required 15 collectors to monitor these 4,000 devices. We were able to use LogicMonitor and get that down to two collectors to monitor all that. The customer had been calling us out on it saying, "Hey, how come you don't see this? How come you don't see that?" We had to throw our hands up in the air. Once we introduced LogicMonitor and showed them what we did within five minutes, and all of the stuff we could see, they said, "Perfect. We'll stick with you guys. You seem to have the right solution."
What was our ROI?
We have definitely seen return on our investment with LogicMonitor, especially once we showed how we could replace that Prognosis tool with it. The cost savings were through the roof. As an example, for one customer of ours, for one year with the Prognosis license, it would have cost $180,000. With LogicMonitor, it only costs us about $8,000 to $9,000. That's a huge savings, and it's great for the customer because it means we can lower our cost and they think we're losing money, but we're still getting so much. That was a huge benefit.
What's my experience with pricing, setup cost, and licensing?
It's affordable. The price we get per license is a lot cheaper than what we were getting with some of the other tools. There are other monitoring tools out there that are cheaper, but what you get with LogicMonitor, out-of-the-box, makes it worth the cost. It works well.
Which other solutions did I evaluate?
There were a few other tools we looked at. Their pricing, how complex their setup was, and even their dashboards and reports were all considered. LogicMonitor seemed to fit all those categories for us and give us huge improvements. It was a no-brainer.
We looked at WhatsUp Gold. We looked at the main SolarWinds package and there was a tool called ScienceLogic that we looked at. And there was also Nimsoft.
What other advice do I have?
Do it. Your customers are going to like it, once you show them the dashboards, the pretty colors, and the ability to easily interact with it. That's going to win over your customers. I guarantee it. I've seen it happen. You can say, "I've got this tool that does everything," but if the customer can't tangibly see what the tool is doing, they'll say, "Well, what am I paying you for?" And they don't want to see generic spreadsheets. They want something that's easy to use and interact with.
I like how they've been improving on it over the years. It seems like they're going in the right direction. LogicMonitor fits what our company needs, and we plan to keep on using it for at least five more years, until something else gets better or they're out of business.
We don't use its AIOps capabilities for things like anomaly detection or root cause analysis yet, but that is something we are looking into. I know they're releasing those features in phases. They've got the first phase of AIOps and then they're pushing the next one with the dynamic thresholds, and that is definitely something we're going to be using, especially when you're looking at Cisco Voice systems and how they perform throughout the day. Dynamic thresholds are going to be huge for us, so that's going to be exciting.
We have about 100 people who work directly with LogicMonitor in our company. They're all the way from managers down to the low-level NOC people who are answering the telephone, to the Tier-3 engineers, and even the sales and marketing people. Everyone interacts with LogicMonitor in some way, either supporting a customer, running reports, or looking at the capabilities and what we are monitoring.
Overall, I've been very happy with the solution so far.
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.
Account Architect at Aussie Broadband
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.
Director at a tech services company with 1,001-5,000 employees
Useful for traditional infrastructure monitoring, easy to set up, and technical support is helpful
Pros and Cons
- "The most valuable feature of LogicMonitor is the infrastructure monitoring capability."
- "LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem."
- "Dashboarding capabilities could be enhanced. It is cumbersome, you must do it all at once, and then you must repeat the process every now and then."
- "If you only want to use LogicMonitor in the cloud, there's a better tool available."
What is our primary use case?
LogicMonitor is predominantly used in modern cloud monitoring tools. You have servers that you want to monitor for performance, CPU, memory, and so on, or you have a cloud environment that you want to monitor for EC2 instances, ALBs, and more.
Our LogicMonitor keeps track of everything. LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem.
What is most valuable?
The most valuable feature of LogicMonitor is the infrastructure monitoring capability.
What needs improvement?
Dashboarding capabilities could be enhanced.
It is cumbersome, you must do it all at once, and then you must repeat the process every now and then. If you ask me, I would rather it be automatic because they know what I monitor. If they have a template that they can provide, I can create a dashboard without even trying.
The issue right now is that I'll have to combine tens of widgets to create my own dashboard which is a little time-consuming and inconvenient.
For how long have I used the solution?
I have been working with LogicMonitor for seven years.
We have the latest version. LogicMonitor is a SaaS product.
What do I think about the stability of the solution?
LogicMonitor is a stable solution.
What do I think about the scalability of the solution?
LogicMonitor is a scalable product.
In our company, we have 5,000 users.
How are customer service and support?
Technical support is good.
How was the initial setup?
The initial setup is easy.
The deployment took one day to complete.
What's my experience with pricing, setup cost, and licensing?
They are expensive for the cloud.
What other advice do I have?
If you only want to use LogicMonitor in the cloud, there's a better tool available. But if it's for traditional infrastructure monitoring, it makes sense; it's a useful tool.
However, if you are a cloud-native organization and want LogicMonitor, I believe it will be a costly investment because there are many better cloud monitoring solutions available.
There are numerous options, including CloudWatch itself, or Grafana with a connection to a CloudWatch data source. You can use Grafana to monitor as well as others, there are numerous tools available.
They are good, I would rate LogicMonitor a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Senior Monitoring Operations Engineer at ANS Group plc
Great LogicModules, a useful dashboard, and easy to use
Pros and Cons
- "Having a full team at LogicMonitor for support is super helpful as they are available all the time to answer any questions you may have."
- "Having a suite of modules that do all the work for you rather than having to set up loads of things yourself and it be there straight away ready to go is mind-blowing."
- "Role-based permissions could be better and updating modules could be smoother."
What is our primary use case?
We primarily use the solution for managed services, Azure/AWS, Kubernetes, and website monitoring.
We look after all sorts of devices and being able to have monitoring coverage of 90% of things we need is great and saves us time. If we need to make some specific change we can and it's relatively easy to do.
Having a suite of modules that do all the work for you rather than having to set up loads of things yourself and it be there straight away ready to go is mind-blowing.
Being able to use this tool with relative ease makes it a worthy monitoring solution.
How has it helped my organization?
LogicMonitor allows streamlined use and offers ease of use with an all-in-one monitoring solution that is SaaS-based. Having this solution SaaS-based means we don't have to handle the platform updates.
Having a full team at LogicMonitor for support is super helpful as they are available all the time to answer any questions you may have.
Having a super easy tool to work with allowed our support staff to get up to speed quickly and has made dealing with alerts and incidents a breeze.
What is most valuable?
LogicModules are great. Creating these is super easy and fun. Allowing users to make their own modules allows monitoring to be covered from all angles. We can make a script, for example, and go get metrics that may not be there out of the box.
The dashboard is helpful for showing off all that data you collect and impressing customers. Dashboards are a real good selling point as showcasing the data you collect all in one place makes troubleshooting and keeping an eye on things way easier that a giant alert list. Having them on a slideshow is super neat too.
What needs improvement?
Role-based permissions could be better and updating modules could be smoother. They are my biggest complaints as they are lacking in comparison to other tools I have experienced. That said, all the feedback we can give to help improve the product as it matures will help the LogicMonitor team build an amazing solution in years to come.
Roles just miss some extra permissions such as allowing people to see certain instances yet not the full device. We'd like to allow for dynamic groups to be made without the need for root permissions.
Module updates are important and you have got to stay on top of them. However, this needs work to make it easier as the loss of data can occur if you are too out of date.
For how long have I used the solution?
We've used the solution for over five years now.
What do I think about the stability of the solution?
I have never had an issue where the stability of the portal was affected.
What do I think about the scalability of the solution?
The solution offers very good performance and can scale easily and flexibly.
What's my experience with pricing, setup cost, and licensing?
I'd advise new users to set it up the way they want and make sure they update/import everything they can.
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.
Vice President at Zix
You can bring up your hardware and software stats in a single windowpane
Pros and Cons
- "Whenever we reach out to our customers, we give LogicMonitor as a dashboard to them so they don't need to monitor the hardware side separately. For example, if my service is running on their hardware X, that means they don't need to monitor hardware X and our services too. LogicMonitor has the capability of monitoring their hardware as well as our services. This is how LogicMonitor helps us."
- "LogicMonitor has evolved drastically in the last couple of years; they have made a lot of changes and are moving very fast."
- "We are working with LogicMonitor to get flexibility to see the absolute running numbers, rather than doing an average. They can keep the average for customers who want it, but there should be a way to at least show the real numbers, which are coming every second on the screen."
- "This is one thing that is a pain and flaw with LogicMonitor."
What is our primary use case?
If I summarize LogicMonitor, it is a single windowpane. You don't have to run four hardware stats and software stats on multiple screens during the monitoring of services. It gives you flexibility. It has the capability to pull up your data sources as well. So, it is like a single window, where you can see all your resources recorded, e.g., what value are you deriving out of your software?
We have our own product that we are specialized in. We needed something to help us with the setting up of the monitoring part.
Our customers are very happy. They are running Dell EMC hardware, so they don't need a Dell EMC monitoring window and our software windows. With LogicMonitor, they can see what is happening inside Dell EMC in a single, unified view that completely monitors their alerts.
How has it helped my organization?
We have some customers who are running a mix of Dell EMC, HPE, and Cisco hardware. We have our own software, as a service organization. We don't sell hardware. Whenever we reach out to our customers, we give LogicMonitor as a dashboard to them so they don't need to monitor the hardware side separately. For example, if my service is running on their hardware X, that means they don't need to monitor hardware X and our services too. LogicMonitor has the capability of monitoring their hardware as well as our services. This is how LogicMonitor helps us.
LogicMonitor has the ability to alert us if the cloud loses contact with on-prem collectors. We have more than 50 on-prem collectors, and there is the flexibility of putting an escalation chain to every collector. So, if a collector goes down, then whatever escalation mechanism is bound to that particular collector can fire. For example:
- If an email has been attached to that collector, that email will come.
- If a call is attached, that call comes via mobile.
- If an SMS is there, then that SMS comes via mobile.
- Third-party external integrations over PagerDuty or any HTTP delivery also happen because they have the ability to send alerts through Slack as well.
What is most valuable?
We use the LogicMonitor dashboards with a couple of widgets. We have some custom dashboards as well. The CPU and memory usage dashboards are very cool to run, because if the hardware is intact, then your hardware services are working fine.
We have around six to seven customers working with customer data sources. It helps us give more reports to our customers. For example, the CPU and memory usage are standard dashboards which count how much memory and CPUs are working. However, there are certain things that our customers want from the application side, like how many signups you're doing. We created those data sources on LogicMonitor and helped our customers see the same dashboard on the same screen. This has helped us a lot.
The solution provides us with granular alert-tuning for devices. They have three thresholds out there: warning at 70, error at 80, and critical at 90. You can segregate whether you want to call it a warning, error, or critical. There is flexibility, and we are happy with that.
Go-to-market is very easy with LogicMonitor. Today, if my customer needs five dashboards of software and 10 dashboards of hardware, then I am capable of delivering that with LogicMonitor.
What needs improvement?
I would give reporting an eight out of 10. LogicMonitor takes the data from us and does an average on the graphs. So, it doesn't show the absolute case. This is one thing that is a pain and flaw with LogicMonitor. For whatever data that gets collected from the hardware, it shows the average of one minute. This is basically a pain because we don't know what is happening in those couple of seconds, because what you see is the last minute's average. For example, if there is a surge of over 100, we will not be able to see the 100. It will turn down to the average of 50 or 80. Then, it becomes a tug of war with customers, where we will say that it was because of a surge it closed at 120. They reply, "No, in the graph, it is showing 50. How can you say 120?" Then, we tell them, "No, LogicMonitor pushes the average out every minute." We keep some of our services at a threshold of about 100. Whenever the threshold crosses 100, then the service will fail. However, the graph never shows 100. The graph will show 50 or 80, because it is an average per minute.
We are working with LogicMonitor to get flexibility to see the absolute running numbers, rather than doing an average. They can keep the average for customers who want it, but there should be a way to at least show the real numbers, which are coming every second on the screen. This is not something new that we are asking for. There are a couple of freeware available in the market, Munin or WhatsUp Gold, which have these capabilities to show real, absolute numbers as well as the average, min, and max. What we get from LogicMonitor is only the average, min, and max. The absolute is not there.
We are not asking anything new or out-of-the-box from LogicMonitor. Our customers realize that these things are available in freeware versions in the market. Also, whatever is added as free should be a part of their paid subscription.
Everybody is moving onto their mobiles. In the last five years, the development of their mobile application has been very slow or non-existent. Whatever the improvements have been made, they were made on the desktop view. However, on the mobile side of it, it only has the monitoring. As an administrator, if I need to create a user, then I need to open a laptop or go to a desktop to create a user. I can't create a user from the mobile application.
For how long have I used the solution?
I just started using LogicMonitor.
What do I think about the stability of the solution?
The stability is fine.
What do I think about the scalability of the solution?
I don't see any challenges with scalability. Whatever my product is capable of delivering, LogicMonitor is delivering that too.
The users of this solution include my team members. They use the LogicMonitor Portal for customer account creation and credentials, such as changing a password or creating dashboards. Also, all our customers have read-only access for their dashboards.
We monitor close to 100 devices. We have plans to increase that usage in the future.
How are customer service and technical support?
The support is very good. We are happy with the kind of attention that we get from our customer service manager (CSM).
Which solution did I use previously and why did I switch?
In 2016, we started off our organization. The same thing happened with LogicMonitor. The timing was that we were both startups at the same point in time, so we grew at the same pace. We never checked another competitor of LogicMonitor, and LogicMonitor was our first buy of its kind. We have been with LogicMonitor since day one.
How was the initial setup?
The initial setup was very easy because they have product manuals and provide guidance. What they have maintained on their website is very concise and their team is very eager to help as well.
If I go through their manuals and website, they cover a lot of devices out-of-the-box, including Cisco and even customized development.
LogicMonitor has a long list of OEMs that they can monitor and service, like Barracuda, Fortinet, FortiGate, and Cisco.
What was our ROI?
There is no ROI. We are mitigating outages for our customers, but not really saving time.
What's my experience with pricing, setup cost, and licensing?
LogicMonitor is competitively priced at the same level as other vendors, like Datadog.
Which other solutions did I evaluate?
We have not tried another operator, like Datadog, or other solutions out there. We were early adopters with LogicMonitor, and we have stuck with it until this day.
It takes a lot of time to develop a data source to put on the LogicMonitor platform. It's not easy for us to plug out of LogicMonitor and plug into Datadog. Plugging out and plugging in will work only in cases where we are monitoring basic things like CPU memory, which comes with the default package. When it comes to custom data sources, LogicMonitor has given us the option to write a script that they can make visible in their dashboards.
When I talk to competitors, like Datadog, they have their own ways of handling data. To consider switching, we would need to invest our time in understanding which formats work with their product and how that will impact our customers and their timelines.
What other advice do I have?
LogicMonitor has evolved drastically in the last couple of years. They have made a lot of changes and are moving very fast. They are getting accustomed to machine learning, AI, DevOps, etc.
Don't reinvent the wheel. Just concentrate on your business and put your monitoring on LogicMonitor.
The solution has helped consolidate the monitoring tools that we need to an extent. For example, if our customer is running an HPE machine and doesn't have a license for HPE monitoring, they can at least see the basic hygiene level of hardware through LogicMonitor.
In the last month, we deployed the agentless collectors. We are still in the phase of commissioning those devices, so I don't personally have any experience on this.
I would rate this solution as an eight (out of 10).
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
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.
Pre-Sales Technical Consultant at a tech services company with 11-50 employees
Enables us to consistently wow our customers and set high SLAs because it reliably tells us if there is a problem anywhere
Pros and Cons
- "It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that."
- "LogicMonitor enables us to consistently really wow the customers by sorting that out."
- "One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting."
- "One of the areas that I sometimes find confusing is the way that the data is presented."
What is our primary use case?
We use LogicMonitor to monitor our customer environments. Some customers opt to look after their own environments, but some customers have us monitor them for them.
We use it to monitor the availability of servers and of network hardware. We have some storage array networks that are being monitored by it as well. We really use it as a guide to help. We monitor all of the key components in the different environments that we have running under LogicMonitor, and we use LogicMonitor as an early-warning system. If a problem develops in a customer environment, and we're monitoring it with LogicMonitor, then we get fairly rapid notification that there's a problem so we can start looking into it and doing something about it.
Also, along with all of that monitoring comes a lot of information logging for things like bandwidth, so we can see how much data is coming and going over different links. If a customer came to us and said, "We're thinking about downgrading the network links that we have," we have evidence to present to them to say, "Yes, it's okay to do that because you're hardly using the network link." Or we can say, "We wouldn't advise you to do that because we've observed that you're using most of that link and, if anything, you need to increase your bandwidth."
The device numbers being monitored is definitely on the order of several hundred among our three or four dozen customers. We're probably monitoring 50 different environments.
How has it helped my organization?
The solution's ability to alert you if the cloud loses contact with the on-prem Collectors is the crux of the solution. The customers are relying on us being proactive and highly responsive to any outages in their environments. A lot of the time, when we're phoning the customer up and saying, "We've detected that you've got an outage here," the customer doesn't even know about it. It hasn't even filtered through and their people haven't reported it. LogicMonitor enables us to consistently really wow the customers by sorting that out. They're saying, "I didn't even know that there was a problem in the environment," and we're already getting on and fixing it because LogicMonitor has allowed us to do that. It's really good.
The deployment is all automated, once we've selected where we want the Collectors to go. It saves us time because we're not having to faff around doing it. That might save us an hour per customer. The agentless aspect of it speeds up the deployment. Once we've got a single Collector there, we can leverage the information that that Collector can gather from all of the other devices. That's also really good.
What is most valuable?
The monitoring is the most valuable feature, the ability to have Collectors monitoring the health of different services. That's the thing that really helps us.
Among the dashboards, it's the availability ones that are my favourites. We have them set up so that they're only going to flag problems. If we look at the dashboard and it's completely empty, then we know that everything's in the green. If we look at the dashboard and there are entries on it, it means that somebody, somewhere, has a problem.
We use LogicMonitor's ability to customize data sources where a customer is providing web services or when looking at the availability of shared storage arrays. That's where we've started to customize it a little bit more to look at specific metrics that the Collectors have.
LogicMonitor provides us with granular alerts tuning for devices and that enhances our monitoring. The granularity that LogicMonitor goes into is really good. At first it can be a bit overwhelming because there's so much to it. But once you've distilled down the bits that you need to be paying attention to, and the bits that you're not particularly interested in, then it makes it quite simple. And when I say "all of the bits that you're not interested in," you're not interested in them right now. But that's not to say that in the future a requirement won't come up where you actually need to look at those bits. The fact that it supports so many different monitoring features is really good.
What needs improvement?
One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting. With some data types, it's not really possible to do that.
But that's one of the good things about LogicMonitor: You've got all of the data there. The sheer wealth of data that it gathers means that you can take that data and manipulate it in other ways, if you want to.
For how long have I used the solution?
We've been using LogicMonitor for three or four years now. We're partnered with LogicMonitor, so we can resell the solution as well.
I work in a pre-sales role, so when customers need new solutions they will come and ask. If I'm looking to scope replacement hardware, or if I'm looking to review the bandwidth utilization at a customer site, that's when I would go into LogicMonitor. Our service desk, predominantly, does the day-to-day monitoring. Whenever I come to LogicMonitor, it's a case of delving into historical data. At the same time, I've got an appreciation of how the solution works and the cool stuff that it'll do.
What do I think about the stability of the solution?
I've got no reason to believe that it's unstable, at all. I've not heard of Collectors crashing or the main console being unavailable for any extended period of time. There are periods of maintenance where it would be unavailable, but I'm certainly not aware of anything that was cause for concern with regards to the stability.
What do I think about the scalability of the solution?
It scales well; no concerns whatsoever.
How are customer service and technical support?
I've never actually used their technical support, but I know that our guys have, and they've always been able to fix problems fairly quickly. The technical support, as far as I'm aware, is really good.
How was the initial setup?
I believe LogicMonitor monitors most devices out-of-the-box, but that was done with the setup which I wasn't involved in. We've got a lot of different customers. They've all got different types of network hardware. They've all got different storage arrays. Some of them have different types of hosts from different manufacturers. But we're able to monitor all of them with LogicMonitor because the information that LogicMonitor is pulling from them is common across them. The devices include Dell and HPE hardware, such as storage arrays, including Nimble, as well as a lot of Cisco networking gear. It will even monitor stuff that isn't enterprise-grade, but provided that something is enterprise-grade, it typically conforms to all of the WMI monitoring capabilities that LogicMonitor plugs into.
We have about half-a-dozen people who use LogicMonitor, and they're mostly third-line support engineers, so they're quite senior engineers. We have first- and second-line support and they just do the monitoring, but a lot of the really serious investigation, if there are any issues, go over to senior roles.
What was our ROI?
It gives us the ability to talk about our monitoring solution and service with a very high degree of confidence in ourselves. And we can set very high SLAs because we know that LogicMonitor is reliably going to tell us if there's a problem anywhere. That will enable us to start working on it very quickly, which in turn will help us to deliver very high SLAs and very rapid response times to our customers. Obviously, customers are going to be happy about that because they want things fixed quickly. That is the best benefit that I see from it.
What's my experience with pricing, setup cost, and licensing?
It's an enterprise-grade solution and competitively priced compared to the other solutions that are out there. If it were extortionately expensive, we wouldn't be using it. If it weren't doing what we needed it to do, we wouldn't be using it. Our organization is not huge, but LogicMonitor is worth every penny that we pay for it. I've never heard anyone say, "I'm not sure that we're getting good value for money from this product." It's integral to our business.
When you compare it to competitors, maybe some of the competitors' products are going to be a bit cheaper, but it comes down to the functionality that you're getting. You're paying for what you're getting, so I would say it's good value for money.
Which other solutions did I evaluate?
The solution's overall reporting capabilities are pretty good. We've assessed a lot of different solutions, because if we're offering a monitoring service to customers, it needs to be really good. We looked at SolarWinds and other ones, but LogicMonitor was the one that consistently came out on top across the monitoring requirements. LogicMonitor was hands-down the best.
LogicMonitor consolidates the monitoring tools that we need in one solution. We didn't have any tools in place originally, but all of the different types of things that we want to monitor comprised one of the reasons that LogicMonitor came out on top. It was the sheer breadth of functions that it has. A lot of the monitoring solutions that we were looking at would only do maybe 75 percent of it. They would monitor the uptime of servers and they would monitor the availability of network links, but they wouldn't give us any information around the bandwidth utilization of those network links. Other solutions would give us the bandwidth utilization, but then they wouldn't be able to monitor the servers. LogicMonitor gave us everything in one package.
What other advice do I have?
It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that.
I'm not aware of any false positives that we get through LogicMonitor. That could be because we've tuned it over time so that we've tuned out any of those false positives. But generally speaking, if LogicMonitor flags something, there is a problem. Sometimes those problems are transient and something is just flagged because there was a blip in the system for whatever reason. But then it resolves itself without any intervention. LogicMonitor still allows us to see all of that stuff.
There are always lessons learned when you're running anything like this at scale. You set things up the way you think they should be set up initially, and then, with 20/20 hindsight you invariably decide, "Well, we didn't need to do that. We should have done this." But the solution allows you to do that. You don't end up fenced into a corner where you configured something the wrong way initially and you can't undo it. If you do see ways of doing things better, you can change them as you go.
I would rate LogicMonitor a 10 out 10. I've used other monitoring solutions over the years, and LogicMonitor does things really well. The console may not be quite as flashy as others that I've seen, but it's perfectly functional. Having a flashy console is not necessarily the be all and end all because, often, if the console is flashy, and it distracts you from what you're looking at. Every time I've ever used LogicMonitor, it's given me everything I needed out of it. I've got no complaints about it whatsoever.
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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free LogicMonitor Report and get advice and tips from experienced pros
sharing their opinions.
Updated: July 2026
Product Categories
IT Infrastructure Monitoring Application Performance Monitoring (APM) and Observability Network Monitoring Software Container Monitoring Cloud Monitoring Software AIOpsPopular Comparisons
Datadog
Zabbix
Dynatrace
Splunk AppDynamics
New Relic
SolarWinds NPM
Splunk Observability Cloud
IBM Turbonomic
NinjaOne
PRTG Network Monitor
Nagios XI
WhatsUp Gold
Grafana
Elastic Observability
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?



















