LogicMonitor Reviews

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.

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.

We've been using LogicMonitor for about a year and a half.

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.

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.

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.

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.

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.

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.

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.

In terms of pricing, I would rate LogicMonitor four out of five.

We did look at different options before choosing LogicMonitor, but I'd rather not say which ones.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

I've been using LogicMonitor for nearly 18 months.

We have not had an issue since we installed the solution, at all. It has been rock-solid.

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.

We've had excellent support, both tech support and account support.

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.

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.

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.

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.

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.

Sparx Solutions is a managed service provider. We primarily use the LogicMonitor platform for monitoring, maintenance, and management of our managed services and customers' infrastructure. In terms of management, it is more around monitoring and alerting. That is essentially the core component that we use it for. However, there are other features integrated into the platform that we get value out of.

We have baked LogicMonitor into our core services, in terms of MSP and managed service offerings. We use this tool to fundamentally provide network monitoring services to our customers. It is definitely a great tool and something that we use daily.

We have multiple users using these solutions. They are technicians and engineers. Essentially, they use this platform for different purposes. So, a support resource will be able to use it to identify alarms and when there is a new ticket that needs to be created to remediate a problem. Engineers may use this platform to obtain valuable insight into the systems that they are working on, e.g., if they would like to understand whether a device has a really high CPU before they plan a change, etc. There are different use cases for using the platform. One of the main use cases is having users use the platform to provide support services.

We deploy probes, which are hosted by us. These connect back to the LogicMonitor platform in the cloud.

In terms of alerting, there is already a prebuilt alert threshold for a lot of the metrics. It is quite smart out-of-the-box. You may even identify issues which were not visible to you before by just introducing monitoring from the LogicMonitor platform. 

To a certain extent, there are mapping functionalities within the platform. A lot of these sorts of features, which are desired, come straight out-of-the-box. By being able to drop a Collector in the environment, you can quickly identify a lot of key information. Maybe some information, which you didn't previously have visibility to, becomes very visible. That sort of insight is very good information and allows us to be able to provide more value to our customers by having a better understanding out-of-the-box.

There are a multitude of features that we use. Obviously, with the core foundational features, which are monitoring, we use different sorts of data sources to monitor. For example, SNMP would be an example of syslog monitoring. Primarily, that is used for network devices in our use case. When we monitor network devices for our customers, it is all performed with the compute being within the LogicMonitor platform and architecture. The list goes on. 

There are a multitude of different vendors, products, and hardware that it can perform monitoring on. It is not limited to that either. There is actually a vast range of different services that can be monitored, e.g., cloud services and services that use APIs. It is quite customizable and flexible in terms of monitoring capabilities. In addition to what is out-of-the-box, there are also capabilities to configure custom monitoring which can use many different data sources. From that perspective, it is quite broad in its scope of monitoring. 

In terms of the services that we like to use, there is the built-in AIOps, which is quite a good service. It analyzes metrics of data over time and can identify anomalies based on AIs, sort of an intelligence in the back-end. This is a really good service. Some of the services can add on components to the platform, like cloud monitoring, so you can monitor your cloud environments, such as AWS, Azure, and Google Cloud Platform.

There are quite a vast amount of different features that you can use within the platform. Some of them are additional costs and some of them come out-of-the-box. Another example of something, which has recently been included in the core component, would be a service called LM Config. Essentially, this service allows us to collect network devices, run configuration files, and take backups of our customers' infrastructure centrally from one system. Rather than needing individual systems at every customer site, because this is a cloud delivered sort of architecture, we can take backups of our customers' infrastructure through the platform, which is a really great convenience and sort of efficient way of doing so. This is actually an automated process, so you can schedule it to occur as frequently as you would like.

LogicMonitor enables us to modernize legacy tooling and consolidate monitoring tools in our customers' stacks. It has a nice user interface. It is very straightforward in terms of usability and utility. 

A single pane of glass is always preferred over distributed monitoring or other management platforms. In the past, you would need to have multiple different technologies performing different functions. For example, backups would usually be under another tool. Therefore, LogicMonitor was a great tool for us when we found that it had integrated backups using LM Config. That has reduced the time of being able to provide value to a customer. Being a single pane of glass, a lot of your metrics and alerts can all be grabbed from the tool. For a managed service provider, like us, it creates a lot more efficiencies within our operations. Our users only need to learn one tool, as opposed to learning multiple tools.

We believe that the dashboards are one of the most powerful functionalities within the LogicMonitor platform, as they are quite close to real-time, dynamic, and update quite frequently. Also, they give you a glimpse into the environment without having to run reports, etc. So, the dashboards are definitely a very powerful way of obtaining information and insights from any environment quickly. There are obviously environments where custom dashboards are required. However, a lot of time, the default dashboards provide enough information to get you going and give you that visibility instantly. Monitoring is overtime, but the earlier that you onboard and get the monitoring going, the faster the dashboard starts to populate with data. In that instance, you will be able to see data as it happens through the network or systems that you are monitoring.

