LogicMonitor Reviews

We installed LogicMonitor as a SaaS-based solution, and we have an agentless approach. We are monitoring the overall interface and not just the network devices. I am looking after the network devices only.

LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure. They also have a great notification system. If something goes wrong, you'll be automatically notified. LogicMonitor also integrates with ServiceNow, so you can easily get alerts in those systems.

Another thing I like about LogicMonitor is their dependency metrics. This means that if one device goes down, you won't get alerts for other devices that depend on it. This helps you to quickly identify and resolve problems.

Overall, I think LogicMonitor has a lot of great features. However, I do have some concerns about the deployment process. It's not as straightforward as it could be. Additionally, some of the workflow automation features require scripting knowledge, which can be a barrier for some users.

LogicMonitor has good features, but the ease of use is a little bit confusing. Additionally, we are looking for workflow automation, which is a little bit tricky for LogicMonitor. But we are still exploring more and do not have detailed training in LogicMonitor.

Moreover, the deployment process needs improvement. The thing is the deployment or whatever the standard deployment should be implemented here. That is not fine-tuning.

In my personal opinion, for workflow automation and other stuff, we have Python or scripting knowledge, and that part is very tricky. Whenever we try to call the service or the LogicMonitor team, and we open a ticket, it is chargeable.

In future releases, we would like to see a configuration backup manager. A feature that automatically backups the device configuration will help us. So, instead of going with another third-party tool, this will be good.

We have been using the product for two years.

The stability is very good. We have a SaaS-based solution and a cloud-based solution. We never experienced any kind of downtime from them. So, that part is very good.

It will be good because whatever knowledge I have with LogicMonitor is limited. I have not been able to fully explore LogicMonitor because of the scripting and other overflow automation concepts. Even courses are not available on working data. So, basically, working on the courses is available for free. I really didn't deep-dive into LogicMonitor.

In our organization, the regional office, we have two major regional offices in the USA, Kansas City, and Mumbai. So, Mumbai's count is 2,000, and Kansas City's is 4,000.

Almost all use LogicMonitor, which would include branch offices as well. So, more than 100 branch offices. We are monitoring one key code universal, and the rest of the branches have separate networks and accesses.

I would rate the scalability of this solution an eight out of ten.

The technical support is very good. But the only thing is that if you have some issues with the particular script writing and some customized reports, we have to open the case with them, and that is chargeable. That is what the subscription part is, and what the agreement between our organization and LogicMonitor is, I don’t know. Our dedicated SME handles it in the USA office.

So, if we want to open a case with them, we go to our SME, and they will try to resolve the issue. If not, then it will be chargeable. Last time, we raised some queries, and my management told me that if the query is not solved, open a case, and it will be chargeable.

I have been working with SolarWinds for more than four years. So, I can talk about SolarWinds. SolarWinds is good for network monitoring. It has reporting of topology diagrams and all this stuff that we can get over there. Also, a bandwidth analyzer is available, which is a very handy tool. There is also configuration management, which is like an add-on basis. So that is good. But with the recent incident with SolarWinds, it is no more secure. If you wanted an on-premises solution, then probably go with ManageEngine or SolarWinds. But when looking for cloud-based, we thought LogicMonitor will be good for us. We only have to check and gain some knowledge on whatever they provide, the knowledge portal or training. So, that is part training for us.

The team in the USA or the partner who implemented LogicMonitor earlier is not in the proper shape of architecture or deployment. So, it's got some issues with the network device group and servers. So, all are messed up. We decided to fine-tune the hardening of this LogicMonitor.

Personally, the way we implement it here. I feel it is not easy to use.

The solution is deployed on the cloud.

I would rate the pricing for LogicMonitor a six or seven out of ten, where one being cheap and ten being expensive. 

The thing is that some features are there, but we have, like, incompetency to add up that feature. So, the product is feature-packed. But some of the features we have to explore still.

Overall, I would rate LogicMonitor an eight out of ten.

We use the solution for network monitoring. 

LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical.

The most useful feature we've found in LogicMonitor is its ability to deploy templates automatically. It's quite smart in this regard. When we add a device, it detects the type of device and deploys the appropriate template for it.  

The tool's alerting system has been pretty good for us. We receive SMS alerts if we're not in front of our screens, which has improved our response time to potential issues. The escalation chains feature has been particularly useful in this regard. Overall, it's easy to use and simplifies our alerting process.

The tool is highly integratable. 

LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations. 

I have been using the product for more than two years. 

I rate the solution's stability a nine out of ten. 

I rate the product's scalability a ten out of ten. 

