LogicMonitor Reviews

We use LogicMonitor to monitor our customer environments. Some customers opt to look after their own environments, but some customers have us monitor them for them.

We use it to monitor the availability of servers and of network hardware. We have some storage array networks that are being monitored by it as well. We really use it as a guide to help. We monitor all of the key components in the different environments that we have running under LogicMonitor, and we use LogicMonitor as an early-warning system. If a problem develops in a customer environment, and we're monitoring it with LogicMonitor, then we get fairly rapid notification that there's a problem so we can start looking into it and doing something about it.

Also, along with all of that monitoring comes a lot of information logging for things like bandwidth, so we can see how much data is coming and going over different links. If a customer came to us and said, "We're thinking about downgrading the network links that we have," we have evidence to present to them to say, "Yes, it's okay to do that because you're hardly using the network link." Or we can say, "We wouldn't advise you to do that because we've observed that you're using most of that link and, if anything, you need to increase your bandwidth."

The device numbers being monitored is definitely on the order of several hundred among our three or four dozen customers. We're probably monitoring 50 different environments.

The solution's ability to alert you if the cloud loses contact with the on-prem Collectors is the crux of the solution. The customers are relying on us being proactive and highly responsive to any outages in their environments. A lot of the time, when we're phoning the customer up and saying, "We've detected that you've got an outage here," the customer doesn't even know about it. It hasn't even filtered through and their people haven't reported it. LogicMonitor enables us to consistently really wow the customers by sorting that out. They're saying, "I didn't even know that there was a problem in the environment," and we're already getting on and fixing it because LogicMonitor has allowed us to do that. It's really good.

The deployment is all automated, once we've selected where we want the Collectors to go. It saves us time because we're not having to faff around doing it. That might save us an hour per customer. The agentless aspect of it speeds up the deployment. Once we've got a single Collector there, we can leverage the information that that Collector can gather from all of the other devices. That's also really good.

The monitoring is the most valuable feature, the ability to have Collectors monitoring the health of different services. That's the thing that really helps us.

Among the dashboards, it's the availability ones that are my favourites. We have them set up so that they're only going to flag problems. If we look at the dashboard and it's completely empty, then we know that everything's in the green. If we look at the dashboard and there are entries on it, it means that somebody, somewhere, has a problem.

We use LogicMonitor's ability to customize data sources where a customer is providing web services or when looking at the availability of shared storage arrays. That's where we've started to customize it a little bit more to look at specific metrics that the Collectors have.

LogicMonitor provides us with granular alerts tuning for devices and that enhances our monitoring. The granularity that LogicMonitor goes into is really good. At first it can be a bit overwhelming because there's so much to it. But once you've distilled down the bits that you need to be paying attention to, and the bits that you're not particularly interested in, then it makes it quite simple. And when I say "all of the bits that you're not interested in," you're not interested in them right now. But that's not to say that in the future a requirement won't come up where you actually need to look at those bits. The fact that it supports so many different monitoring features is really good.

One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting. With some data types, it's not really possible to do that. 

But that's one of the good things about LogicMonitor: You've got all of the data there. The sheer wealth of data that it gathers means that you can take that data and manipulate it in other ways, if you want to.

We've been using LogicMonitor for three or four years now. We're partnered with LogicMonitor, so we can resell the solution as well.

I work in a pre-sales role, so when customers need new solutions they will come and ask. If I'm looking to scope replacement hardware, or if I'm looking to review the bandwidth utilization at a customer site, that's when I would go into LogicMonitor. Our service desk, predominantly, does the day-to-day monitoring. Whenever I come to LogicMonitor, it's a case of delving into historical data. At the same time, I've got an appreciation of how the solution works and the cool stuff that it'll do.

I've got no reason to believe that it's unstable, at all. I've not heard of Collectors crashing or the main console being unavailable for any extended period of time. There are periods of maintenance where it would be unavailable, but I'm certainly not aware of anything that was cause for concern with regards to the stability.

It scales well; no concerns whatsoever.

I've never actually used their technical support, but I know that our guys have, and they've always been able to fix problems fairly quickly. The technical support, as far as I'm aware, is really good.