Its templated dashboards are quite comprehensive out-of-the-box. For a lot of users out there, the out-of-the-box dashboards and monitoring will suffice. They are definitely comprehensive. Obviously, every environment is different, so you will need to tweak it where suitable. Overall, it's a pretty straightforward onboarding process. Assuming that you have all the right information required, if you want to monitor certain systems, then you may need passwords and configuration setup. Assuming that all these things are complete, then the onboarding process is pretty straightforward and streamlined.

One of LogicMonitor's benefits and strongest elements is that it is very extensible. It allows you to configure a lot of customizations, which are sometimes limited in other platforms. However, we found in our experience with LogicMonitor that it is quite extensible. The functionality is quite comprehensive in terms of customization. You can get very detailed into what you would like to monitor, whether it is using an out-of-the-box data source or a custom data source. You can then create custom dashboard elements so you can exhibit that data in a dashboard.

There have been some new features that have been released recently in the last few months, one of them being LM Logs. This feature uses syslog and SNMP to correlate data. So, if there is an alarm that is identified on a device, the LM Logs component will actually correlate the received log messages from the device and give the resource, or whoever is trying to remediate, insight. Instead of having to log into the device and check the logs manually, the LM Logs feature provides all that within the platform. This definitely decreases the amount of time it takes to resolve, as some of the steps that you would normally do are actually provided within the platform. So, we would definitely like to explore more of the product's feature sets.

We use the solution's AIOps functionality. We have made quite good use of it. It is something that we use daily. In terms of being able to predict anomalies or alert on anomalies within the environment, those prompt us to perform additional investigation. I would assess AIOps as being highly-effective for helping to detect warning signs that precede issues. Some of the monitoring that is provided out-of-the-box provides visibility, even in terms of metrics that you would not normally monitor or may not even know that could be monitored. From that perspective, having a broader scope of monitoring out-of-the-box gives you insight. In terms of AIOps, if we receive alarms where there have been multiple anomalies occurring within a certain time period, then that would prompt us to proactively investigate an issue prior to it actually occurring. From the visibility perspective of having monitoring out-of-the-box, it has been highly-effective and quite insightful.

We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset.

We started using LogicMonitor between the end of 2019 to early 2020. It has been almost two years, I would say.

In the time that we have been using it, we have never had a major outage that has affected our ability to alarm or report. From that perspective, it is quite good in terms of stability. There are a lot of new features being released, and we have never had an experience where a major outage was caused by the introduction of a new feature. We are quite happy with its stability.

It is all sort of invisible to us as updates roll in. I think the most recent one coming out is version 155, which is about to be released tonight. At the moment, I would imagine we are using 154.

LogicMonitor is making many updates quite frequently and their monitoring capabilities are growing very rapidly. With every update, I see that gets released, there are new integrations to different systems as well as new monitoring configured. Being a cloud delivered platform, all the updates are performed by LogicMonitor. So, using the system, this is quite invisible to us. 

New updates roll out quite frequently. I believe that it is quite comprehensive in terms of its scope and capability to monitor many platforms, including on-prem platforms/devices, cloud infrastructure, etc. So, I think that it is quite good in its update releases. I'm quite happy with the amount of updates that are occurring. I keep up-to-date with all the different monitoring requirements.

I definitely think that having ongoing maintenance is required. That is not specific to LogicMonitor, but for any IT monitoring platform. I think it is always recommended to have ongoing maintenance performed. In terms of patches, everything is all delivered via SaaS. So, a lot of the patches and new features are actually done by the LogicMonitor team. 

It is scalable out-of-the-box, which is good. The way that it is configured, out-of-the-box, you get a lot of good feature sets. There is minimal configuration required to get up and running. Obviously, the larger the environment, the more effort that is required. In terms of out-of-the-box feature sets, it is pretty comprehensive. You can essentially turn it on, tweak a few metrics, and be on your way. So, there is obviously some work to do. With this particular platform, it has been the most efficient that we have used at this stage. 

The scalability element of LogicMonitor is sort of built into the platform. From the very beginning, the platform is designed to be scalable, in terms of its automatic identification of different vendors. Once it identifies the vendor or system that it is trying to monitor, it knows which data sources to apply to that device. This is all an automatic process. If you have the right information configured on the device, then it will automatically identify what type of device it is and the metrics are for monitoring. Also, it has its own alerting preconfigured. For some of the metrics that are common across multiple vendors or systems, it actually knows by default what the expected result of the monitoring is. This obviously differs between different devices. However, for common elements that are considered successful or failures in terms of monitoring, these are pre-built into the system. 

Additionally, there are predefined remediation steps in some of the data sources. Not only does it alert you on the failure of some monitoring elements, but in some cases, it also provides you with some recommended remediation steps to follow to resolve the problem. That goes outside of the monitoring. From that perspective, it is quite insightful, especially to a resource who is using the tool. They may be able to obtain some insight from the platform, which may assist in resolving the issue.

Once the solution is structured in a way that your requirements desire it to be, then the onboarding process is quite straightforward. It works on a very scalable inheritance model. So, you can have a top level configuration that pushes down all the way to the bottom, and you can override values at the bottom level. In terms of scalability, and onboarding specifically, if your rules are already configured in such a way that it allows you to just onboard, then no additional work is required, other than creating the customer, branch, or whatever you are monitoring in terms of a container and just adding devices. Once the device is added to the system, the inheritance model will actually push down different metrics and alerts based on automatic identification of vendor, equipment, and systems. So, everything is very automated. That is one of the key strengths of the platform: It is very dynamic and scalable out-of-the-box.