The response time for support needs to be better. They're pretty fast in responding, but there are many areas they won't cover; it often falls out of scope. While they're good at getting back to us, they're not owning the issue and assisting. 

Neutral

The tool's deployment is very simple. 

The solution is not expensive. 

We use Datadog for cloud monitoring. I rate the overall product an eight out of ten. 

We use it to monitor the performance and health of all our internal IT systems in our data center as well as our customer equipment that we have out on customer sites. We have our own stuff in our own data center, but we also have hundreds of devices out on our customer sites where we need to monitor and manage the health and performance of them.

Before we were using LogicMonitor, we didn't really have visibility on a lot of things. We went from almost nothing at all, e.g., no visibility on things, no good monitoring, and not being alerted or aware of problems when they would arise, to putting in LogicMonitor across our whole estate and customers' environments now. This has meant that we have been able to centralize that function. When something goes wrong, we can react to it quickly. We can resolve it before it impacts our customers. That is massively important.

We went from nothing to pretty much full visibility across our internal and external estates of equipment, which has been massive for us in terms of being able to resolve problems faster and provide better customer service to our customers. At the end of the day, our customers pay us to be on top of their stuff. LogicMonitor helps us do what we are supposed to do for our customers. So, it is very good from our perspective.

We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor.

We monitor stuff that is on-prem and in the cloud. It is very good comprehensively for that. It is brilliant. I could probably only count a couple of times where there has been something I have needed to monitor that hasn't had a data source or something in LogicMonitor. It is only niche products where I guess it wouldn't necessarily make financial sense for them to actually develop something for this at the moment. For example, we started using a fairly new product, which we rolled out for a lot of our customers, and noticed when we first started using it that there were a limited amount of data sources in LogicMonitor for it. Over the last couple of months, that has been developed significantly. Generally, if it doesn't do something that we want it to do, there is a chance that it will do it at some point and that process is usually quite quick. 

We are very happy with it from a future-proofing perspective. With the amount of updates that LogicMonitor pushes out, I have no concerns that LogicMonitor won't be able to keep up with them as the IT environment changes for our customers and ourselves going forward. It will be great for that.

There are a lot of valuable features. The product is probably one of the best-featured products in terms of its usability. It is brilliant. The in-depth graphs are really good for visualization. Remote access to devices through the LogicMonitor portal is really good from an ease-of-use perspective. Also, it is very secure.

LogicMonitor bought a company called Unomaly and integrated their log analytics into the LogicMonitor portal, which has been very good for us. Although we have a very big technical team, our internally facing IT team is quite small so having a product that is very easy to use is really important for us. We don't have loads of people who are experts in every individual product that we have. We have people that need to be skilled across a large number of products. So, the usability is very good for LogicMonitor.

We definitely use the Dashboards feature. We generally construct the dashboards ourselves, so we don't use the template ones that LogicMonitor provides by default, but we do use the Dashboards feature for our own dashboards. The templates are good examples of what you can do with dashboards, but they don't tend to meet a lot of our requirements, so we tend to do them from scratch.

We use the Dashboards feature for some of our service reviews and things for customers. We will present a dashboard to a customer when we do a review with them to show them graphs and stats on their solution. 

We use dynamic thresholds within the AIOps functionality. It is good because there are a lot of times when our customers have things fluctuate. This means that we are not getting alerted for stuff all the time, e.g., every time it just goes slightly over a threshold. So, the dynamic thresholds means that we're just able to react a bit more appropriately rather than just logging issues with customers when they are not really issues.

LogicMonitor has given us visibility into issues that we didn’t even know existed. It picks up on things, like failed power supplies or disks running out of space.

Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on.

I have been using it for three or four years. I used it across two different companies. So, I used it at a previous company, then I moved to my current company. We have had it in my current company for two or three years.

Stability is pretty much perfect. I don't think I have ever seen a problem with it. I don't think I have ever had an issue where I needed to roll anything back or tried to log in and it has not been available. It is pretty spot on there.

For what we have done so far, it has scaled perfectly. We are by no means one of their larger customers, 100 to 450 devices, and we have not really had any issues with scalability from that perspective. I don't know what it is like if you are monitoring tens of thousands of devices, but scalability has been perfect for us.

We probably have about 20 or 30 internal users who log into LogicMonitor and do things within the tool. They are largely hands-on technical staff, and there are probably a couple of more management or service delivery roles in there. Service delivery is customer success, doing reviews with customers to make sure they are happy. Usually, they just use the dashboards feature for that. As a service provider, the majority of our staff are technical engineers who either support customer environments, therefore looking at alerts and things within the tool, or they are using it to access customer solutions. 90% to 95% of our technical staff are using it.