I believe LogicMonitor monitors most devices out-of-the-box, but that was done with the setup which I wasn't involved in. We've got a lot of different customers. They've all got different types of network hardware. They've all got different storage arrays. Some of them have different types of hosts from different manufacturers. But we're able to monitor all of them with LogicMonitor because the information that LogicMonitor is pulling from them is common across them. The devices include Dell and HPE hardware, such as storage arrays, including Nimble, as well as a lot of Cisco networking gear. It will even monitor stuff that isn't enterprise-grade, but provided that something is enterprise-grade, it typically conforms to all of the WMI monitoring capabilities that LogicMonitor plugs into.

We have about half-a-dozen people who use LogicMonitor, and they're mostly third-line support engineers, so they're quite senior engineers. We have first- and second-line support and they just do the monitoring, but a lot of the really serious investigation, if there are any issues, go over to senior roles.

It gives us the ability to talk about our monitoring solution and service with a very high degree of confidence in ourselves. And we can set very high SLAs because we know that LogicMonitor is reliably going to tell us if there's a problem anywhere. That will enable us to start working on it very quickly, which in turn will help us to deliver very high SLAs  and very rapid response times to our customers. Obviously, customers are going to be happy about that because they want things fixed quickly. That is the best benefit that I see from it.

It's an enterprise-grade solution and competitively priced compared to the other solutions that are out there. If it were extortionately expensive, we wouldn't be using it. If it weren't doing what we needed it to do, we wouldn't be using it. Our organization is not huge, but LogicMonitor is worth every penny that we pay for it. I've never heard anyone say, "I'm not sure that we're getting good value for money from this product." It's integral to our business.

When you compare it to competitors, maybe some of the competitors' products are going to be a bit cheaper, but it comes down to the functionality that you're getting. You're paying for what you're getting, so I would say it's good value for money.

The solution's overall reporting capabilities are pretty good. We've assessed a lot of different solutions, because if we're offering a monitoring service to customers, it needs to be really good. We looked at SolarWinds and other ones, but LogicMonitor was the one that consistently came out on top across the monitoring requirements. LogicMonitor was hands-down the best.

LogicMonitor consolidates the monitoring tools that we need in one solution. We didn't have any tools in place originally, but all of the different types of things that we want to monitor comprised one of the reasons that LogicMonitor came out on top. It was the sheer breadth of functions that it has. A lot of the monitoring solutions that we were looking at would only do maybe 75 percent of it. They would monitor the uptime of servers and they would monitor the availability of network links, but they wouldn't give us any information around the bandwidth utilization of those network links. Other solutions would give us the bandwidth utilization, but then they wouldn't be able to monitor the servers. LogicMonitor gave us everything in one package.

It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that.

I'm not aware of any false positives that we get through LogicMonitor. That could be because we've tuned it over time so that we've tuned out any of those false positives. But generally speaking, if LogicMonitor flags something, there is a problem. Sometimes those problems are transient and something is just flagged because there was a blip in the system for whatever reason. But then it resolves itself without any intervention. LogicMonitor still allows us to see all of that stuff.

There are always lessons learned when you're running anything like this at scale. You set things up the way you think they should be set up initially, and then, with 20/20 hindsight you invariably decide, "Well, we didn't need to do that. We should have done this." But the solution allows you to do that. You don't end up fenced into a corner where you configured something the wrong way initially and you can't undo it. If you do see ways of doing things better, you can change them as you go.

I would rate LogicMonitor a 10 out 10. I've used other monitoring solutions over the years, and LogicMonitor does things really well. The console may not be quite as flashy as others that I've seen, but it's perfectly functional. Having a flashy console is not necessarily the be all and end all because, often, if the console is flashy, and it distracts you from what you're looking at. Every time I've ever used LogicMonitor, it's given me everything I needed out of it. I've got no complaints about it whatsoever.

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.

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 are in four public clouds. We are in AWS, Azure, and GCP. While we do Oracle cloud, we only have a small footprint there. We are monitoring all the virtual server environments as well as all the services in those environments and alerting on various set points depending on what it is: virtual, server and service. 

We are also monitoring our colos. We have on-prem hardware, networking, and server solutions that we are monitoring with LogicMonitor. We are in both the cloud and on-prem. The breadth of cloud and on-prem that we have is a good use case for LogicMonitor

We have very fine-tuned alerting that lets us know when there are issues by identifying where exactly that issue is, so we can troubleshoot and resolve them quickly. This is hopefully before the customer even notices. Then, it gives us some insight into potential issues coming down the road through our environmental health dashboards.

