IT Central Station is now PeerSpot: Here's why

LogicMonitor OverviewUNIXBusinessApplication

LogicMonitor is #3 ranked solution in top AIOps tools, #4 ranked solution in best Network Monitoring Tools, #4 ranked solution in Infrastructure Monitoring tools, and #4 ranked solution in top Cloud Monitoring Software. PeerSpot users give LogicMonitor an average rating of 10 out of 10. LogicMonitor is most commonly compared to SolarWinds NPM: LogicMonitor vs SolarWinds NPM. LogicMonitor is popular among the large enterprise segment, accounting for 62% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 30% of all views.
LogicMonitor Buyer's Guide

Download the LogicMonitor Buyer's Guide including reviews and more. Updated: June 2022

What is LogicMonitor?

LogicMonitor, a unified observability platform, brings together comprehensive monitoring capabilities and enables observability across data centers, public/private clouds, and applications. LogicMonitor provides correlation, context, and clarity to understand the business impact and causes of complex IT incidents.

LogicMonitor is a SaaS-based unified observability platform that enables today’s digital enterprises to adopt a cloud-ready operating model for effectively meeting key business demands. The solution provides clarity across hybrid enterprise IT, and brings diverse IT and development teams together to solve complex problems. In addition, it enables IT to innovate faster while improving operations efficiency to the critical IT services they deliver. 

LogicMonitor unifies IT teams around a single platform that allows for the collection, analysis, contextualization, and exploration of observable data in hybrid settings.

LogicMonitor Features

LogicMonitor has many valuable key features. Some of the most useful ones include:

  • A single source of truth for data onboarding, management, and exploration across infrastructure, apps, and IT stacks.
  • A robust ecosystem of community-supported LM modules to accelerate onboarding.
  • Provides an intuitive interface with dashboarding, reporting, and data exploration to regularly and effectively monitor and troubleshoot.
  • AIOps capabilities enable anomaly detection, early warning detection, and rapid root cause analysis for services, applications, and infrastructure.
  • Monitors across networks, systems, storage, and other IT infrastructure.
  • OpenTelemetry-based application microservices with business context and vendor independence.
  • Logging to aid infrastructure monitoring, anomaly identification, and troubleshooting.

LogicMonitor Benefits

There are many benefits to implementing LogicMonitor. Some of the biggest advantages the solution offers include:

  • Instantly resolve issues across DevOps and ITops teams with a single source of truth. Anticipate and discover problems early, eliminate dead ends in troubleshooting, and deploy more frequently with the confidence that hybrid IT is under control.

  • By evaluating IT data in real time for anomaly detection, you can gain predictive insights. Identify potential flaws by analyzing billions of metrics and data points from hundreds of IT devices and resources.

  • Consolidate monitoring across IT infrastructure and apps to save money and reduce risk. By replacing several point products, you can save money on licensing and maintenance.

  • Consolidate enterprise-scale and innovative capabilities into a single platform.

  • To enhance productivity, the solution offers complete visibility across the technological stack with insights, context, and correlation.

Reviews from Real Users

LogicMonitor stands out among its competitors for a number of reasons. Two major ones are its robust root cause analysis and its event correlation tool. PeerSpot users take note of the advantages of these features in their reviews: 

Valentine C., Technical Service Delivery Manager at Sparx Solutions, writes of the solution, “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.” He adds, “I will rate it as a solid nine out of 10.”

Robert V., Teamlead at i-LEVEL ICT Solutions, notes, “One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot.”

LogicMonitor Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens

LogicMonitor Video

LogicMonitor Pricing Advice