It reduces the time for onboarding customers. We have experienced that firsthand. It actually creates efficiencies when onboarding. The way it does that is by using automation, a sort of inheritance, and a sort of scalable architecture out-of-the-box.

The tech support has been great. For any query that I have, I have been able to talk to a resource quite quickly. In terms of their turnaround time, they are always available during the times that we have needed them. They have shown that they can go above and beyond in terms of their supportability with the platform. I am definitely very happy with the level of support being provided.

There is a lot of information in terms of the learning platforms that LogicMonitor provides. They give you sufficient information to build dashboards and other customizations within the platform. So, the information is readily available, if anyone wishes to pursue that.

We have discussions with the vendor quite frequently every couple of weeks. So, we are always in touch.

In the past, we needed to spend a lot of time and effort tweaking and adjusting metrics per customer, though not with LogicMonitor, which is not efficient. With LogicMonitor, we found that the overall time to onboard a customer into monitoring, providing useful and valuable input to the customer based on their environment, is quite quick. So, the time to onboard and provide insight is quite quick. This is a good example of a way that we found the solution to be quite efficient.

We did previously use another solution. The reason why we switched is LogicMonitor has more advanced extensibility in terms of custom configuration. That was one of the drivers. Another driver why we switched was our user experience with the account teams. We found that with LogicMonitor, from the moment that we sort of met over the phone or virtually, we always had a good experience and felt that we were being looked after. That definitely increased our drive to sort of move away from our previous solution. Additionally, there were integrated functionalities, like LM Config, that take configuration backups from network devices and systems. LM Config was a feature that we wanted to consolidate into one platform.

There was planning that was required before the rollout of this product. That planning is to ensure that the product aligns with our monitoring requirements. In terms of planning, there will always be planning before you introduce any sort of tool like this, i.e., an IT monitoring tool, in terms of how you would like to structure the platform. This foundational planning is ultimately what affects your capability to create efficiencies in alerting and problem identification. 

There is obviously consideration around your alerting. I think alerting is probably one of the key features that any digital IT provider would use, whether it is an MSP or if you are monitoring your own infrastructure. One of the key things that you want out of a platform like this is its ability to promptly alert when there is an issue in your environment, then ultimately triggering a chain of events that would occur after that. So, in terms of planning, you will need to sort of assess your current monitoring and see how you would structure the architecture of the alerting. A lot of it comes down to that. 

It is quite flexible in that sense that no matter what sort of company you are, whether you are an MSP or internal IT looking to deploy a new product in your environment, it comes down to what your requirements are. So, there is not a set timeframe because there are a lot of factors involved, like understanding what your alert rules look like and the classification of the infrastructure. You might have some critical infrastructure, and you will need to consider that and put it in its own group. There are many different methods of doing this, but it all comes down to the requirements.

In terms of configuring and rolling out the platform, once the planning component of it was complete, the actual rollout was quite straightforward as it aligns to the structure that we defined prior.

We deployed LogicMonitor in-house.

There are a lot of different components involved in rolling it out. We would have to configure the platform first with all the planning prerequisites. Once that was all done, then we would have to go and install the Collector applications on our probes and essentially onboard each device individually. 

There is an automatic sort of device for onboarding that you can frequently run to identify any new infrastructure in the environment and flag it. Once this is in, the ability to identify new infrastructure is very straightforward and quick. In terms of how long it takes to actually roll it out to our entire customer base, it takes about a month's time. This includes planning, communications, and multiple other factors as well. 

The quicker that we can onboard, the quicker that we are able to collect metrics to give us insight. Then, we are able to provide value to the customer and insights on their environment more quickly.

The return on investment is having the capability to offer more advanced features as part of our service offering. By having that capability, we have an advantage because we can offer different capabilities and functionalities within a single platform.

It has quite an advanced feature set, especially with its functionality like AIOps. It definitely gives us an edge and advantage to be able to provide these services to our customers and allow our customers to utilize our infrastructure for their own monitoring or reporting purposes. I definitely think that the functionalities are quite good and advanced. It definitely gives us that edge. From the perspective of the services that we can provide, we are able to offer more services to our customers by utilizing the features of the LogicMonitor platform.

From the feedback that we have received from our customers, they are quite happy with the tools that we have been able to offer, things like dashboards and centralized backups. From that perspective, I think that our customers are happy, having provided their feedback on LogicMonitor.

In certain circumstances, the AIOps functionality helps prevent outages. It really comes down to the circumstance. There are multiple factors involved. Being able to promptly receive information that could be anomalous, from the AIOps feature, allows us to proactively investigate alarms prior to any outages occurring, and this is sort of down to circumstance. From this perspective, time is being saved in respect to resolving an issue.

LogicMonitor has given us visibility into issues we didn’t even know existed. It comes down to the consolidation of data and being able to have dynamic dashboards and effective alert rules. It can provide information where something unrelated to the device may cause an alarm to be produced. It might not be directly related to the device that you are concerned with. However, it could prompt an investigation outside the scope of that device which may help us identify an issue downstream or upstream.