It is used across our entire business. It is probably one of the tools that we centrally revolve around. It's becoming a pretty core part of our business, and we do have plans to increase our usage. 

At the moment, we have a commitment of 350 devices. We are slightly over our commitment, but I just had a quote from our account manager to increase to 450 or 500 devices. We just wanted to see a quote just to see what the volume discounts would be on each level.

It depends on the sort of customer that we win as to how many devices that we might need. For one customer, we might end up needing five devices, but for another, we might need 50. At the moment, we are looking at ramping up to 450 to 500, but that scales every time we win a customer. Over time, I suspect it will keep going up. Hopefully, it doesn't go down. If it goes down, we are losing customers. 

The technical support is brilliant. You get different types of tech support people at different companies, and LogicMonitor got it right in terms of the type of people they have and the way they operate. They have good channels for how to communicate with their support staff. Every time that I have dealt with someone from support, they have been really helpful. If you ask a question, you generally get quite a comprehensive answer. It will not only answer your question but also provide information on how they came to that conclusion. So, next time, if you see something similar, then you are able to resolve it yourself. I think their support staff is very knowledgeable. I have had no complaints about any ticket that I have ever logged with them.

One of the things that I did when I came into the company was to put this solution in place because they didn't have something.

It is one of those tools where you start using it and see how nice the graphs are. I have used other monitoring tools in the past, and their graphing has just been awful. Once you see LogicMonitor and start using it, you realize how easy and nice the application is to use.

The initial setup is straightforward. There are not too many steps. The process for doing it within the portal is very easy. It is step by step. It is very simple to do and understand. The steps are very clear and well written. It doesn't take long. The installation of the collector does not really have any settings to put in. It is just opening the installer and clicking "Next" a few times. Deploying a collector to a site takes five minutes. 

The initial deployment is a gradual thing. Our IT estate has grown considerably since we started using LogicMonitor. When we put LogicMonitor in, we probably had less than 100 devices. Now, we are already looking at uplifting our commitment to 450 to 500 devices. We have gradually grown it, so we haven't necessarily had to do a complete rollout for 500 devices in one project. We have been adding 10 to 20 a month. It doesn't take long at all. It's not something that we are looking at how to streamline, because it is already so quick.

LogicMonitor reduces new customer onboarding time because the collector rollout process takes us a couple of minutes.

We can drop a collector onsite for a customer, and we can pick up everything or select things that we need. It is very easy deployment-wise. This is really important to us. One of our current goals as an MSP is to always reduce the amount of time that it takes us to roll out solutions for customers. The quicker that we can deliver something, the quicker that we, as an MSP, can bill it. Also, the quicker we can get the cash into the business, the better for the business. Being able to drop something on a customer site and very quickly get everything added massively reduces the time it takes us to roll stuff out, which is really good for our business.

The way that we use LogicMonitor is probably a bit different to how some customers use it. We configure, install, and roll out appliances to customer sites. Installing LogicMonitor on the appliances is part of our build process. As we build the appliances in our lab, we install the LogicMonitor agent on something, then it gets shipped out to the customer's site. So, it is built into our build processes. Strategically, it is part of that. Our general strategy for rolling out is nothing special because we have done it over time.

General maintenance of the solution deployed on a customer site is pretty much nothing. Because we auto-upgrade all the collectors on customer sites, so we don't have to do anything. 

This does not really have anything to do with LogicMonitor, but we spend quite a lot of time just generally maintaining alerts within the tool, because we constantly need to change the thresholds of things. We get an alert for something, then we realize, "Actually, no. We don't need to monitor that," so we have to turn it off or change when we are alerted to something. From experience, that is something you have to do with any monitoring tool. You can't expect to install it and then never have to do anything with it. It is probably where we spend most of our effort maintaining it.

If we had other tools that were more complicated, we would need to hire more staff, and then our staff costs would be higher. Therefore, the costs of the products or services that we sell to our customers would then, naturally, have to be higher. Having a wide number of features under one product, which are very easy to use, means that we don't need to have highly skilled expert people running the solution. It can be run by more junior members of staff, and we don't need to have a lot of different products and software, which would increase our overall costs, which we would then have to pass on to our customers.

LogicMonitor saves us time. If there was a problem and we didn't know where the problem was, we would potentially spend hours of time trying to locate where the problem was. Whereas, LogicMonitor helps us pinpoint where problems are. Instead of spending hours looking at something and finding out if it is an issue, we might spend minutes instead.