The breadth of its ability to monitor all our environments, putting it in one place, has been helpful. This way, we don't have to manage multiple tools and try to juggle multiple balls to keep our environment monitored. It presents a clear picture to us of what is going on.

When I first started, it was less granular in terms of the fine tuning and the ability to tune out specific servers running high CPU. Keeping a global general standard has really helped. We now modify the environment where we need to alert and ignore those areas where we're not as concerned. This has helped our company in ways that maybe management doesn't even realize, e.g., we're not waking up our engineers in the middle of the night. Therefore, there is more job satisfaction in being able to get a good night's sleep. For example, we had one team that was being alerted every couple hours, which was ridiculous when you're on call and need to sleep. This was one of my first prime objectives when I started: To improve the quality of life, so we don't have as much turnover in our engineering support staff.

At the top of the list of most valuable features is the ability to modify and add data sources, to use other people's data sources, and the LM Exchange itself. It gives LogicMonitor a lot of flexibility. It gives the end user the ability to monitor just about anything that can connect to a network and send data, which is a nice. You can take the data sources for what you are trying to do, then modify and adjust them to what your new parameters are or your use cases. With a lot of other applications, you either don't have the option at all (because you have to use what they have out-of-the-box) or it takes a lot of work to be able to enable monitoring something new. That is the best thing about being an administrator of LogicMonitor.

I have written my own data sources in a number of cases. We have also leveraged existing data sources and modified them to fit our specific cases. We don't typically publish them, but I know with the LM Exchange that it's becoming easier to do that.

I know management very much likes the dashboard presentations that LogicMonitor has. They are very comprehensive. You can pull in other things and add them in as a widget. You can see more than just what is in LogicMonitor, as it gives a single pane of glass for whatever management is interested in or whatever environment they're looking at when they are the monitoring software metrics. Then, it is presented all in one location, which is really nice.

We have SLAs for uptime, all our hardware, and all our infrastructure: hardware, servers, and storage. I have spun up a number of services based on the specific metrics for all those devices, then determine SLAs based on the uptime of those metrics. We have a nice SLA dashboard that shows the uptime of all of our environments, so when my manager or his manager comes to me, and asks, "What was the uptime of our environments or this area in storage?" Then, I can quickly look at the dashboard and tell him. Therefore, I really like that feature. 

Another dashboard that we find valuable is environmental health. We have a number of dashboards for all of our products. We have product teams for whom we created dashboards to look at the product, not just see what's happening now or in the past, e.g., what is currently having an issue. We also use it for forecasting, where we potentially might see an issue with storage on this server with a CPU that generally runs high or if there is an increasing trend in network traffic on the pipe. The environmental health dashboards have helped us stay ahead of potential issues that were coming down and ensure we had uptime for our customers' environments. 

LogicMonitor has the flexibility to enhance networking gear as well as handle our unique environment: servers, hardware, cloud, and Kubernetes. There are a lot of features that we like about LogicMonitor.

I would rate it a nine out of 10 in terms of alerting. It is doing everything that we wanted it to do. We did a lot of tweaking in the last year and a half. In the last two years, since I have gotten really familiar with the product, I have been able to mesh with the teams to learn what we need to alert on. Previous to my arrival, we were sending a lot of alerts to teams, waking them up in the middle of the night. We have cleaned up a bit of their garbage so we are pretty clean in terms of what we're alerting on. It is doing a good job of letting us know when there is a problem in the environment, which is nice. 

I have struggled a bit with the SLA calculations though, because I have some issues with the reporting having no data. However,  I have worked around those issues and we have a solid process for reporting the SLA.

Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved. Also, for a LogicMonitor program, it really depends upon the hardware and environment that it is running on to make that call. 

In terms of when it alerts, there are times when we do get alert storms because one device kind of fails on an interface where there are a number of things. Even if only one out of the five things on the interface fails, then everything on the interface will alert.

I would like it to able to create network maps and connectivity structures so you don't have to manually do it. This piece hasn't been a big hitch for us, but I imagine there are other customers who would really like to see the mapping piece of it grow and become a little bit more automated.

I personally have been using it for almost three years. The company has been using it for six years.

The stability is very good. There are times when we get specific alerts based on if there are issues with this piece or that, but those generally haven't affected us. 