An example where LogicMonitor has provided visibility into an issue is it could highlight if there is a configuration issue. We predominantly monitor networks with this platform. Any example of networks using LogicMonitor's mapping feature can give us visibility into what physical links are connected between devices. When there is an alarm in the window where you look at the mappings, it actually identifies the alarm on the device. So, you may be able to identify misconfigurations. 

Another example is using the LM Config feature. If there has been a change to a running configuration file, it actually flags this change. So, if you have a change management policy that needs to be adhered to, and somebody has made a change without authorization, you can actually flag this information. Even though it may not cause an immediate outage or issue to be triggered, being able to have the visibility that somebody has made a change can prompt an investigation that could prevent an issue which may occur later.

LogicMonitor saves time in terms of its ability to proxy a connection through a device. For example, if you are troubleshooting a device, which you may want to connect to, you can proxy this connection through the platform. As a support resource, I don't need to use multiple platforms to connect to a device to further investigate the issue. It is all consolidated. From that perspective, it saves time because a resource now only needs to use one platform.

It saves time because the resource does not need to leave the platform. Depending on how many activities or issues that you are working on, that time could vary. From a consolidation perspective, everything is accessible within the platform. I definitely see the value in a resource not having to actually leave the platform to remediate an issue that is present.

The solution reduces mean time to repair. An example of this is when the resource no longer needs to look at logs manually on a device. It could actually be integrated into the platform. By having those logs right in front of you, it is very quick to make assumptions or conclusions about issues. Whereas, in the past, you might have needed to log into the device independently and do your own review. 

Another example of reducing mean time to repair is the ability to connect to the device directly from the platform. Being a cloud platform, you can perform this connection wherever you are. So, if you are working from home, you don't need to VPN into an office, then connect to some on-premises equipment. Being cloud delivered, you can configure SSO for authentication to authorize against your domain. This makes the authentication and login processes quite easy, especially now during this time of COVID as a lot of people are working from home. It has the flexibility to connect wherever you are as well as the ability to connect to a device within the platform.

LogicMonitor is a premium solution and offers a premium feature set. In terms of what it offers, it is more about value. 

The features were very valuable to us because we could consolidate them into one platform and have a good user experience with the platform, our accounts, and the support team. That was the key driver for us. That was what we were looking for. We looked for a comprehensive solution that could provide advanced features all in one platform, and LogicMonitor was the solution that we chose. It definitely has a premium price. However, you are getting what you pay for in a very effective way. That was important in our decision-making.

There are add-ons. One of the add-ons, LM Config, has now been integrated as part of the standard fee. Also, there are different tiers which offer different feature sets.

I evaluated multiple different solutions. Some of the solutions that we looked at were NinjaRMM, Auvik monitoring, and Kaseya. There were multiple different platforms that I personally trialed. Not that they didn't have good offerings, it is just that the LogicMonitor platform was comprehensive in its feature set. We found, with LogicMonitor, that most of the features we desired were actually consolidated into a single platform. This made it really easy to onboard and offboard as well as apply new features or monitoring to our userbase.

We are very selective about the vendors that we use, in terms of our products that we provide.

So far, the introduction of cloud monitoring with LogicMonitor is testament to their ability to stay up-to-date with different sorts of monitoring and future IT requirements. I have seen progress on this front from LogicMonitor. Ever since we started using the LogicMonitor platform, there have been many updates that have introduced new functionality that seemed to be catered for the future of IT.

There are still some features that we haven't fully integrated that we would like to do. At the moment, we are currently reviewing what the value of these tools will bring to our customers.

We don't use Dynamic Thresholds at this stage. Dynamic Thresholds are something that we would like to review as we proceed with the product. It comes down to use cases. Depending on what you are monitoring, it may make sense. However, in some cases, it doesn't make sense, which is a factor to consider.

In terms of visibility, LogicMonitor provides a wide variety of information. The more devices that you are monitoring, the more information that you can cross correlate. Especially using other features, LM Logs is definitely something I can see value in. From a support perspective, it decreases the amount of time it takes to identify or resolve a problem. So, you receive an alarm, then when the resource looks into the alarm, the LM Logs capability actually allows you to see the log messages at the time of the alarm. Instead of the resource having to manually connect to the device and check the log file, this information is correlated for you within the platform. So, this is not a feature that we use today. I have seen a demo and can definitely say that there is a lot of value from this particular feature. I believe that a lot of providers would see the value in it.

At this stage, we are quite happy with the level of functionality that we have with this tool.

I would definitely recommend trying LogicMonitor for yourself. I believe you will quickly see the value in the different feature sets that are provided and its simplicity, in terms of the user interface. If you have used another platform for IT monitoring before, this is very good in terms of the user interface. It definitely has a great user experience when you are using the platform. It is very customizable in terms of the color schemes that you can use. Definitely give it a go and you will see the value, just as I have.

If you feel like you can't find the tool that meets your requirements, it is definitely out there. Personally, we were looking for a new tool for quite a significant amount of time. We looked at many tools. Coincidentally, towards the end of that sort of campaign of trying to find a new solution, I actually received a call from a LogicMonitor resource. It was quite coincidental. It's actually funny how it happened. So, one of the lessons I learned is there are many platforms out there and you just have to keep looking. Eventually, you will come across something like we did, like LogicMonitor, that will meet your requirements. 