What users are saying about LogicMonitor pricing:
  • "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.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."
  • "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."
  • "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."
  • "The licensing side of things with LogicMonitor, is quite simple. It is one license per device. Recently, you have additional licenses with things, like LM Cloud, which does confuse things a bit. Because it's very hard to estimate how many licenses you're going to need until you're monitoring it, so it's quite hard through that process to give a customer price to say, "This is how much this services will cost.""
  • "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."
  • "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."
  • "It's an enterprise-grade solution and competitively priced compared to the other solutions that are out there... 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."
  • LogicMonitor Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Valentine Christofis - PeerSpot reviewer
    Technical Service Delivery Manager at Sparx Solutions
    MSP
    Top 20
    Being a single pane of glass, a lot of metrics and alerts can all be grabbed from one place
    Pros and Cons
    • "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."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.
    Buyer's Guide
    LogicMonitor
    June 2022
    Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,229 professionals have used our research since 2012.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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. 

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

    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. 

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    Which other solutions did I evaluate?

    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.

    What other advice do I have?

    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.
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Philip Reeve - PeerSpot reviewer
    Technical Director - Cloud Services at Harbor Solutions
    Real User
    Top 20
    We went from nothing to full visibility across our internal and external estates of equipment
    Pros and Cons
    • "We only have one monitoring tool, and that is LogicMonitor. It does pretty much everything we need under one roof. They are very good at rapidly releasing new features. It's not like we have to wait six months or a year between new features and data sources. There is very quick development. If there is something that doesn't do it for us, I know I can just raise it with support or our delivery representative, and there is a good chance that that will be looked at. If it's not too much effort, we will see it released in the next few months. So, the solution is very good from that perspective. We have everything in LogicMonitor."
    • "Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on."

    What is our primary use case?

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

    How has it helped my organization?

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

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

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

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

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

    What is most valuable?

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

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

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

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

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

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

    What needs improvement?

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

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

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

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

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

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

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

    How are customer service and technical support?

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

    Which solution did I use previously and why did I switch?

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

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

    How was the initial setup?

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

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

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

    What about the implementation team?

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

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

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

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

    What was our ROI?

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

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

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

    What's my experience with pricing, setup cost, and licensing?

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

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

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

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

    Which other solutions did I evaluate?

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

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

    What other advice do I have?

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

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

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

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

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

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

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

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

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

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Buyer's Guide
    LogicMonitor
    June 2022
    Learn what your peers think about LogicMonitor. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
    610,229 professionals have used our research since 2012.
    Senior Operations Engineer at a tech services company with 11-50 employees
    Reseller
    Top 20
    Enables us to get up and running much faster, while still maintaining a customized look and feel for our clients
    Pros and Cons
    • "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."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

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

    How was the initial setup?

    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.

    What about the implementation team?

    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.

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    Which other solutions did I evaluate?

    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.

    What other advice do I have?

    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.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: MSP
    Head of IT Operations at a computer software company with 201-500 employees
    Real User
    Top 10
    Its visualization capabilities enable us to be more proactive in resolving issues and preventing problems
    Pros and Cons
    • "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."
    • "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 pinning that device and not getting any real intelligent information from it, then it can't appear on the map with other devices. Or if it can appear, then it won't show you which devices are actually joined to it."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    Just over two years.

    What do I think about the stability of the solution?

    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.

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

    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.

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    What other advice do I have?

    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.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Daniel Gavin - PeerSpot reviewer
    Network Architect at Envision IT
    Video Review
    MSP
    Top 5
    It consolidated our monitoring tools, reducing our onboarding times
    Pros and Cons
    • "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."
    • "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."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    We have been using LogicMonitor for about four years.

    What do I think about the stability of the solution?

    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. 

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

    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.

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    Which other solutions did I evaluate?

    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.

    What other advice do I have?

    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.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Idan Lerer - PeerSpot reviewer
    Senior Director, US Operations at Optimal+ Ltd.
    Real User
    Gives us one tool and one location so we can see across our entire, international infrastructure
    Pros and Cons
    • "Our installed base is in more than 70 locations around the globe... The fact that we don't need to manage and control 80 different servers just to monitor all of our infrastructure is a big difference. Now we have only one. The time savings are huge."
    • "LogicMonitor provides us with granular alert-tuning for devices. We can tune the alerts based on different aspects. For example, some of the environments are very big so we need to tune the thresholds differently than we would for a small environment. That is pretty easy to do in the tool."
    • "I would like to see more SQL monitoring and database monitoring. Although it has some basic functionality there, I would like to see more advanced database monitoring. I would like to be able to drill down into the SQL execution plan or the storage processor or query performance."

    What is our primary use case?

    LogicMonitor is a monitoring solution and we monitor all our infrastructure, up to the application level. We developed additional data sources in the tool, which is a kind of customization. We have a Big Data infrastructure, a Big Data solution for semiconductor and electronics companies. We stream a huge number of files into a central location. We load them and we process them. The engineers have a type of client-based analytic tool. Using LogicMonitor, we monitor the full process of the data stream: data loading, the ETL process, the SQL database, and Big Data solutions like Vertica and Hadoop.

    It's a SaaS-based solution. We deployed it across all our infrastructure, which includes on-prem and cloud: AWS, Azure, and Google Cloud.

    How has it helped my organization?

    The tool saves us a lot of time in troubleshooting. It helps us to be proactive and catch errors before they start to be a big problem.

    With LogicMonitor we are much more efficient. We have a huge infrastructure. Our installed base is in more than 70 locations around the globe. We have installations in Asia, in Europe, and the U.S. Before, we used Microsoft's System Center Operations Manager and for that we had to install a dedicated server, per location, and we couldn't see the whole picture across all our infrastructure. Since deploying LogicMonitor, we have one tool and one location where we can see across all our infrastructure. This is a huge improvement for our efficiency. The fact that we don't need to manage and control 80 different servers just to monitor all of our infrastructure is a big difference. Now we have only one. The time savings are huge. I can't even calculate them, but I would say hundreds of hours.

    LogicMonitor's ability to alert us if the cloud loses contact with the on-prem collectors is critical for us. We use and rely on LogicMonitor to make sure that the infrastructure is stable. In a case where we have a collector down, it's critical for us to know because all the servers using this specific collector will not get any more notification alerts or counters from those servers. We are a 24-by-seven solution for enterprise customers and the uptime of our solution is critical. Even just a stop in collecting information is critical for us.

    The AIOps is helpful because with ETL, for example, we monitor the number of files we have in different folders, like in the input folder or in the "pass" folder or the "fail" folder. We are not sure what the right number of files in each folder should be because of different volumes per customer. With AIOps I can know in advance that for this specific customer, 10 files in the input folder is okay, but for another customer it may be 100 files because that customer is much bigger and has more files. It helps me to understand that 10 is okay for this customer and 100 is okay for that customer.

    What is most valuable?

    The tool itself is valuable. I wouldn't say any specific feature is. It is very easy to customize and easy for us to build different different dashboards and put all we need on one screen and to correlate between different services. For example, in one screen I can see what the status is of my database, the ETL, and the CPU and memory for different servers.

    LogicMonitor provides us with granular alert-tuning for devices. We can tune the alerts based on different aspects. For example, some of the environments are very big so we need to tune the thresholds differently than we would for a small environment. That is pretty easy to do in the tool.

    The solution’s AIOps for things like anomaly detection, root cause analysis, and dynamic thresholds is a new feature that they announced in the last year or so. Because we have a very big infrastructure, but also very small ones, sometimes it's not easy to put the right thresholds or the right alert-tuning in place. So the AIOps is important. I don't want to have to specify a different threshold for each server. I would like the system to be able to learn what the right settings are and alert in that way. This is key. It's easy to use and you don't need to read too much to understand the visualization.

    What needs improvement?

    There is room for improvement with the UI. The UI is not that innovative. Although in general I like the UI, because it's very easy to use and very easy to customize, when you look at LogicMonitor for the first time, you don't think that it is a very cool tool. I do think this is a very cool tool, but the UI looks like an old UI.

    I would like to see more SQL monitoring and database monitoring. Although it has some basic functionality there, I would like to see more advanced database monitoring. I would like to be able to drill down into the SQL execution plan or the storage processor or query performance. In SolarWinds there is a model for SQL database monitoring. LogicMonitor has some, but not at an advanced level.

    For how long have I used the solution?

    I have been using LogicMonitor for three to four years.

    What do I think about the stability of the solution?

    In the last three or four years we have had only one event with downtime. The uptime is not a concern. Although, with that event, about two years ago, it was a critical issue.

    What do I think about the scalability of the solution?

    I don't see any issue scaling this tool. You can install as many collectors as you need. Each collector can monitor a lot of devices. And the UI is pretty fast, even if we add more and more data sources.

    We are now using it a lot and I expect that in the future we'll keep using it at the same volume.

    How are customer service and technical support?

    I haven't seen a problem with technical support. I think that they are pushing Professional Services more and more which, in general, as a customer you don't like too much because this involves extra payment.

    But overall, we get good support. We just implemented a new feature of LogicMonitor, the configuration management, and we got a lot of support from them in the last three to four weeks without any problem. We did a PoC on the configuration management to see if it would be helpful for us and their support team helped us as part of the PoC.

    Which solution did I use previously and why did I switch?

    We mainly used SCOM, System Center Operations Manager, and all kinds of scripts — VBScripts, PowerShell scripts — that we developed. But since it was hard for us to deploy, we didn't deploy it across all our infrastructure. We are not using it anymore.

    We switched mainly because we were looking for a SaaS-based solution and a centralized solution. Using SCOM, we had to install a server per site. Since we have more than 60 or 70 different sites it was a huge overhead for us, not just the installation but managing it.

    Since we only used one solution before, I cannot say that we consolidated multiple monitoring tools, but we were able to consolidate a lot of servers into one solution.

    I wouldn't say there was a big difference in the number of false positives we had before and the number we have now with LogicMonitor. We manage the tools that we used before LogicMonitor very closely. But with LogicMonitor, it's easier to control it from one location so it saves us time. Before, I had to log in to dozens of different servers to implement the specific alert thresholds. Now I can do it from one location, so dealing with the false positives is much better now.

    We also changed our approach. Before, our approach was to collect everything and to start cleaning what we didn't need. With LogicMonitor we approached it differently. We knew from before what we need, so we only put in what we need, rather than collecting everything and starting to filter.

    How was the initial setup?

    The initial setup was very easy. I did it by myself in a matter of a few weeks.

    The automated and agentless discovery, deployment, and configuration is very easy. You put the one agent in place and, from this agent, you can monitor the rest of the infrastructure you have in that specific environment.

    In terms of the solution monitoring devices out-of-the-box, for us it was about 50/50. What we did is that we started to monitor at the application level, not only the infrastructure. The ETL is part of the application level — how many files we have in different stages. For this, we had to develop all kinds of scripts inside the tool. But even if you need to develop a new, custom data source, it's pretty easy. For us it's a matter of a few hours and we can deploy the new data source across our infrastructure. We know how to manage that pretty well in the tool.

    But for the rest of what we had to monitor it was pretty okay. It was able to monitor all the Windows and Linux devices, as well as SQL databases. They have a lot built into the tool.

    We don't monitor networking and I think that they put a lot of effort into the networking devices, like CO networking or storage devices. They are not part of what we need to monitor. 

    We did a PoC. We deployed LogicMonitor in two of our environments. We have central and edge-types of environments. We put one on a central and one on an edge and we ran the tool. We made sure that we had everything we needed. I then gave my team some training — I have teams in the U.S., Asia, and in — and they took it on themselves.

    For maintenance, to change configuration and that kind of thing, in our organization it's a matter of three to four people, because they are in different locations. So in the U.S. they manage their stuff, and in Asia they manage their stuff, because there are different infrastructures in the U.S. and Asia.

    We give LogicMonitor to our customers as well. We build dashboards for them and they log in to our instance and they can see their infrastructure. About say 30 people are using the tool, as a result. They are mainly IT engineers and DBAs.

    We use this tool at different tiers. Tier 1 is our customers; Tier 2 is the field engineer; Tier 3 is our support headquarters, and Tier 4 is R&D. All of them log in to the tool and see what is going on in the infrastructure.

    What was our ROI?

    It's hard to measure the ROI, but there have been huge savings for us from the licensing point of view, manageability, deployment, implementation, and usage. It has been a huge improvement.

    And, of course, the fact that we can be proactive and stop errors and eliminate production downtime using this tool is priceless for us.

    What's my experience with pricing, setup cost, and licensing?

    Aside from the standard licensing of the solution, if you would like to implement other features, like what we did just now with the configuration management, there are extra costs.

    Which other solutions did I evaluate?

    We tried Sumo Logic. I liked the look and feel of the Sumo Logic UI more; not the ease-of-use, just the look and feel. But LogicMonitor was easier to deploy, easier to customize, and I got better support. I felt that with the Sumo Logic I would need much more support from the company.

    What other advice do I have?

    Be creative. You can be creative with this tool because it's easy to customize. What we did, for example, in the dashboards, is that we put the different components that in some cases can be correlated. We can see an issue in one component and the correlation to the other components.

    Also, it is important, at least for us, that it's easy to customize, and that goes for any monitoring tool, because we would like to monitor the application level and not only the infrastructure. It's easy to add the data sources, easy to customize, easy to build the dashboards. Since we have people all over the world, and we don't all sit in one office, if it wasn't that easy we would have to spend a lot of time on training, for knowledge transfer, etc. But I could give it to a basic user and say, "Please go ahead and use or customize your LogicMonitor," and he would be able to do it. This is critical for us.

    We are not using the solution's reports that much. Lately, we have developed a few reports, mainly for management. For example, with one report they can see, once a month, what the status is for specific storage, because we may need to charge our customers more, based on the storage size. But we mainly use the dashboards.

    What we automated is mainly the monitoring: the ETL, the response time of different services, the SQL server, the Big Data, but it's more monitoring. I'm not sure that I would call it automation. While it hasn't helped us to automate, it has helped us to be more proactive.

    I would rate LogicMonitor at nine out of 10. I really like this tool and so does the rest of my team.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    William Guertin - PeerSpot reviewer
    Senior Systems Engineer at Accruent
    Real User
    Top 10
    Its fine-tuned alerting lets us troubleshoot issues and resolve them quickly
    Pros and Cons
    • "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."
    • "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."
    • "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."

    What is our primary use case?

    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

    How has it helped my organization?

    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.

    What is most valuable?

    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. 

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

    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. 

    What do I think about the scalability of the solution?

    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.

    How are customer service and technical support?

    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.

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What was our ROI?

    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.

    Which other solutions did I evaluate?

    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. 

    What other advice do I have?

    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.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    AdamGleeson - PeerSpot reviewer
    Pre-Sales Technical Consultant at a tech services company with 11-50 employees
    Consultant
    Top 10
    Enables us to consistently wow our customers and set high SLAs because it reliably tells us if there is a problem anywhere
    Pros and Cons
    • "It's the depth of data that it gathers that I find really useful because there's nothing worse, when you're trying to find information about something or dig deeper into something, than hitting the bottom of the information really quickly and not having enough information to work with. With LogicMonitor, there is a load of information to dig through. It's a really good solution for that."
    • "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."

    What is our primary use case?

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

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

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

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

    How has it helped my organization?

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

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

    What is most valuable?

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

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

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

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

    What needs improvement?

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

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

    For how long have I used the solution?

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

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    It scales well; no concerns whatsoever.

    How are customer service and technical support?

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

    How was the initial setup?

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

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

    What was our ROI?

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

    What's my experience with pricing, setup cost, and licensing?

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

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

    Which other solutions did I evaluate?

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

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

    What other advice do I have?

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

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

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

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

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
    Buyer's Guide
    Download our free LogicMonitor Report and get advice and tips from experienced pros sharing their opinions.
    Updated: June 2022
    Buyer's Guide
    Download our free LogicMonitor Report and get advice and tips from experienced pros sharing their opinions.