It can handle scaling. It is like any other cloud service. There is a cost associated with scaling, so we currently don't monitor all of our environments. We monitor just the customer-facing production environments. It would be nice if we could monitor our dominant environments, but we will have to pay a lot more due to the scaling issue. So, there's a balance there between what we would like and what we are willing to pay for.

We have had issues in the past with data collection. Maybe it is due to pushing the limits of what LogicMonitor can do, or even the devices its monitoring. For example, we have a couple of F5s that are heavily used with a number of data sources on them and the SNMP couldn't actually pull all the information back in time, which was causing blind spots.

We have probably close to 100 users who use LogicMonitor, not all of them on a regular basis:

• We have infrastructure engineers who maintain the infrastructure of our environment.
• We have product engineers who maintain the IT server environments for the products. They work closely together with the infrastructure engineers.
• We have our automation team and DevOps team who use LogicMonitor to do performance modeling on their environment and learn the automation processes that they have. They also use the API fairly heavily. 
• We have software engineers on the teams who are monitoring specific server processes.

There are heavier and lighter users in all those areas. We have primary admins who administer LogicMonitor, and we're the heaviest users of it.

Their technical support is very good. When we have an issue, they are usually knowledgeable enough to handle it. If not, they at least know what the issue is. It seems like they're sitting right next to a DevOps software engineer because it doesn't take them long to escalate to the developers. They are very good at getting back to us. I would give them 10 out of 10 in terms of their response.

LogicMonitor has become our standard for all the products. Each product is basically an acquisition, e.g., we got rid of Datadog recently and phased out Splunk. The other solutions all came with their own tools, and we have gotten rid of all those other tools. A lot of that happened before I joined.

I was not involved in the initial setup.

I was at the company for enabling the cloud and Kubernetes, which was a fair amount of work to pull that information in and reconfigure the cloud devices. We had them monitored as regular resources, but needed to migrate them over to monitoring them as cloud devices. It was a fair amount of work with no good way to automate it.

We haven't had as big a cost for downtime, so that has saved us a lot of money.

I am on a call every Monday where we evaluate all the alerting that has been done in the previous week. We have gone from constant complaints two years ago down to basically nothing.

When we spin up new servers and network devices, we have NetScans that are going on in LogicMonitor. It's a weekly scan on each subnet. If it detects a new device, then it will look it up in the DNS. From there, we have everything named appropriately, such that they are named in a way where LogicMonitor can, using property sources, figure out who the device belongs to and what the device does. This is in addition to it doing a standard SNMP network monitoring for the device to determine what it is. It uses that information, along with the name and property sources, to automatically assign where that device goes in our resource tree, then starts holding that device. That has been a lot of work, but it has been very fruitful in terms of being able to be hands-free and hands-off for bringing new devices into LogicMonitor. This saves us about five man-hours a week.

When we were evaluating software packages (and we were already using LogicMonitor at that point), LogicMonitor became one of the few solutions that ended up on our short list because it can handle cloud and on-prem. They are really good at both. Solutions, like Datadog, don't give you the option to monitor on-prem hardware. They assume that you are just in the cloud because why would anyone be on-prem when there is cloud available, then you can spend a lot of money in the cloud. 

We have used dynamics thresholds in only a couple of cases. We didn't necessarily see the application of dynamics thresholds in looking at critical alerts. So, we haven't used that a whole lot. Also, we haven't really leveraged the AI pieces of LogicMonitor. We are at a point with our tuning that we haven't needed to do so. If teams started complaining about specific alerts, like specific servers showing trends, increasing or decreasing, then we would probably do it, but we have been able to handle those concerns with static thresholds at this point.

I would rate the solution a nine out of 10.

The biggest things are infrastructure monitoring and alerting. This is mostly for our virtual machines, but it is also for other networking equipment and a few other pieces as well.

We are at the newest update. It is a mix between on-premise Collectors and their software as a service (SaaS), which is the newest update. Our Collectors are also on the newest version right now. While they don't have to be the newest version, they tend to get pretty close to the newest version to work properly.

We have used the solution’s ability to customize data sources to a small degree. We are able to more finely tune all the details of what we are monitoring. This comes down to the false negatives or positives, and being able to alert on the actual details that we want to be alerted on.

The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at.