We have had a fantastic experience so far. It is a fantastic product. It is definitely worth looking at. It has definitely delivered on our requirements. I will rate it as a solid nine out of 10.

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.

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.

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.

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.

I just started using LogicMonitor.

The stability is fine.

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.

The support is very good. We are happy with the kind of attention that we get from our customer service manager (CSM). 

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.

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.

There is no ROI. We are mitigating outages for our customers, but not really saving time.

LogicMonitor is competitively priced at the same level as other vendors, like Datadog.

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.

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). 

It is to monitor our customer’s infrastructures. We provide the service as part of our managed service offerings. We monitor our customer networks and infrastructures for things, like availability, vital statistics, and the various services, that they have running in their environments. We provide a NOC and Service Desk that actually responds to alerts that come up and use the tool to allow them to be proactive in looking after their environments.

It is clean and clear compared to other products that we have used. This has made it easier to get to the root cause of a problem, because it's easier to see (through the visualization) where the problems lie.

I have worked on several data sources where I've either customized what's there already or created additional ones that don't exist. Also, LogicMonitor have been very flexible in terms of providing resources to assist with building custom data sources. If we have a requirement, we can approach LogicMonitor and they will assist us in getting the data that we are after.

It has improved our control over the environments that we manage. With a lot of products, you can just pop a device and get a metric out the system. With the LogicMonitor, you can do a lot of manipulation through scripting, then calculate the results that you're getting. It makes you more efficient and able to get the data in the particular format that you want.

You can do a lot of tuning of alerting, from the device group down to the data source and individual instances of those data sources. This is very flexible. We have many customers who have their own requirements of what they want us to do alerts on, so I was asked to be more flexible with our monitoring and alerting. I now can provide more bespoke, customized services for them.

LogicMonitor alerts us if the cloud loses contact with the on-prem collectors and we have found this advantageous. We have email alerting and an integration with our ticketing system. In some instances, we have automated text messages and phone calls for the more critical services. When our collectors do happen to go down, that's a P1 situation because we've lost complete sight of the customer's environment.

We have started using Artificial Intelligence for IT Operations (AIOps) capabilities more for the anomaly detection and for troubleshooting. The root cause analysis is something which we're testing now to see how it will work for us. These features will take a lot of noise away from the alerts when they come in.

One thing which has really helped is the integration that we have between LogicMonitor and our ticketing system: The ability to be able to log and update the ticket. We do have additional functionality to this integration as well, where if we have a number of alerts for a particular device in a period of time, then it will then create a problem ticket in the ticketing system and attach the associated incident tickets. All of these pieces help dramatically in terms of keeping everything central in the ticket. We know when things have gone down or cleared. It's not repeatedly opening and creating tickets for every single failed poll. In terms of the whole ticket management process, it's helped immensely with that.

Most of the products that we work with it does monitor out-of-the-box because we work with a lot of the big vendors, like Microsoft, Cisco, Palo Alto, Citrix, etc. They are very good at having the data sources readily available for those.

The most valuable feature is the visualization of the data that it is collecting. I have used many products in the past and they tend to roll up the data. So, if you're looking at data over long periods of time, they start averaging the data, which can skew the figures that you're looking at. With LogicMonitor, they have the raw data there for two years, if you are an enterprise customer. If you are looking at that long duration of data, you're seeing exactly what happened during that time.

I have probably two types of favorite dashboards:

1. Dashboards that give a general overview of our whole environment and a complete sort of NOC-level view that can be drilled into if there isn't an alert.
2. I like the dashboards that can be very granular into a particular service or piece of equipment. For example, if you were looking at a dashboard just related to Citrix, you can have a huge amount of detail on one page. Taking all the metrics into visual graphs, pie charts and big number widgets which makes it a lot easier than having to work your way around the devices that you are monitoring to bring the data that you're interested in altogether.

We are quite a large networking company. One of the features that we like with LogicMonitor that they have out-of-the-box is NetFlow, which is a great tool to help troubleshoot something. This has improved how we can provide a service to our customers.

The anomaly detection is a very good tool because you can compare the statistics that you're looking at against a week or month ago to see if it's something that's truly out to the norm or not. The visualizations that I get are very powerful. These capabilities enable us to be more proactive in resolving issues and preventing problems. If you are managing a customer's network as you should be, you should be looking at these tools and visualizations on a general day-to-day basis to understand what is happening with the customer's network. It's very useful to use these tools to learn about what's going on and know what the norm is for those networks. Then, you can get to a point where you're tuning your alerting to be a bit more in tune with what the actual norm is for that customer.

The solution has consolidated the monitoring tools we need into one. A reason why we moved to LogicMonitor would be the additional features that are provided, like NetFlow. We would use a separate solution for that and configuration management as well. Just to have those additional items built into the product has been a really good part of the product.