LogicMonitor reduces mean time to repair. If we didn't know where a problem was or weren't able to pinpoint it, we could spend hours or days, potentially, looking for the cause or source of a problem. Whereas, with LogicMonitor, we can do it in minutes or hours, depending on how complex the problem is. It probably halves, if not more, the length of time it takes us to get resolutions.

We include costs in our pricing for the monitoring and management, but the LogicMonitor name probably doesn't have too much to do with that, but that's just because of the way we work.

We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month.

There is another feature of LogicMonitor that we would quite like to use, but it is quite expensive for our use case. It is called LM Config. We would have a very light use case for it. Therefore, I don't think that we could justify the cost of that at the moment. It is something that we would like to use, but it is just a bit expensive. 

It is definitely not the cheapest tool. As we scale, as a relatively small business, there are times when I think, "Should we monitor that?" or, "Should we do that?" because of the price of the devices. However, it is so good that we are not really looking at doing anything else.

I had evaluated LogicMonitor at a previous company, which was a much bigger company. It was a company where it was a lot harder to make purchasing decisions. When I moved companies, I had already seen LogicMonitor and how good it was, so I didn't look at anything else. I just knew we wanted to use LogicMonitor.

If people are comparing something based on price alone, I would still say, "Do a trial. Look at some of the extra features that LogicMonitor provides," because we have found that it does more for us than just monitoring. We use it as our remote access solution to things as well, which means that we were able to get rid of another product that we were paying for in favor of LogicMonitor. So, we have consolidated two requirements into one. Even though LogicMonitor might be more expensive than another solution, we have saved overall.

Go with LogicMonitor. Definitely, do a trial and test out the functionality.

We don't really use that many legacy tools. We are a fairly modern company in that pretty much everything we use is software as a service. So, LogicMonitor fits very nicely into that for us. We don't use products where we have to install them on servers. Everything that we use is cloud-based, and LogicMonitor is cloud-based. So, it is great from that perspective. We don't really have legacy apps, so LogicMonitor fits very nicely into that.

We actually don't use a large number of the integrations, and that's not necessarily because we don't want to. It's because we don't have some of the products that it integrates with, but we are looking to put some of them in largely because LogicMonitor has integrations with them. A good example of this is our support desk system at the moment is a certain product, but we're looking specifically to put something like ServiceNow in because LogicMonitor integrates with it. Doing that would mean that we can reduce the amount of effort on our support teams having to manually pick up things and log them, instead it could be done automatically. 

I think actually having LogicMonitor and their integrations is affecting our buying decisions for other products. This ability to integrate with other products is becoming increasingly more important. As our business grows, we are looking at how to become more efficient. Also, being able to integrate LogicMonitor with other systems is becoming increasingly more important as we look to streamline our work processes. 

We are looking at LogicMonitor's collectors along with the templated integrations and dashboards to enable us to automate our onboarding process and roll it out to new customers> It is on our roadmap, but a little bit further down the line. We are quite a small team and have a lot of stuff on our roadmap. This is just one of those things that we haven't gotten to yet.

It probably indirectly affects our ability to win customers. For some MSPs, if they are specifically selling their customers LogicMonitor, then it may be a bit more relevant. Our customers don't necessarily see LogicMonitor behind the scenes. It indirectly affects our ability to win customers in that we are able to be very responsive to problems and resolve things that may happen with their solutions. So, it allows us to react quickly, which affects our general ability to win customers when they ultimately get references from other customers and those customers are able to feed back that we are very responsive and able to rapidly resolve issues for them.

We don't tend to advertise to our customers that we use LogicMonitor. We don't push it as a premium product because of the way we use it. We bundle it within our service, and it is just a tool that we use internally to manage our MSP customers.

The biggest lesson that I have learned: No matter what tool you use, you still have to spend a lot of time tweaking alerts. You can't expect to put a tool like LogicMonitor in, just leaving it alone and never having to do anything. So, it is important to have a tool that is very user-friendly because you will still have to use it on a daily basis.

I would rate it a nine or 10 out of 10. It is probably one of the best tools that we have used.

We are a network of hospitals using the solution to monitor our network devices and all of the interfaces connected to them. It's predominantly instances of applications running on Windows Server. We use the Windows WMI for Windows Server stats.

The IT directors at our hospitals use it, so we have around 90 end-users Some of them have extended the monitoring capabilities to printers to stay on top of toner supplies. In the past, we've had admin people freaking out because the printer is out of toner, and we have any in the closet. Nobody was watching that, and some people would be hoarding supplies.