I built a remote workforce dashboard, which is my favorite dashboard. When the company pretty much all started working from home, I put together a lot of different graphs of types of infrastructure pieces necessary for users to be able to work from home and put those all onto one dashboard. Therefore, at a glance, we could view the health to make sure anybody working remotely would be in good shape and be able to work successfully.

The reporting capabilities are pretty effective, if you know what you are looking for. We don't use the reporting features a whole lot. However, when I have gone in to create reports, as long as you know what you want to be included in the report, it's definitely pretty quick and easy to get the reporting started.

Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure.

Our company has been using it for four to five years. I personally have been using it within the company for about three years.

It's been highly stable. We have had two brief outages, which lasted less than an hour, in the three years that I have worked with them.

We have two people (at any time) dedicated to deployment and maintenance. They are our systems engineers.

It is easily scalable.

We have about 20 users working with the solution who are mostly systems engineers. We also have some DevOps engineers and a few software architects who use it.

We have 1000 resources that we are monitoring with a couple hundred websites. As our company grows, we do plan to increase usage, but nothing major. It will probably be about a 10 percent increase over the next year or two.

I'd rate the technical support pretty highly. The few times that we have had to put in a ticket for support, they have been very helpful. Every time that I can remember, the issue has always been something on the actual resource being monitored. While not technically LogicMonitor's fault, they were still able to help us quickly identify and resolve it.

Twice in the last three years, we have had brief outages between LogicMonitor and our solution. We received phone calls almost immediately from LogicMonitor indicating this. It was a very quick reaction. We know the issue isn't on our side, which is good, in these particular cases.

LogicMonitor was able to replace at least two different solutions that we had in the past for monitoring. One of them being Logicworks. LogicMonitor was able to monitor a wide variety of websites, devices, and virtual machines. We were able to consolidate some of our monitoring so we are one single source now instead of multiple.

The solution’s automated and agentless discovery, deployment, and configuration has been helpful. I've used some of the automated discovery, especially when we've changed data centers and put a bunch of new hosts into our data center. I used their discovery tool. It was able to find and pull in most of the resources that we actually wanted. Even though I wasn't there for the initial deployment, for the times that I have used it, it seems very helpful. There are still some manual processes and checking that we do, but it has helped out a lot.

Out-of-the-box, it was able to monitor vSphere virtual machines, which was the biggest for us. We also have network load balancers, switches, and firewalls that it was able to pull in. We had to do very little to get it monitoring and reporting correctly.

We have definitely seen ROI with LogicMonitor. We used to provide 24/7 IT support for our users. We have since been able to change to operating just within normal business hours for IT support, and LogicMonitor was a large part of being able to accomplish that.

LogicMonitor has reduced our number of false positives compared to how many we were getting with other monitoring platforms. We have seen a 50 percent reduction in false positives, possibly more.

It really just comes down to making sure that we're getting alerts on something that actually does need attention.

We're starting to look into the solution’s Artificial Intelligence for IT Operations (AIOps) capabilities for things like anomaly detection, root cause analysis, or dynamic thresholds to see if it might be useful for some of our services.

Take a look at your environment and at what level of detail you will need for monitoring. One of the advantages to LogicMonitor is just monitoring your vSphere environment without monitoring the individual VMs within it. You still get a lot of detail about those VMs as instances. To put a VM in as a resource, instead of an instance, you get a lot more granularity on the operating system side for what you can look at. However, just monitoring your vSphere environment alone gives you a surprising amount of detail.

The biggest lesson I've learned is you need to understand what role your different devices play in your infrastructure in order to successfully monitor them. Get a detailed list of the devices that you do have in your environment that you want monitored and why you want them monitored. The why you want them monitored will tell you what different things you might want to be alerted on because LogicMonitor will collect a lot of information about your devices. Narrowing down what you actually want to be alerted on is the important part.

I would rate the solution as a nine out of 10.

We use it in a few different ways:

• For general monitoring of operating systems. 
• Leveraging some customized offerings, specifically for creating application monitoring. 
• Some external site-to-site monitoring in various places, ensuring that our websites and external pieces are available over an Internet connection. 

It has given us a clearer view into our environment because it's able to look in and pull things off of the event viewer or log files. We have been able build dashboards and drill down on things, which has helped improve our time to respond. Also, in the case of specific conditions being met in X log, we have been able to get in and take a look at that a lot faster rather than trying to connect and parse through the log and figure it out. It's able to flag that and work us towards a solution faster than normal.