The topology mapping is all based on the dynamic discovery of devices that could talk to each other. There is no real manual way that you can set up a join between two devices to say, "This is how this network is actually set up." For example, if you have a device, and you're only pinging that device for availability and not getting any real intelligent information from it, then it can't show you which devices are actually connected to it. Before the topology mapping was released, I was working with product management and did raise this issue at the time. I haven't seen it yet, but it was something that I suggested to them that they should allow customers to be able to build their own topologies, or at least to override what's being discovered, just for visualization more than anything.

I can completely understand that the old topology mapping is how the root cause analysis and the alert suppression work, which is all dependent on that as well. So I wouldn't want to override that in terms of functionality. But, in terms of a visualization on a map, it would be a big plus to be able to do that.  I have been told that this is being worked on in the background.

Just over two years.

It is a very solid platform. I haven't noticed any real outages from my point of view. I've seen when LogicMonitor emails out to say, "There is currently a problem in these particular regions," but I don't think I've actually seen myself experiencing those issues. They are very good at communicating out what's going on. In terms of actual availability, I've never really seen an outage on the platform at all.

Because it's a SaaS offering in terms of scalability, onboarding customers is more on the LogicMonitor side. They are the ones who need to have the capacity to onboard these customers, and I've never had an issue so far. From my understanding, they are growing month on month in terms of their infrastructure.

There are definitely limitations with the sizing of the devices that LogicMonitor provides. It's based on the number of instances in general. A lot of the time, I have customers on a large collector who say something like, "It needs to be a particular spec for 10,000 instances." On the customer sites, I have the same spec device with 50,000 to 60,000 instances, and it's working perfectly fine. So in terms of the actual scalability, there are restrictions, but I think LogicMonitor has been quite conservative in terms of what they've published and say that they're actually capable of. In my experience, I've been able to push those boundaries a fair amount.

From our company's point of view, there are probably about 50 to 55 users who access LogicMonitor to use it in one way or another. Then, we provide logons for our customers as well, if they want to see their own environment. Service desk and NOC analysts are the main people who use the platform, then we have our service management team who log on there to get information for monthly reports or outage queries.

We do use quite a lot of the platform. There is room for growth, but it's just one step at a time while we're getting used to the platform and as and when we have a requirement for using additional features.

The great thing about LogicMonitor is that you have the inbuilt chat within the platform. You're getting through to people that know the product and not getting through to people who are just logging tickets. Most of the time, you're either getting an answer straight away to your problem or they try their very best before they actually have to escalate it somewhere else. I seriously can't fault their technical support.

LogicMonitor replaced our other monitoring solution, ScienceLogic, which was very similar to this platform in terms of multitenancy and customisation. The previous platform charged a premium cost for the additional features that come with LogicMonitor. To have the additional pieces native in this product is a huge advantage.

We evaluated about 6 products before moving to LogicMonitor.  The decision to move was based on features, ease of use and commercial elements.

Most products are very good at onboarding devices onto the platform. LogicMonitor is no different either. Once it has some credentials that it can use, it will automatically discover the metrics that it wants to apply against them. They are very good at setting some good baseline thresholds, so they give you a good starting point with those data sources to say what you should be alerting on and at what levels. Because of that, it does reduce the time down it takes to onboard a customer.

For the average onboarding time, you have several factors that can contribute to it. You must make sure that you have the right credentials to access devices and the devices themselves are accepting access to them. The LogicMonitor process has improved how long it takes to onboard a customer, especially with the time it takes to provision a collector. A collector takes minimal time at all. Whereas with my previous vendor, towards the end of our relationship, it was taking a long time to get the collectors up and running. A lot of the time, you had to get support involved because it wouldn't happen properly.

We used the professional services of LogicMonitor.  They were amazing and extremely efficient.  They had experience of migrating from our previous platform and were able to automate as much as possible.

I think that we have seen ROI. We moved to LogicMonitor because of the types of devices that we are monitoring. It’s better for us now with the efficiencies that we're getting from the platform. It's definitely benefiting us. It's more than just having a tool. It's something we can use day in, day out, giving us good insights to what is happening.

It has saved time because you have the information that you need in one place. In turn, the productivity is better because of it.

The licensing side of things with LogicMonitor, is quite simple. It is one license per device. LMCloud and LMConfig is slightly different but still a simple model.

The standard license it's very straightforward versus my previous vendor where there was like six different tiers of licensing on the devices that you're monitoring based on the number of metrics they were getting per device.

From what I understand, they are bringing out a number of new features, where there will be a different licensing model for those features. So, it will be interesting to see how that comes about and affects things. However, today it hasn't been too bad. It has been a very straightforward licensing model.

Take your time with it. A lot of the delays that we had were around customers not giving us access to their networks to get the collectors installed. We had a very strict timeline that we had to follow when we were doing the migration because our contract was ending with our previous vendor. We had to get everything all up based on a particular date, and it was down to the wire. We were very close to actually not monitoring a couple of customers because they just weren't giving us the access we needed. So, my advice is if you're onboarding the product and you are dealing with many customers, then just make sure you give yourself enough time.