LogicMonitor replaced SolarWinds after a security breach.  We work with a network service provider that owns all of the network devices, and we had some issues with total inventory control. We're a monitoring site, so we're not necessarily on the operational side and we're out of the loop sometimes when things are changing.

It is easy to set up and monitor an entire facility. This is crucial because we have around 80 facilities that require monitoring. LifePoint is a hub-and-spoke environment, so it is essential to understand all of the WAN interfaces.

I'm a learn-by-example person, so it would be nice to have a cookbook for enterprise management. They have a rich API process, but there aren't many examples of how to do enterprise-style work. It is peculiar about how to do it for one device, but not necessarily thousands.

LogicMonitor can effortlessly pull data from one item at a time. I have yet to find an excellent way to get LogicMonitor to show me all the WAN devices and how they're doing in terms of capacity.

I have been using LogicMonitor for 18 months.

LogicMonitor has been stable so far. There has been a learning curve, where we had to allocate more resources to a collector doing work. At the same time, it has been relatively easy to stand up more of them.

Scaling is a matter of adding more collectors to the environment. If you've discovered too many devices, you have to rebalance the collectors. However, if you add more collectors into a sphere, you don't need to worry about doing the load balancing by yourself. You let the mechanics do it for you.

I rate LogicMonitor support nine out of 10. They have a button on all of the webpages that says "Contact Support," so you can do that online or submit a ticket. Both have worked well.

Positive

I was a big user of SolarWinds before. It was easy to pull data out of SolarWinds and then put it into other tools for big-picture analysis across the entire enterprise as opposed to an individual device.

Setting up LogicMonitor isn't very complex. We quickly learned that we could do some collector load balancing. As we're adding devices to a series of collectors, it can do its own load balancing to ensure you don't have too much on one server doing S&P polling. 

We did most of the work ourselves.

We've certainly seen a return. One of the features we use extensively is Netflow, which helps us better understand what is consumed in the WAN environment. For example, we can determine that the DICOM processing is unnecessarily using up the WAN. It can go over a Meraki network, which is an encrypted process going over the general internet. We have highly secure Opt-E-WAN environments that most traffic goes over, but we also use the public internet to send other encrypted data.

The license is annual, and I'm not fully aware of what it costs. We have a through-cycle that we go through, and they've been generous with us going above our limit. They're not strict on it. At the end of the year, they got us to renew. We always add some cushion for what we expect. Also, if you need custom monitoring or design work, you can pay them for consulting services. 

I rate LogicMonitor eight out of 10. It's easy to add new features to LogicMonitor. They have an active community of users who are willing to share their experiences and how they have extended the solution to do unusual things.

We use it as a primary monitoring tool for our cloud offerings. I work for one of the largest service providers in Australia and their cloud solutions. We monitor the entire cloud solutions using LogicMonitor.

The plugins are easy to integrate, and LogicMonitor provides these add-ons for vendors like VMware. It becomes very easy to integrate them and take the data sources. One does not need to configure everything individually. It automatically detects all the resources by their type and starts monitoring them almost immediately.

There is a lack of automation, especially in terms of remediating problems. The problem is seen and identified, but there is a need and a gap where LogicMonitor can help us automate the remediation of the problem. I hope it will be there in the future.

My colleagues feel the ease of use is a concern because to implement the granularity of the product, you need some programming knowledge and understanding of code development.

So, it becomes a challenge for everyone in your company, especially administrators who might not know how to code. Otherwise, there is no problem with LogicMonitor.

I have been using the solution for the past four years.

It is a stable solution.

It is highly scalable. We have never seen any issues regarding resource crunch. It's an everyday thing. All of our services use it as a primary resource for monitoring infrastructure. So in my department, we have fifty-odd people, and the service desk is around twenty-odd people. Our company is significant. We are on the verge of deciding whether You want to use this for the entire organization because a bigger company has acquired us, and that company does not use LogicMonitor. And we are pushing that LogicMonitor is a good resource for us, and we should use it across the company. Right now, it is in one department, but we want to push it across the organization, then it would become really big. We would have around two thousand end users using it. So, currently, we have two, and if this goes organization-wide, then there would probably be more people getting on board for this.

It's very good. They were there when we required some assistance from LogicMonitor. I personally dealt with those cases, and I was extremely satisfied with the kind of response I received. I rate it ten out of ten.

Positive

I worked with NETGEAR and other internal tools, but nothing was as elaborate, extensive, graphically oriented, and well-informed as LogicMonitor. It is one of the best product analysts.