We have a few custom data sources that we have defined, especially for our application. It is able to leverage a specific data source and build monitoring rather than just having it be a part of the general monitoring. It is segmented and customized for what we actually need, which has been pretty helpful.

Custom data sources have given us a bit more information from a point in time and historically viewpoint. In the console, it is easy to compare week-over-week or month-over-month traffic and numbers. As changes are made in the environment, we can look and have better historical knowledge, and say, "We started seeing this spike three months ago and this is the change we made," or, "We started seeing this CPU usage reduced after the last patch or software update." It lets us be able to compare and get a better insight into the environment over a longer period, rather than just at a point in time, when investigating an issue.

The solution has allowed us to have specific alerting for specific messages. If we know that X messages on a notification let us know this state has happened, we can then set that to be either an email notification or a tracking notification. In the cases of a log meaning that we have a specific issue, we can have it send an email and let us know. Thus, we have a better, faster response. We also have integrations with PagerDuty, which allows us to be able to make things very specific as to the level of intervention and the specific timing of that intervention. It has been nice to be able to customize that down to even a message type and timing metric.

The solution’s ability to alert us if the cloud loses contact with the on-prem collectors has been helpful to know. E.g., if we are having an issue with our Internet connection or some of our less monitored environments, such as our lower environments in different data centers where we don't have as heavy of monitoring. Therefore, it's helpful to have that external check there versus our production environments which are heavily monitored. Typically, we are intervening before it times out to say that it's lost the connection. It's been helpful to have that kind of information. This way, we know either via a page or email if there is any sort of latency or a timing issue with it connecting to the cloud. It's been helpful that it's not just a relying on the Internet connection at our site, but is able to see into our environment, then it monitors when there are connectivity or timeout issues.

We use it for anomaly detection because our software is designed to function in a specific way. Therefore, anomaly detection is helpful when there are issues that may not be breaking the software but when it is running in a nonstandard way, then we can be alerted and notified so we can jump on that issue. Whether the issue will be fixed it in the moment or handed off to development to find a solution, it's helpful to have that view into how it's running over the long-term.

It is a pretty robust solution. There are a lot of customizations that you can put in for what you want it to be checking, viewing, and alerting on. As we get alerting and realize that that's not something we need to be alerted on or it happens to be normal behavior, a lot of that information can be put back into the system, to say, "Alright, this may look like an anomaly, but it isn't." Therefore, we can customize it so it gets smarter as it goes on, and we're really only being notified for actual issues rather than suspected issues.

It's been helpful to be able to have some information to be able to pass along to development that's very specific as to what the issues are. E.g., we can see an anomaly during periods of time while this is running, then pass that along so development can figure out, "Is it a database issue, an application issue, or possibly a DNS level issue?" They also determine if there are further things that need to be dug into or if it is something that can just be fixed by a code change. 

The solution’s automated and agentless discovery, deployment, and configuration seems to work pretty well for standard pieces, like Windows servers and your standard hardware. It has been able to find and add those piece in. Normally, if I'm running into an issue with finding something, it's usually because it's missing a plugin or piece that just needs to be implemented, which just needs to be added in manually. However, 99 percent of the time, it finds things automatically without a problem.

The flexibility to be able build a custom monitor is its most valuable feature. Because it's just a general CPU or memory, it doesn't always give you a full picture, but we can dig into it, and say, "These services are using this much, and if these services are using more than 50 percent of the CPU, then alert us." We can put those type of customizations in rather than use the generic out-of-the-box things with maybe a few flags. It's been very nice to be able to customize it to what we need. We can also put in timings if we know there are services restarting at 11 o'clock at night (or whenever). We can put those in so as long as it's doing exactly what we want it to do, which is restarting the service, then it won't monitor us. However, if there are any issues or errors, then it monitors us right away. That's been really helpful to leverage.

We use a few dashboards. A couple are customized for specific groups and what they maintain. As I am doing projects, I'm able to make a quick dashboard for some of the things that I'm working on so I can keep track without having to flip between multiple pages. It seems pretty flexible for making simple use cases as well.

I have a custom dashboard which monitors each site and does virtual environment monitoring, such as CPU, memory, timing, etc. It was easy to get in place and adjust for what I wanted to see. It has been one of the go-to dashboards that I have ended up utilizing.