The reporting capabilities are within average. They are good for certain point-in-time reports that you might need. However, most reporting that we do is service reports that we provide our customers at the start or end of the month. Because we try and look at various data from multiple systems in one report, we use an external product to get the data from the LogicMonitor API that we want to put into one report. With the reporting in LogicMonitor, you would have to run many reports to try and get all of those pieces of data. Therefore, we use a third-party product so we can just run one report, have it all automated, and take away the administrative headache. There is nothing wrong with the reporting. It's just for our requirements: We need the data to come from LogicMonitor and other platforms as well.

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.

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.

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.

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.

We've used the solution for over five years now.

I have never had an issue where the stability of the portal was affected.

The solution offers very good performance and can scale easily and flexibly. 

I'd advise new users to set it up the way they want and make sure they update/import everything they can.

We are a managed service provider, so we have a wide range of deployments. LogicMonitor, as a whole and software as a service solution, is deployed with collectors on-premise, which also ties directly into cloud providers.

We primarily monitor Citrix environments for customers. That varies from the delivery side, so network Citrix ADCs as well as virtual desktops and the supporting infrastructure around that. That's probably our primary use case.

While we do some NetFlow capture for other managed service clients, the primary use case would be Citrix monitoring.

LogicMonitor really improved our workflow as a company. Previously, we had been using a combination of about four or five tools. We were able to consolidate those all into LogicMonitor, which significantly improved our response time to new customers and onboarding time for new employees.

We can create granular alerting for devices. Then, since we are a managed service provider, we can have very granular alerting, not only for our own purposes, but where customers would like to be alerted directly on specific issues. It is very easy to build escalation chains that include the customer as well as our own team.

LogicMonitor's AIOps give us a great view of performance over time and potential changes in performance.

We have been able to tune LogicMonitor very granularly and eliminated most of our false positives. Any monitoring platform is going to give you false positives to some degree, but we have definitely reduced our false positives with LogicMonitor by at least a half.

The dashboarding is very useful. Being able to create custom data sources is one of its biggest features which allows quick time to market with new features. If one of our vendors changes their data format or metrics that we should be monitoring, then we can quickly adjust to any changes in the environment in order to get a great user experience for our customers.

We have created custom dashboards for our customers to give them a single pane of glass view as far as what their environment looks like in relation to their Citrix environment or VMware Hypervisor environment. LogicMonitor is a combination of things that they have pre-built. Especially along the VMware infrastructure, they have some great dashboards canned and ready to go. On the Citrix side, we have developed a lot of our own dashboards for customer use. We have gotten great feedback from those, as they're very easy to throw together and provide a lot of value to our customers.

We use custom data sources extensively. It's one of the greatest features of LogicMonitor, as a product. We can have very granular control over our data sources. Customizable data sources are one of the primary draws to LogicMonitor, and we do use them extensively. Developing new LogicModules is very simple. We primarily use PowerShell, but there are also a myriad of other options depending on what your target operating system is.

LogicMonitor alerts us very quickly if one of their collectors loses connectivity with the cloud. Occasionally, we will get alerts for customers where we don't have extensive monitoring in place, and they may not be aware that their site is down or that there are other issues with their environments. We have had occasions where the alerts that we get from LogicMonitor that the collectors are down might be our first indication where a customer is having an issue.

At this time, we are using AIOps for dynamic thresholds and anomaly detection. For anomaly detection, we found it quite helpful because it will give us an idea of when there is an anomaly in the environment. For example, if you have a backup job that normally would run, but it isn't running or if there is a bulk data transfer that wouldn't normally occur at a particular time, we can have it alert one way or another. That is a great feature, as far as LogicMonitor's AIOps toolkit.

We have found LogicMonitor's reporting capabilities to be somewhat lacking. That is one of the only areas that we really thought was not as strong as it could be. One of the great things is the dashboard functionality, which we were able use to work around the reporting functionality. Instead of having a canned report that gets emailed to our customers, they have a live dashboard that they can log into and view the things we would normally include in a report. They can have a live look, where they can really drill into the data and see what is there.

LogicMonitor's reporting capabilities definitely could use an improvement. We have made do with the dashboarding and done what we can to make that work for our customers. However, there are definitely customers who would like a PDF or some kind of report along those lines, where we have been utilizing other tools to provide them. The out-of-the-box LogicMonitor reporting is the only thing that we have been less than impressed with.

We have been using LogicMonitor for about four years.

LogicMonitor's stability has been very good for us. We have not experienced any major outages or issues with LogicMonitor as a product in the several years that we've been using it.

We have a team of a couple of people who handle the implementation and deployment of LogicMonitor. We have a larger team who handles the day-to-day support. One of the great features of a LogicMonitor being a software as a service product is we don't have to monitor or manage the tool itself. The collectors update automatically. We handle the operating system running the collector within our normal toolset. Therefore, it gets Windows updates and does all these things on its own or through that toolset. There is very little time that has to be spent managing the tool itself. We are really just managing our systems in the tool. 

Scalability is actually one of the reasons that we went to LogicMonitor from our own internal tool sets. The scalability is as big as you want to go. I've seen other customers that have thousands of endpoints in there without any issue. We certainly have not run into any scalability issues in our environments.

We have a variety of users who interact with LogicMonitor on a daily basis. We have our managed services team who work directly with the customers and are in there on a day-to-day basis doing remediation of issues as they arise. We also have our implementation group who take care of onboarding new customers, working with them on any custom data sources or custom monitoring needs that they might have. Then, our customers are able to log and see their own environment along with the dashboards and things that we built for them. It really has been a great tool for our team and customers to be able to see all of that. 