The initial setup is straightforward. It took us around a week to thoroughly architect the solution deployment. The collectivity takes hardly five to ten minutes to install on any machine you want to be a collector and a monitoring resource. It doesn't take more than ten minutes. And installation of an architect is just a one-time job. You don't do it every day like we did it four years back. After that, we didn't look at it. We only spent some time, like, ten minutes creating new collectors, and that's it.

The pricing can be a little aggressive. Right now, it's a bit much for smaller organizations to adopt it. But comparatively, it also provides good features. So it's a give and take.

We did evaluate it, and we saw pros and content. Looking at the cost structure, everything, and business requirements, this was the best fit for us.

As I told you, this bigger company has acquired us. The other departments use that product, and the cost structure is not as high as LogicMonitor. But I am researching it. I still need more information. But with my initial research, I found a gap in how Icinga takes care of necessary components of our infrastructure, especially IBM web infrastructure, and how LogicMonitor incorporates that versus how Icinga does it. I still need profound information, but the preliminary research shows a LogicMonitor is better.

They have to first evaluate their options, consider their business requirements, use cases, and fix the purpose. If it is to process, LogicMonitor is definitely a tool to go for.

I rate it ten out of ten.

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.

We use it for monitoring our customer networks, for monitoring network devices, and we also use it for monitoring our hosted environment.

We're a managed service provider. We have LogicMonitor deployed so that we not only have our devices input into the system, but we also manage a lot of resources for our clients in it. We have it set up so that they can only see their items in there, through a lot of access control. We have a local presence with the collectors, the polling stations, while the data resides in the cloud. Once we pull the data, it then shifts all the data up to the cloud for long-term storage. LogicMonitor is all SaaS-based, other than the local collectors.

Before LogicMonitor, we were using another tool, and deployment of that tool took a lot of time, effort, and energy from our team, and it was very customized. While the end-product could have been great, because everything is so customizable, the problem was that we couldn't get up and running very quickly. With LogicMonitor, we didn't lose any of that customized look and feel, but we were able to get up and running so much faster. We went from onboarding even simple networks over the course of weeks to down to about a week.

We're able to monitor most of the things that our customers worry or care about. That's mostly because of the flexibility of LogicMonitor. The beautiful part about this is that if something is not currently in the system at the moment, the support from LogicMonitor has meant that it gets ramped up pretty quickly.

For customers who have multiple monitoring platforms, it's definitely very easy to simplify and get to a situation where there is one place for monitoring everything. That's definitely been helpful for them.

LogicMonitor's collectors, along with its templated integrations and dashboards, enable us to automate our onboarding process and roll it out to new customers. We've learned how to make it our own, based on what LogicMonitor provides us. We've been able to make ourselves more efficient, absolutely. The faster we can get online and onboard customers, the faster we can get to the point of turning their service on. That means that we can go from a non-paying customer who has agreed to work with us, to a paying customer who's now fully onboarded. We then have them working through the specifics of a managed services solution, outside of the monitoring tool, which is very important for us.

The breadth of things it's able to monitor, the simplicity of the deployment, and how quickly we can get it up and running are the biggest factors when it comes to helping us win new business. Functionally, there are no aspects of LogicMonitor that hinder that ability. It has definitely helped our margins, as an MSP, especially on the monitoring side, because we can get up and running so quickly. It's an absolute must for us to have the tool.

Seeing how easy it is to manage devices, how simple it is to add, remove, or modify a device, and the amount of data that's included out-of-the-box whenever you add a device, makes it far superior to any product. There are no add-ons needed. You license a resource or a device and you don't have to worry about adding a plugin to get all the additional metrics and the full depth of device data. This just happened last week on a customer demonstration call with a customer that has experience with SolarWinds. The customer saw how easy it was to get up and running on LogicMonitor and they were immediately sold and said, "Okay, give me a quote." That's a real scenario in which this product helped us. It's those aspects that not only help us gain new customers, but also to retain customers.

Overall, LogicMonitor saves us time. It's hard to quantify how much now, given that we've been using it for as long as we have.

When I consider LogicMonitor for future-proofing our business, with the ability to monitor customers' future IT environments, I'm pretty comfortable with it. That's because anything that we have come to them to request—whether it be a new feature, or having input into the UX and UI designs—they've been very open and very responsive to. Their support has been very accommodating. When it comes to looking at what could potentially be coming down the road, or to being future-proofed, I feel pretty good, given my experience with the types of special requests I've brought to them.

One of the most valuable features is the flexibility it gives for monitoring a particular device. There are a variety of ways we can get data into LogicMonitor.

In addition, it is an open platform that gives us the ability to add third-party application integrations, such as Slack or ServiceNow or Webex Teams.