We can kind of get a single pane of glass and be able to view specific functions, whether it be sites or the entire environment. We are able to quickly get in, see what's going on, and where issues are coming from rather than having to hunt down where those issues are. Therefore, it's helped us more with our workflow than automating functions.

The solution’s overall reporting capabilities are pretty powerful compared to ones that I have used previously. It seems like it has a lot of customizations that you can put in, but some of the out-of-the-box reports are useful too, like user logon duration and website latency. Those type of things have been helpful and don't require a lot of, if any, changes to get useful content out of them. They have also been pretty easy to implement and use.

It needs better access for customizing and adding monitoring from the repository. That would be helpful. It seems like you have to search through the forums to figure out what specific pieces you need to get in for specific monitoring, if it's a nonstandard piece of equipment or process. You have to hunt and find certain elements to get them in place. If they could make it a bit easier rather having to find the right six-digit code to put in so it implements, that would be helpful.

Personally, I've been using the solution for about a year. We've had it in place for about a year and a half, but I came to the organization about a year ago.

I don't think we've really had a time where the application or monitoring nodes have failed. The connection to LogicMonitor has been very stable. We haven't had any connection issues to the SaaS offering. It's been pretty resilient and stable from our end.

The scalability seems fine. Every time we've had to expand and add elements, we've not run into any delays or issues with it. It seems to expand with us as we've needed to use more features. We haven't had any issues with delays or timing. It's been able to handle what we've thrown at it.

There are at most 10 users at our company, who do everything from application monitoring to platform engineering to some developers who have access into the solution for some monitoring pieces. Varying segments have been able to get in and they all seem to have had pretty good luck with accessing and using it.

We are using LogicMonitor pretty extensively. We're using it from low level environments, development, quality assurance, all the way up to user testing and production. We have leveraged it in as many segments and parts of the business as we can. It has been really helpful to have it be able to handle different workloads, but also be customized. This way, we're not getting triggered at 2:00 AM because a switch is on in the office reporting an issue, instead we can adjust those timings to report for specific times of the day rather than any time during the day.

We have about 1,000 totals including VMs and physical devices.

The technical support has been pretty good. I haven't had to leverage it, but some of the people I work around have taken it on when we have had questions or issues to leverage the process. They seem to be fairly responsive and the timing of it is usually good. We are usually hearing back in minutes instead of hours. We haven't had any major issues with them.

We've eliminated three different monitoring tools by leveraging LogicMonitor. We had two different in-house, custom built tools that were used for a long time that we were able to roll off, and we also used Nagios. I have also used Zabbix and Orion.

LogicMonitor has reduced our number of false positives compared to how many we were getting with other monitoring platforms. We leveraged the solution to focus it down and only look at the specific things that need monitoring, e.g., rather than every time a service is down we get notified, instead if it's not a critical service, then we can just get a flag, go back, and check it. This is rather than getting spammed with hundreds of emails about specific things being down. Thus, we can customize it for what we actually want to know and need for non-issues.

It had already been implemented before I joined the company. We've added a few functions since then, but the core and initial launch of it had already been implemented and heavily used at that point that I joined.

We have definitely seen ROI.

We have seen probably a 80 or 90 percent decrease in false flag alerts.

We move our people so they're able to be more proactive on things, rather than having to deal with parsing through and figuring out if something is an issue or a non-issue, that cuts down on our personnel time of managing the day-to-day processes. That's been helpful. At least from conversations I've had with management, they've seemed to have found it to be a good investment and solution for getting our normal work done, but also for making sure that we're ready to go if something does go wrong.

It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise. 

I would definitely recommend LogicMonitor. It's something to look at either when signing up for a trial or for a use case process . It's been a great product. It has customizations when you want them, and out of the box solutions if you don't want them. It works and is reliable. Compared to other monitoring platforms I've used in the past, it seems to be the most powerful and robust that I've dealt with.

The solution monitors most devices out-of-the-box, such as, Windows, Windows Server, Linux, F5 load balancers, Cisco firewalls, and Cisco switches. Those have been pretty easy to monitor. Our issues have been with one-off or nonstandard platforms that we've implemented. Otherwise, everything has been pretty easy to implement.

I would rate it as a solid nine (out of 10).

We primarily use it for unified observability, network compliance, and the benefit of an easy-to-administrate SaaS-based solution.