The role-based access control that LogicMonitor provides is very robust. We are able to provide single sign-on for our users as well as multi-factor authentication for our customers. Therefore, the role-based access control and authentication components of the LogicMonitor product are excellent.

Our use of LogicMonitor is constantly increasing as we roll our managed customers into the platform. We definitely plan to increase our managed services, and directly as a result, increase our utilization of LogicMonitor.

We have only had to engage with technical support on a handful of occasions over the last four years. Thankfully, the product runs very well; we've had very few issues with it. On the couple of occasions that we have had to engage technical support, they have been very quick with first-call resolution, and we've been very happy with our experience during that process.

LogicMonitor provides very wide support for just about any device that you can use in an enterprise environment. We've used it for VMware, XenServer, and Hyper-V on the hypervisor side. On the storage side, we have people using NetApp and Dell EMC. On the networking, we are using Cisco. We also have some customers running UniFi gear and Juniper. There are just a massive variety of devices that it can monitor out-of-the-box.

LogicMonitor was a great move for us in terms of consolidating our monitoring tools. We previously used a combination of paid and open source tools to monitor our customer environments. Being able to consolidate to LogicMonitor has allowed us to save significant time in server management when managing the tool. We have also seen a lot better onboarding times for our employees coming to the environment. It has been a great gain all-around.

The customer onboarding time was cut down by a half to maybe three-quarters. As far as the employee onboarding time, they only have to learn one tool instead of having to learn multiple tools. We have consolidated our collector or data source development from probably three languages down to just PowerShell. That has been a huge gain. It's much easier to find resources that can learn or know PowerShell, so that's been fantastic.

LogicMonitor replaced Observium, Zabbix, Nagios, and SolarWinds.

The initial setup with LogicMonitor was very straightforward. The team at LogicMonitor worked with us to deploy our first collector, then walked us through how to create groups and assign properties to the groups or devices. Most devices have very good metrics out-of-the-box, as the data sources that LogicMonitor provides are excellent for the vast majority of devices. Where we have had to create our own data sources has been with our managed services around more complex data sets, not a specific device.

In our organization, deploying to our internal systems took probably six hours. It was very easy.

We did the initial implementation with the LogicMonitor team. They had a very straightforward strategy as far as getting it deployed. It was very easy to get our devices added in there. As we have moved forward, we have certainly learned different tips and tricks as far as how we organize devices into categories or groups in order to effectively monitor devices with minimal user interaction.

The return on investment with LogicMonitor has been excellent. We have seen a great reduction in the number of hours spent managing the tool as well as the ability to monitor a wide variety of services and systems without significant investment, in terms of time for developing custom modules or having to dissect a tool to figure out exactly what we need to do to add the functionality that we're looking for. On top of that, being able to onboard our own employees in a much faster method with only having to learn one tool instead of having to learn four or five tools has been a gain to the net positive with our onboarding process.

Our customer onboarding process is now automated. We don't have to go in and manually create a large numbers of devices in multiple platforms. We go through the process and install the collectors at the customer site, then we have templates that we utilize to deploy LogicMonitor out to those collectors. The automation with LogicMonitor has probably saved us 20 or 30 percent in time, as far as deployment to customers goes.

As a managed services provider, the licensing model that LogicMonitor provides us is excellent. We are able to scale up and scale down as needed. The pricing is reasonable for the amount of features and support that they provide.

As a managed service provider, we have the highest level of licensing that they offer, so we don't have any extra fees. I believe there are some add-ons for some of the lower tiers of LogicMonitor service, but that's not something that we use with our agreement.

We found that the amount of time that we were spending on managing the tool or doing upgrades was significant. We found that the cost of LogicMonitor was less than the cost to maintain some of these open source products that we had running. The other side of that is there were some new features that we wanted to roll out to decrease our footprint as far as what we're monitoring. The time that we would have taken to develop or enable those modules in our toolsets would have had a higher cost than moving to this software as a service based product.

We evaluated a handful of options. The ability of LogicMonitor analysis as a managed service provider really shined. A lot of the other products didn't have a great MSP portal or their role-based access control was not really mature enough to handle multiple tenants. Therefore, LogicMonitor won out very quickly when we started to evaluate most of the players out there.

We looked at SolarWinds and a couple of other solutions.

If you are looking to implement LogicMonitor for the first time, work through their available documentation. There are a couple of certifications that they offer which are very good and give you a good foothold into the process. Then, talk with people who are currently using LogicMonitor. There is a great support community out there with people who are more than willing to help.

AIOps does provide a very useful data set. They have been continually improving it. AIOps is one of those things, which is there and we use it a bit. While the dynamic thresholding is interesting, the anomaly detection is probably more a nice to have, and not more of the primary features that we use.

We have not utilized the automated discovery and deployment. With managed services, we have to keep track of how we charge customers. Generally, we have a specific list of devices that we're going to monitor, so we don't use the discovery features on LogicMonitor.

As far as monitoring platforms go, I have worked with a wide variety. I would give LogicMonitor a 10 out of 10.