There are also integrated features that allow for forecasting growth within the environment, not only for standard metrics like CPU and memory, but also for hard drive space utilization. Those are some pretty interesting and exciting features that are included in the platform.

On top of that, LogicMonitor has the ability to map out an environment at the network level.

It also enables us to drop a collector and automatically pick up everything in the target IT environment and map relationships. Obviously, you have to have the ability to reach the device. If there is anything stopping you via firewalls, then you can't get to it. But from a hypothetical standpoint, once a collector is in, we can capture everything very quickly based on an IP scheme. This has its advantages and disadvantages. The advantage is that we can capture everything very rapidly. However, if there is a misconfiguration on the client's network, then there could be the possibility of grabbing devices that are not needed. So there is some TLC that needs to be done when handling these, but it is a very useful aspect of the tool when it comes to onboarding.

In terms of instant visibility into all of the technology we will monitor for customers, it depends on the customer. But anything the customer wants us to monitor is leveraged. Some customers will say they only want to monitor telephony, while some will only want to monitor their network. We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status. It's pretty important for being able to provide a valued service to the customer about the overall health and availability of their environment.

We use LogicMonitor's dashboards quite a bit. In fact, we have our own customized dashboards. We use pieces of the templated dashboards and they definitely help in guiding us to places where we can pull certain indicators of how our customer is doing. Overall, we almost always end up having to adjust the dashboards to fit our customer needs, but the templated dashboards are significantly helpful. They tell us the different methodologies that we can use. We then take them and tailor them for the specifics that we need.

It's super-easy to customize the templated dashboards. For example, we have a school district customer with a campus. The template dashboards give us templates for wireless and templates for general networking and a few other things. We pick and choose the different widgets that we want out of those dashboards and we put them on the single dashboard for that particular school. That provides them visibility into all the things that are critical to them without having to go through multiple dashboards. We get rid of the things that they don't care about, things that our next customer may care about. We try to come up with dashboards that are specific to our customers' wants and needs and to give them, as much as possible, a single place to look for something.

LogicMonitor also hits the vast majority of technologies and complex environments when it comes to coverage, including on-prem, hybrid, cloud, et cetera. It does a really good job at covering the most-used technologies.

The only functional area I can think of that has room for improvement would be the dashboards. They could use a refresh. It would be nice if there were more widgets and more types of widgets.

We've been using LogicMonitor for two and half years.

Up until two weeks ago, I would have said the stability of LogicMonitor is phenomenal. We had never had an issue. But two weeks ago, they had a bumpy week and a half.

Scalability is based on our customers. The process for scaling the product out, for handling the resources from the collector side, is very simple. The one thing we've had issues with is that, when it comes to certain widgets on the dashboards, there are limitations on how many instances can be displayed through a widget. That is something that has caused us to rethink the way that we do our dashboards. Not that that's a bad thing, because it allowed us to actually come up with building dashboards for the client, and that has worked out really nicely. But that is one area where the scalability of the product has been a headache.

Not counting our API accounts, we have around 50 people using LogicMonitor. A lot of them are our frontline staff who are using the system to monitor, alert, notify, and to assist customers with getting their environments back up and running. The other accounts are used by our clients to log in and see their dashboards and devices. There are also folks on the backend, like me, who manage the environment, add the devices, manipulate the devices, delete devices—housekeeping.

We use LogicMonitor quite extensively and we have plans to increase our usage. Any of our clients who were not using us for monitoring before, rather we were being used for other projects by them, are either onboarded now or they're coming on board. The percentage of our clients that we have within monitoring is growing day by day and week by week.

We leverage their tech support quite a bit. They have a chat and a phone feature. For the most part, we leverage their chat and we use them for a very wide variety of things. Overall, I've been very pleased with their level of support. They've done a really good job of turning things around and helping where we've needed the help.

We switched from our previous solution because deployment time was entirely too long and it was too complicated.

Once we were given our initial tutorial of the product, before we onboarded ourselves, it was very easy to do and we have found onboarding and implementation very pleasing. In terms of an MSP onboard, their documentation is some of the best documentation I've seen from a vendor. Based on their documentation, you can very easily onboard yourself. But we also had an executive-level onboarding demonstration.

Our original deployment had professional services involved and it took three or four weeks. But our customer deployments usually take a week. The biggest issue with our customer deployments is having the customer give us the right level of access. Slowdowns don't usually happen from the LogicMonitor side, they're usually from the customer side.

In our own company, we don't have a ton of devices to monitor, so it was really about making sure we got everything incorporated into the monitoring platform, including our cloud services.