I'm familiar with LogicMonitor, mainly through my clients. Its key features include network discovery, user-friendly dashboards, and robust reporting capabilities.

Once you have your data within LogicMonitor, whether it's for network, server, or storage data, your LogicMonitor has many dashboards built out of the box. So, all your data is consolidated in a nice, efficient way. Suppose a customer needs to provide reports to management or understand which devices have been added during a certain period or are out of compliance.

LogicMonitor needs to invest more in APM functionality. The solution's core focus is infrastructure monitoring, but LogicMonitor is endeavoring to expand into the APM space with the tool. It works adequately but could benefit from additional investment to enhance its performance.

I have been using LogicMonitor for three to four years.

I've had no issues. I rate the solution’s stability a ten out of ten.

The solution is suitable for enterprise customers. Twenty users are using this solution.

Scalability is excellent. Many other solutions cannot scale up to a sizable footprint without hiring more staff, allocating more resources to infrastructure, or obtaining additional budget.

They offer various support levels to clients, allowing them to choose the level of service they prefer. Typically, enterprise customers opt for premium support or even higher levels. With round-the-clock availability and resolution within an hour or two, custom support is also available.

Positive

The initial setup is easier than other solutions, so we partnered with LogicMonitor.

The pricing can vary yearly or monthly, depending on the clients we're working with and their size and scale. For example, the pricing for a customer with ten thousand licenses versus a hundred licenses can vary.

LogicMonitor is a SaaS-based solution, but users can deploy it wherever they want. They can deploy collectors in the cloud, on-premises, on their servers, or VMs. It's flexible in how it can be deployed. However, unlike many other monitoring tools, you don't need to set up a lot of infrastructure.

For an enterprise customer, LogicMonitor may not be considered excessively expensive. It tends to have a higher price tag compared to legacy monitoring solutions, yet it offers more value. Smaller customers with only a few hundred licenses might perceive it as pricier since they have fewer items to monitor and fewer demands. The true value of the solution shines in large, intricate environments where it can effectively monitor hundreds of devices.

In terms of advice, anyone currently using a monitoring solution is likely aware of its shortcomings. I suggest not hesitating to challenge the status quo and explore alternative solutions. LogicMonitor, among others, represents a significant step forward in SaaS-based monitoring solutions. These platforms offer considerable value with minimal ramp-up time and learning curve. Considering a solution like LogicMonitor, it's crucial to identify the gaps in your current monitoring environment. I encourage you to try it; reach out to a reseller, such as myself, or directly to LogicMonitor to explore the platform. It's one of those situations where seeing is believing; you need to experience the value firsthand.

We haven't had any issues with LogicMonitor. All of my clients have loved it and are renewing their subscriptions. It has been fantastic compared to many other tools we've used, especially in the reusability space.

Overall, I rate the solution a ten out of ten.

LogicMonitor is predominantly used in modern cloud monitoring tools. You have servers that you want to monitor for performance, CPU, memory, and so on, or you have a cloud environment that you want to monitor for EC2 instances, ALBs, and more. 

Our LogicMonitor keeps track of everything. LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem.

The most valuable feature of LogicMonitor is the infrastructure monitoring capability.

Dashboarding capabilities could be enhanced.

It is cumbersome, you must do it all at once, and then you must repeat the process every now and then. If you ask me, I would rather it be automatic because they know what I monitor. If they have a template that they can provide, I can create a dashboard without even trying. 

The issue right now is that I'll have to combine tens of widgets to create my own dashboard which is a little time-consuming and inconvenient.

I have been working with LogicMonitor for seven years.

We have the latest version. LogicMonitor is a SaaS product.

LogicMonitor is a stable solution.

LogicMonitor is a scalable product.

In our company, we have 5,000 users.

Technical support is good.

The initial setup is easy.

The deployment took one day to complete.

They are expensive for the cloud.

If you only want to use LogicMonitor in the cloud, there's a better tool available. But if it's for traditional infrastructure monitoring, it makes sense; it's a useful tool. 

However, if you are a cloud-native organization and want LogicMonitor, I believe it will be a costly investment because there are many better cloud monitoring solutions available.

There are numerous options, including CloudWatch itself, or Grafana with a connection to a CloudWatch data source. You can use Grafana to monitor as well as others, there are numerous tools available.

They are good, I would rate LogicMonitor a nine out of ten.