In terms of maintenance, the collectors have software that needs to be maintained. The collector software is relatively easy to update. We can do it all from the portal itself. It handles the updates and restarting of the services, and it does so pretty quickly. Generally speaking, there is no downtime for the customer, whenever that happens. Outside of that, there are data sources and other source files that need to be updated on a monthly or  quarterly basis, according to how they're released. At times, those can cause some false positive alerts if they are not handled correctly on the import. In general, I'm the one who handles deployment and maintenance in our company.

We did it ourselves, but we had a few days of LogicMonitor's professional services to get the initial deployment going. Those services were more of a consulting function. Overall, we didn't need nearly as much help as some customers might.

LogicMonitor has given our customers visibility into issues they didn't even know existed. In some cases, when we do assessments, we will actually load a customer's devices into LogicMonitor. In many cases, it gives us visibility into things like misconfigured stack modules or broken stack modules. Stacks or switches won't be stacked correctly. They'll actually be just this side of failing, and nobody has noticed it. Sometimes there are environmental issues that the customer hasn't noticed, where a particular location gets hot every day around the same time. They don't notice it and eventually it's going to result in something failing.

New customer onboarding, for us, usually consists of two things. One is getting access so that we can get it deployed and get visibility into the customer environment. And the second part of it is access for our team. We don't want the LogicMonitor component to take a lot longer. And, in fact, we're able to get LogicMonitor up and running for our customers much quicker than they're able to give us accounts.

It also reduces mean time to repair. When we see an alert, more often than not it's intelligent enough to help us come up with some sort of a solution faster. We can see a service or a server or a switch go into a critical state. A lot of the time, without something like LogicMonitor, which has the full visibility into the device, you would have to log in to the device and do some troubleshooting to figure out what's going on. It could just be that the temperature of the chassis is elevated and it's causing the system to underperform. I can't tell you how much time it saves us on something like that, but scenarios like that are what we experience on a daily basis. It definitely cuts time off of our troubleshooting and response. It's everything from temperature alarms, to disk space, to bad memory modules, and bad hard drives. You name it, we see it. And instead of having to log in and troubleshoot for an hour or two hours, the data is right there in front of us already and we can automatically dispatch somebody to go repair the device.

We're currently paying $525 per month per device for monitoring, and a dollar per device for configuration management.

We've had customers who have reduced their costs by not having multiple platforms for monitoring. That said, especially with super-large environments, the cost model for LogicMonitor is the one area where we run into issues. It's the one area where it can hinder our ability to win new customers. But that's only in very specific cases of very large customers. We're usually competing with something like SolarWinds. SolarWinds is on-premises and the cost model is very different. Sometimes we have challenges with large environments competing against that kind of cost model, where we're paying per node. When there are 3,000 or 4,000 nodes, that cost model can get very expensive very quickly.

There are three different licenses that we can get. There is the monitoring license, there is a configuration-monitoring license, and there is a log license. We've generally gotten the configuration-monitoring version. We're trying to get to a scale where we can get those numbers down. What we'd love to see is the scale of cost per device going down. The numbers get skewed, even still. The cost for 2,000 or 3000 devices shouldn't be the same as the cost for 500 devices, and by a large margin.

The AIOps is the log portion of the solution. We would love to use it, but the way that they have it licensed, we haven't been able to. They want to license it for our entire portal and it doesn't really make a whole lot of sense to us. For us, it's challenging the way they have it licensed right now. We're working toward it.

It does give us the ability to charge a premium price but it's a little tough to call something a premium product in the monitoring world—even though we may see it as a premium product—because our customers don't look at it that way. For them, it doesn't matter how great the monitoring tool is.

We looked at three or four others, but that was several years ago. We chose LogicMonitor because of the simplicity of deployment and the time to get up and running. It's simple, but it's still as complicated as it needs to be to do all of the things that we need it to do.

The biggest lesson I have learned from using LogicMonitor is that other products are inferior. Also, compared to what we knew with the legacy monitoring tools, LogicMonitor has done a great job. There are definitely better ways of doing things than the traditional monitoring tools did. If a new customer has SolarWinds or OpManager or some other on-premises tool, sometimes they're afraid of the cloud tools. What we'll say is that the amount of things that it can do far outpaces the legacy tools.

Think thoroughly about the structure you want to have in place. Don't just start implementing. Think thoroughly about how you want to be set up, how you want to manage the devices, how you want to manage the people, and how you want to manage the alerting. Plan, scale it out, and implement it properly so you don't have to go back in and do some cleanup work on the backend after the fact.

I would rate LogicMonitor a high nine out of 10.

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.