Infrastructure Monitoring and Observability Platform logo

    Infrastructure Monitoring and Observability Platform

    LogicMonitor's automated SaaS performance monitoring platform provides IT Ops teams with end-to-end visibility and actionable metrics to manage today's sophisticated on-premise, hybrid and cloud IT infrastructures. Deploy and manage your monitoring faster and automatically with Auto-Discovery of devices. Act on infrastructure performance data using built-in and customizable dashboards, performance forecasting, and full reporting. Use built-in workflow capabilities including alerting routing and escalation management to improve IT team response.

    Ratings and reviews

    4.5
    696 ratings
    17 AWS reviews
    |
    679 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (696)
    Seth Jenkins

    Proactive monitoring has prevented outages and improves visibility across cloud infrastructure

    Reviewed on Nov 12, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LogicMonitor is monitoring infrastructure environments and utilizing dashboards to give a high-level overview.

    LogicMonitor helps my team spot and respond to issues across those infrastructure environments. The critical errors and warnings identify how severe an alert is, and we take action depending on that severity.

    How has it helped my organization?

    LogicMonitor has impacted our organization positively. It gives us the ability to be proactive in identifying issues in the infrastructure before we reach an outage or critical impact.

    One specific outcome I can share is that I have a pool of hosts in Azure that we are monitoring closely for memory usage. LogicMonitor has been pointing out all of the times those hosts were severely impacted throughout the day. With that information, we have started to add additional hosts to the pool while also looking at different sized VMs to support our users.

    LogicMonitor has not affected our team's mean time to resolve incidents, but it has given us the ability to avoid incidents completely.

    What is most valuable?

    The best features LogicMonitor offers are ease of use and dashboards.

    The dashboards are especially easy for my team to use day-to-day. They give a high-level overview of how things stand, in red, yellow, and green, and allow us to know if things are working as they should or if we need to put attention on the environment.

    LogicMonitor is an easy tool to work with, and creating dashboards is pretty easy, which is very helpful.

    What needs improvement?

    LogicMonitor can be improved. The ability to tune the application and tune the alerts to match your business needs is the most critical feature and the one that takes the most time. I have been using Claude to help tune my environment, and it would be nice if LogicMonitor had something similar, and for free.

    For how long have I used the solution?

    I have been using LogicMonitor for 13 years.

    What do I think about the stability of the solution?

    LogicMonitor is very stable.

    What do I think about the scalability of the solution?

    LogicMonitor scales easily and scales well.

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

    We did not previously use a different solution. We have been using LogicMonitor from the beginning.

    What was our ROI?

    I do not think LogicMonitor has generated any savings. It is really more about preventing incidents and production outages than saving money.

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

    I did not purchase LogicMonitor through the AWS Marketplace.

    Which other solutions did I evaluate?

    Before choosing LogicMonitor, we did not evaluate other options. We only looked at LogicMonitor because we were familiar with it.

    What other advice do I have?

    On a scale of one to 10, I would rate LogicMonitor overall an eight.

    My reason for an eight is that it is very useful and helpful, but there are some challenges, and it does take daily administration to fully utilize the tool. It is definitely not a set it and forget it type of application.

    I do not have any challenges with visibility across the environment at the moment, including with the Envision platform.

    I am using Claude to manage the LogicMonitor environment.

    The cloud provider we use is mainly Azure, but we use AWS and GCP too.

    My advice for others looking into using LogicMonitor is to make sure that you provide a dedicated admin to manage the tool and tune the alerts.

    reviewer2925621

    Infrastructure monitoring has accelerated customer onboarding but needs better analytics guidance

    Reviewed on Nov 12, 2026
    Review from a verified AWS customer

    What is our primary use case?

    Our primary use case for LogicMonitor is infrastructure monitoring and observability across multiple customers. We primarily use LogicMonitor to monitor infrastructure, configure alerts, manage alerting policies, and perform log analysis. It supports various environments, including Windows, Linux, SNMP-enabled devices, databases, and other technology stacks.

    In my day-to-day work, I handle multiple customers. When a new customer is onboarded, we first understand their requirements and assess their existing infrastructure. For example, a customer might have anywhere between 1,000 and 5,000 network devices that need to be monitored. These devices could include Linux servers, Windows servers, network devices, databases, and components from various other technology stacks.

    Based on the customer's requirements, we prepare an implementation plan and onboard all the required devices into LogicMonitor. We also create a structured resource tree that aligns with the customer's infrastructure and organizational requirements. This structure typically separates environments such as Production (Prod), Pre-Production (Pre-Prod), and Development (Dev).

    The purpose of creating this resource tree is to organize the infrastructure effectively and enable customers to monitor their devices in a structured manner. This helps them achieve better visibility into their infrastructure and simplifies the overall observability process.

    Although LogicMonitor offers several capabilities, including log monitoring, alerting, and alert configuration, our primary focus is on infrastructure monitoring and observability. This is the core use case for which we implement and manage LogicMonitor across our customers' environments.

    How has it helped my organization?

    LogicMonitor has had a positive impact on our organization. We work with various vendors and technologies that compete with LogicMonitor, such as Dynatrace and the ELK Stack. Each of these solutions has its own strengths and capabilities. However, we primarily use LogicMonitor for observability, particularly infrastructure monitoring and observability.

    One of the key advantages of LogicMonitor is its faster implementation process. Using LogicMonitor, we can typically complete the implementation for a customer within 15 days to one month, depending on the complexity of their infrastructure and requirements. During this period, we can onboard the customer's infrastructure and configure the monitoring environment according to their needs.

    This faster implementation process has significantly contributed to customer satisfaction. Customers can see the implementation progressing quickly, review the configurations, and provide feedback at an early stage. Based on their feedback and customized requirements, we can make the necessary adjustments and move forward efficiently.

    Overall, LogicMonitor's streamlined implementation process helps us onboard customers faster, respond to their specific requirements, and improve the overall customer experience.

    What is most valuable?

    One of the best features offered by LogicMonitor is Edwin AI, which we are currently exploring and working with. Apart from Edwin AI, LogicMonitor is a relatively simple and user-friendly tool compared to other competing vendors.

    For example, its alerting capabilities for device monitoring are particularly useful. The overall website navigation is intuitive, and the documentation provided for implementation is also quite good. Overall, the onboarding and implementation processes are straightforward and easy to manage.

    Edwin AI is one feature that particularly stands out to me because it is a relatively new capability introduced within the product. I have recently started working with it and am still in the initial learning phase.

    One of the key capabilities of Edwin AI is Root Cause Analysis (RCA). It helps engineers identify the underlying cause of an incident without having to investigate everything manually. It also assists engineers in navigating complex troubleshooting scenarios by providing insights into potential causes and helping them resolve incidents more efficiently.

    That is one of the specific use cases of Edwin AI that I find particularly valuable.

    Apart from these capabilities, I would not add anything further regarding LogicMonitor's features, as I have already covered most of the functionalities that I currently use in my day-to-day work.

    What needs improvement?

    From my perspective, LogicMonitor is primarily useful for infrastructure monitoring. However, compared to some of its competitors, I feel that there is room for improvement in certain areas. For example, solutions such as Elasticsearch offer extensive capabilities for log analytics and dashboard creation.

    One area where LogicMonitor could improve is its implementation guidance and learning resources. The existing videos and documentation can sometimes be quite complex to understand, especially during the initial implementation phase. It would be extremely useful if LogicMonitor could provide customized implementation plans based on individual customer requirements.

    Although LogicMonitor offers certification badges, having more detailed video tutorials demonstrating actual implementation scenarios would be very helpful. These videos could explain the implementation process step by step, covering different use cases and configurations.

    Regarding customer support, my experience has been quite positive, and I am satisfied with the support provided.

    In terms of additional features and improvements, I would suggest that LogicMonitor focus more on providing practical learning resources rather than relying primarily on certification badges. For example, it could offer:

    • More detailed, step-by-step video tutorials covering real-world implementation scenarios.
    • Practical demonstrations explaining how different LogicMonitor features can be configured and used.
    • A sandbox or dummy environment where engineers can practice implementations, explore different functionalities, and troubleshoot scenarios without affecting a live customer environment.

    These improvements would make it easier for engineers to understand the product, gain hands-on experience, and implement customer requirements more efficiently. I have seen similar learning and hands-on enablement approaches offered by competing vendors, and I believe LogicMonitor could benefit from introducing these capabilities as well.

    For how long have I used the solution?

    I have been using LogicMonitor for one and a half years.

    What other advice do I have?

    I would rate LogicMonitor an overall 7 out of 10.

    If I had to choose between a rating of 7 and 8, I would select 7 because I primarily see LogicMonitor being used for infrastructure monitoring. Some of its other functionalities are relatively complex to work with, particularly custom dashboard creation, log analytics, search-related use cases, and data manipulation.

    One of the challenges I have experienced is that modifying, parsing, and enriching data is not as straightforward as it is with some other tools. Competing solutions offer more flexibility when it comes to data enrichment and manipulation. In comparison, achieving similar functionality in LogicMonitor can be quite challenging.

    Regarding AI governance and security, LogicMonitor has these capabilities integrated into its product. Security-related configurations and controls are also managed within the boundaries and policies defined by individual customers.

    As for the accuracy and reliability of LogicMonitor's AI-generated outputs, I am still in the initial testing phase. So far, the results have been satisfactory, and the functionality appears to be working well. However, I would need more hands-on experience and testing to provide a more comprehensive assessment.

    Which deployment model are you using for this solution?

    On-premises

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Badal Bhautikkumarumeshbhai

    Advanced monitoring has reduced downtime and now predicts issues across hybrid environments

    Reviewed on Nov 12, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for LogicMonitor is monitoring our server infrastructure, network infrastructure, and cloud services. In addition, we build customization scripts for LogicMonitor and create our own custom monitoring and metrics.

    Our customizations help us monitor things that the out-of-the-box setup does not cover. For example, if LogicMonitor does not provide out-of-the-box metrics, we can write our own scripts in Python, Groovy, and PowerShell. Based on those scripts, we can run our own commands, hit our own APIs, and set up metrics for them.

    We can also add our own SNMP OIDs and use a logs-based collector.

    How has it helped my organization?

    LogicMonitor helps our team catch issues before they become incidents. For example, if we have an incident in our network infrastructure, LogicMonitor captures SNMP traps and system SNMP traps before it happens. We can identify those anomalies and convert them into ServiceNow incidents, and then the team works on them before major issues arise.

    LogicMonitor has impacted our organization positively. Previously, we used a different tool, SolarWinds, which was not good enough for our needs. We could not capture our own custom metrics or cover other functionality, such as cloud services monitoring and server monitoring. With LogicMonitor, we can do anything with our own scripts, along with the great out-of-the-box solution that LogicMonitor provides.

    One of the finest outcomes we have seen since using LogicMonitor is less downtime. We can reduce the mean time to problem detection and automate with great platform tools such as Itential and ServiceNow. That helps us reduce overall manual effort.

    In terms of the impact on our team's mean time to resolve incidents, before this integration we invested more effort in RCA analysis. With the help of this solution, incident resolution time and downtime have been reduced by approximately 50 to 60%. That is a very good outcome from LogicMonitor.

    What is most valuable?

    One of the best features LogicMonitor offers is network and infrastructure monitoring, which is the easiest way to monitor. The second is the pure-based customization tool, with which we can write any customization script. The third is cloud metrics monitoring. The fourth is log-based anomaly detection.

    I think LogicMonitor's AI capabilities have strong governance and security. LogicMonitor has governance and security options so that our data cannot be stolen by any external party. It is safe from the LogicMonitor side, and it is a good security option.

    I also think the accuracy and reliability of the output of LogicMonitor's AI capabilities are good. LogicMonitor collects the raw data, processes it, and builds a customization model on its own end. It gives the best output, with accuracy of around 90 to 95%. It is a reliable output.

    Dynamic Service Insights affects our service health monitoring and our ability to manage business risk. Dynamic Service Insights provides the anomalies, so we can identify issues and address them with minimal business risk.

    Dynamic Service Insights also affects our understanding and management of digital services in our organization. We use Dynamic Service Insights only for the prediction part. Based on that, we can define our workflows, automate that part, and reduce our effort.

    We use Edwin AI for diagnosing root causes and orchestrating remediation. For example, we monitor the network part. If an alert is triggered from the Envision part, we use Edwin AI workflow automation and a remediation script, and we can reduce manual effort and MTTR. It is an effective option for us for minimal business downtime. It is a very good option and a very good product.

    We are also using the autonomous learning feature of Edwin AI. Once an alert is triggered, the integration triggers ServiceNow, we open incidents, and the rest of the team works on them. When the issue is cleared, the alert also clears, and we face minimal downtime. That is a very good feature of Edwin AI.

    What needs improvement?

    LogicMonitor can improve its dashboards and reporting. It is not a major issue, but we need a very good network topology so that we can identify issues. That topology is required, so LogicMonitor can improve the topology part.

    The main challenge we face with visibility across our hybrid infrastructure is that we need to visualize end-to-end traffic from source to destination. We are not able to capture the topology where we deployed this hybrid cloud in our environment. We are also not able to see the topology from on-premises to the public cloud. That is the main issue in our hybrid infrastructure deployment.

    For how long have I used the solution?

    I have been using LogicMonitor for around two and a half years.

    What do I think about the stability of the solution?

    LogicMonitor is stable.

    What do I think about the scalability of the solution?

    LogicMonitor's scalability is one of the finest in this current era of network monitoring solutions.

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

    We previously used the SolarWinds platform.

    What was our ROI?

    We have seen a return on investment with fewer people needed, money saved, and AI capability. That is a very good option in the current market scenario.

    We have seen measurable savings in manual work, lower downtime costs, and fewer hours spent on incident resolution. That is a very good feature and a very good capability of LogicMonitor.

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

    We purchased LogicMonitor through the AWS Marketplace.

    Our experience with pricing, setup cost, and licensing spans one year only.

    Which other solutions did I evaluate?

    Before choosing LogicMonitor, we evaluated another option: ScienceLogic.

    What other advice do I have?

    I rate LogicMonitor overall as 9.5, or 9 as a round number. I deducted points for the topology, dashboard, and reporting.

    LogicMonitor is deployed in our organization. In our environment, we use public cloud and on-premises infrastructure.

    Our cloud providers are AWS, Azure, and GCP.

    Anmol Kumar

    Unified monitoring has provided a single hybrid view and simplifies alerting and observability

    Reviewed on Nov 12, 2026
    Review from a verified AWS customer

    What is our primary use case?

    Our main use case for LogicMonitor is as our primary enterprise monitoring tool. We handle our complete observability from a network standpoint, as well as for servers and cloud. We have a hybrid environment, and all of it is monitored only with LogicMonitor.

    LogicMonitor helps our team handle visibility and alerts across the network, servers, and cloud in that hybrid environment in a few ways. We have alerting, and we have an integration with ITSM, which is ServiceNow. We also have dashboards created, and with the use of properties, we have set up roles for different teams. None of the teams can see resources that are not in their purview. Using those techniques, we are able to segregate the resources and have all the relevant teams onboarded on the platform itself.

    Apart from that, we use different kinds of technologies. For network, we use SNMP and syslogs. We have custom Groovy scripts written to fetch all the kinds of monitoring that we need from a network standpoint. For cloud, we have a direct integration. We use LM Cloud, which gives us the flexibility to onboard cloud resources automatically without manual intervention. The tags that are in the cloud also get inherited in LogicMonitor, which helps us create dashboards and route alerts accordingly.

    How has it helped my organization?

    LogicMonitor has impacted our organization positively, and the overall impact has been huge because previously, the monitoring piece was segregated. We used SolarWinds for network monitoring, we used another tool for Windows monitoring, and cloud was managed by AWS CloudWatch or Azure Monitor. Now, all of that is combined in a single pane of view. It has become very easy from an organizational perspective to manage the workload and to give our leadership a single consolidated view of how the infrastructure looks at any point in time.

    Since bringing everything into LogicMonitor, we have seen these benefits because tool switching was one of the main reasons we wanted this done. It is now a single layer, where we integrate with ServiceNow and have all the ticketing coming from one source of information, which comes in handy. That overall leads to a reduced MTTR and MTD, which helps in the overall observability goal that we have.

    The challenges in gaining complete visibility across our hybrid infrastructure were mainly for third-party tools for which we did not have out-of-the-box integrations. We have been able to overcome them using LM Envision. It gives us the flexibility of writing Groovy scripts, with which we can talk to any third-party tool that exposes APIs. That flexibility has allowed us to overcome most of the hurdles we had in terms of gaps.

    LogicMonitor has definitely improved our team's mean time to resolve incidents. Previously, we were hopping between different tools and different views. Now that has ended. We are all on the same page with a consolidated view, which has certainly helped reduce MTTR and MTD.

    What is most valuable?

    The best features LogicMonitor offers are its properties, the way it manages tags, and the very smooth cloud onboarding. We can exclude or include resources on the basis of tags themselves. On top of that, LogicMonitor is built on a hierarchical structure where we can define credentials at a top level, which then follow down, and we can create exceptions as well. That makes automated onboarding very easy. The API exposure of LogicMonitor is also very good. The Swagger document itself helps and allows us to automate all the actions that an admin does. The integrations with different tools in terms of customizations are also strong because of the possibility of having a Groovy script written at the back end. That allows us to integrate with any tool that provides API exposure, which helps with integration overall.

    An example of an automation or integration my team built that made a noticeable difference involves the ZPE Nodegrid solution, which our company recently purchased. It uses cellular connectivity to connect to physical devices and does not depend on the infrastructure network connectivity. One of the problems we were facing was that the physical cables were often getting disconnected, and we had no way to monitor it. Since the ZPE portal itself exposes data via API, we saw this as an opportunity to onboard it in LogicMonitor. We built a custom script data source that fetches the data via the ZPE API and then posts that data to the LogicMonitor POST integration API endpoint. That gives us end-to-end visibility across all the ZPE nodes across the globe.

    Apart from this, there are good features in terms of integrations. LogicMonitor has an HTTP integration where we can publish our alerts as a webhook to any third-party tool we want to send them to. It has an integration with Teams, a built-in integration with PagerDuty, and an integration with ServiceNow. All those flexibilities help us integrate with other tools and give us a single holistic view across our IT environment.

    Regarding the accuracy and reliability of LogicMonitor's AI output, I believe the correlation has been working fantastically. From what we have seen in the last 15 to 20 days, the correlation has been absolutely brilliant. However, when it comes to AI investigation, there is still scope for improvement.

    We have been evaluating the Edwin AI tool. We are not doing the remediation part as of today because it requires Ansible. In the POC phase, we are more focused on the AI investigation and the correlation piece. The correlation piece is working great. However, in terms of AI investigation, the tool requires more work.

    What needs improvement?

    LogicMonitor can be improved in terms of correlation. There are no major options in the correlation piece. However, LogicMonitor has introduced Edwin AI, which has all the correlations that we need. We are currently evaluating that tool as well, so we might incorporate it in our future endeavors.

    For how long have I used the solution?

    I have been using LogicMonitor for more than four years now. I have been using it at this company for 18 months.

    What do I think about the stability of the solution?

    LogicMonitor is stable.

    What do I think about the scalability of the solution?

    LogicMonitor's scalability is very easy because the licensing is pretty straightforward, and the collectors are lightweight. We use 40 plus collectors ourselves, and if our workload increases, whether on-prem or cloud, it is as simple as adding new collectors and starting monitoring. The rest of the setup remains the same, so it is not an overhead for sure.

    How are customer service and support?

    Customer support from LogicMonitor is one area where they need to improve, specifically for the APAC region. The support is not that good.

    I would rate LogicMonitor's customer support a five on a scale of 1 to 10.

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

    We have used SolarWinds, AWS CloudWatch, and CA Nimsoft. We switched because we wanted a single solution that can cover our complete IT infrastructure and provide us with a single view.

    What was our ROI?

    Regarding return on investment, I can share employee-wise information. In terms of employees, when we were managing multiple tools, we had a team of 10 plus people. Now, with LogicMonitor, we are managing with only six odd resources.

    What other advice do I have?

    On a scale of 1 to 10, I would rate LogicMonitor overall an eight.

    I give LogicMonitor an eight because of all the features I mentioned, including the monitoring coverage it provides, which is pretty good. That is one of the main reasons. The flexibility it provides is another. On top of that, the cloud onboarding I mentioned is pretty smooth. I am not giving it a 10 out of 10 because there is scope for improvement in terms of dynamic thresholds and event correlations. If those things can be ingested into the LM Envision platform itself, then it will become a 10 out of 10.

    We have been evaluating Edwin AI, the product they have been pitching to us, so I am currently in the evaluation phase.

    LogicMonitor is deployed in our organization as a hybrid. We have on-prem as well as public cloud.

    We use all three major cloud providers: AWS, Azure, and GCP.

    We have not purchased LogicMonitor through the AWS Marketplace.

    We have not integrated Edwin AI with our ITSM tool as of now, as it is only in the POC stage.

    My advice to others looking into using LogicMonitor is to look at it from your use case perspective. If you are looking for a solution that you need to customize as per your needs, then LogicMonitor is one of the best candidates. However, if your expectations are more from an event correlation or AIOps perspective, look at both LogicMonitor and Edwin AI as one solution, and then compare it with other solutions you are evaluating.

    Michael Dieter

    Proactive monitoring has transformed incident response and freed our team from admin overhead

    Reviewed on Nov 11, 2026
    Review provided by PeerSpot

    What is our primary use case?

    I primarily use LogicMonitor to provide visibility into the operational status of our network infrastructure.

    On a day-to-day basis, the most use that we get from LogicMonitor's visibility is with regards to alerts and troubleshooting assistance.

    Alerts and notifications from LogicMonitor allow us to respond to specific hardware, infrastructure, or network issues before our constituent community has to notify us with an open incident through our help center.

    How has it helped my organization?

    LogicMonitor has impacted our organization positively because our networking team now gets to spend our time on network and infrastructure issues, whether that is break-fix, responding to alerts, or building and planning new deployments. Those are the things that the university and our constituents really get value from. The university and our constituents do not get any value if we have to spend our time on administrative overhead types of work. Since we are spending less time on administrative overhead and more time on the other things that are really valuable, the university and our constituent community benefits tremendously.

    LogicMonitor has impacted our team's meantime to resolve incidents. I am not able to give a specific quantifiable number, but in general, we are able to respond more quickly than we have in the past, and we are in general able to resolve situations more quickly than we have in the past.

    What is most valuable?

    Alerts and notifications from LogicMonitor are valuable since we can customize some of the content in them and set the thresholds that we choose to have value in. They are much more reliable and give us much more informed information than a report from our constituent community in a ticket.

    One of the best things about LogicMonitor for our use case is the fact that it is extremely reliable and the hybrid on-premises cloud model allows us to focus on the things that are most valuable to us, which is interacting with the monitoring data that LogicMonitor provides. We are no longer wasting our time on administrative overhead just to keep the lights on. LogicMonitor does that very well without any input from us.

    Regarding how the hybrid model has changed the amount of time our team spends maintaining the monitoring platform, I cannot give an explicit and quantitative number, but my best guess is that with products we used before LogicMonitor, we often spend more than half our time just trying to keep the products in sync, upgraded, and all the various components operational. With LogicMonitor, we probably spend more than 90% of our time interacting with our actual monitoring data and 10% or less of our time on administrative overhead.

    What needs improvement?

    There is possibly room for improvement. Because the capabilities that LogicMonitor delivers are so broad, there can be an issue with moving up the learning curve for new customers that adopt the platform. However, LogicMonitor actually does a good job right now with its online training materials to make the learning curve easier for new customers. It may actually be a challenge to do it better.

    It is always difficult for any company or service provider that iterates change and feature evolution as quickly as LogicMonitor does, because it is always difficult for the training and documentation teams to keep pace with those product feature developments.

    Regarding other improvements needed, we have been a customer of LogicMonitor for a long time. The company itself has grown and changed and continues to evolve. One of the things that has been somewhat difficult for us at times has been the inconsistent way that we are able to access and have a relationship with various LogicMonitor product and technical resources. This is understandable given the growth and evolution of the company.

    For how long have I used the solution?

    I have been a LogicMonitor customer for approximately 11 years. During that time, I have been the primary administrator and operator for our use case.

    What do I think about the stability of the solution?

    LogicMonitor is extremely stable.

    What do I think about the scalability of the solution?

    LogicMonitor is extremely scalable.

    How are customer service and support?

    Generally speaking, we have always been provided and have been able to access appropriate customer support. However, as with all companies, there are times when the support we receive is lacking.

    I would rate LogicMonitor's customer support on a scale of 1 to 10, where one is poor and 10 is the best, at eight.

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

    We have used solutions from other providers, including SolarWinds, HPE, What'sUp Gold, and ManageEngine. We chose LogicMonitor over those other solutions because we believe that overall, LogicMonitor met more of the demands of our use case and met them more effectively and returned a better value than those other solutions.

    What was our ROI?

    However, I can say that our team is only four members. In general, I believe that LogicMonitor allows us as a team of four to effectively service nearly 300 IT infrastructure elements and a campus of almost 4,000 people and several thousand more devices much more effectively than teams that may be larger.

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

    Regarding pricing, setup cost, and licensing, I am not personally responsible for the financial portion of our relationship with LogicMonitor, and I have no authority to agree to terms and conditions. However, I have participated in some of the discussions around all those things, and while it is important to always consider and understand the difference between cost and value, I would say that LM Envision can be an expensive solution, albeit one that does return a lot of value. The evolution of licensing may be something that would be good to include in how things could be improved in the future.

    Which other solutions did I evaluate?

    We did evaluate other options before choosing LogicMonitor, including SolarWinds, HPE, OpsManager, and a number of others.

    What other advice do I have?

    On a scale of 1 to 10, I would give LogicMonitor a rating of nine, where one is poor and 10 is the best.

    I would rate LogicMonitor a nine because our experience during the time we have been customers has been excellent, but I hesitate to give anyone a perfect 10.

    Advice I would give to others looking into using LogicMonitor is to understand very well your use case demands and ensure that those match very well to LogicMonitor's capabilities. That is the way that you will achieve the best value.

    reviewer2924829

    Monitoring has improved incident resolution and prioritizes critical customer alerts effectively

    Reviewed on Nov 10, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for LogicMonitor is infrastructure monitoring.

    A specific example of the infrastructure I monitor is that we monitor customers' environments for metrics as well as up and down status, and escalate to the customer or to our engineering team based on alerts.

    In LogicMonitor, I handle alert routing and escalation across customer environments by using the alert rules and escalation chains and integrations to route tickets to our ticketing system, ServiceNow. From there, a NOC engineer will escalate to the proper team via runbooks.

    How has it helped my organization?

    LogicMonitor has positively impacted my organization by allowing us to organize and alert on many different customer environments.

    The organization and alerting have allowed us to specify the response time we want for specific alerts, so we can prioritize things that are more important and have them come in quicker and reduce a lot of the noise that might be associated if we were not able to have such in-depth threshold adjustments.

    LogicMonitor has had a significant impact on my team's mean time to resolve incidents because it is a game changer from seeing alerts in LogicMonitor in real time, where everything is far more visible. We have been able to add new customers and they see alerts that we did not know about, and we are able to significantly lower something that they might not have found without using out-of-the-box thresholds or getting custom thresholds configured. We can monitor something that they are looking for that maybe they are not always able to detect right away, and we can detect it and lower the MTTR.

    What is most valuable?

    The best features LogicMonitor offers include out-of-the-box compatibility with many different technologies as well as the ability to adjust thresholds based on all sorts of folders or properties.

    The out-of-the-box integrations and flexible threshold settings have changed the day-to-day work for my monitoring team by making it easier for the team to quickly make adjustments across many customers and devices.

    In addition to the features already mentioned, I also value the folder structures and the flexibility with that to organize different companies in different ways.

    Regarding LogicMonitor's AI capabilities, I think its accuracy and reliability of output are good because from what I have seen, it is accurate and gives thoughtful data.

    I have seen a POC on LogicMonitor's Edwin AI for diagnosing root causes and orchestrating remediation, and I think Edwin does a good job at gathering all the information together and eliminating noise and getting everything boiled down to one notification or one alert where everything that comes through is actionable.

    What needs improvement?

    LogicMonitor can be improved by better determining device types to allow people that are less familiar with the technologies to be able to determine a device type when adding a device to know what LogicMonitor needs to monitor it. For example, if port 22 is open, we might know it is a network device and needs SNMP, but having LogicMonitor show that a little better would be helpful.

    For how long have I used the solution?

    I have been using LogicMonitor for six years.

    What do I think about the stability of the solution?

    LogicMonitor is stable.

    What do I think about the scalability of the solution?

    The scalability of LogicMonitor is one of my personal favorite things because we can get a collector installed in their environment and we are able to very quickly add new environments or add new devices into LogicMonitor. We simply need the collector to have access to the devices and then credentials, and we can get started.

    How are customer service and support?

    The challenges I have faced in gaining complete visibility across our hybrid infrastructure have been addressed by LogicMonitor and their support, which continually improves on the software and takes any feedback into account and tries to put that on the roadmap. If I have a good idea, they will send it to a developer and work on that and with me to get that included, or if not, find some custom monitoring or solution that works for the team.

    The customer support is one of my favorites because you can very easily chat with an engineer and get a solution, or our CSM is super helpful in answering any questions or any issues we have and making sure it gets escalated to the proper team.

    I would rate the customer support a nine on a scale of one to ten.

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

    The team has used a different solution previously, but in my six years, we have been using LogicMonitor.

    What other advice do I have?

    On a scale of one to ten, I would rate LogicMonitor a nine.

    I think LogicMonitor fits our needs very well and has the capabilities to do most of what we need it to do, which is why I rate it a nine.

    LogicMonitor is deployed in our organization in such a way that for our customers, it can be any of the options, which is very useful because we can add a collector wherever we need it to reach devices and get those devices monitored very quickly without having to put an agent on all the devices. It helps for growth ability and expandability.

    Our customers primarily use AWS, but on our internal collectors, we use AWS and Azure.

    My advice to others looking into using LogicMonitor is to give it a shot, get a POV or a POC, and see if it works for you. I think it is impressive what LogicMonitor can do out of the box, and having someone that can show you all that it can do and help would be very useful. I think it is a good idea to see how it works in action in your environment.

    Which deployment model are you using for this solution?

    Hybrid Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Jake Baddeley

    Flexible monitoring has delivered fuller observability and simple API‑driven asset visibility

    Reviewed on Nov 10, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LogicMonitor is that we're currently onboarding it as a network monitoring solution to replace another piece of software.

    What specifically made me choose it for network monitoring over the software we're replacing is that it's more flexible; we can build things as we want. We can create our own LogicModules to bring data in via APIs. It seems to be the most malleable tool that there is, and the ability to bring in other features such as cloud monitoring from other departments in the future was a big selling point, rather than just having a product that only does network monitoring.

    How has it helped my organization?

    LogicMonitor has positively impacted my organization in that the fact we could build modules and bring APIs in from different vendors allows us to have full observability. We are no longer reliant on engineers remembering to add information somewhere. The API connections are to the vendor's portal, so as soon as the product gets activated, it automatically, within 24 hours, gets pulled into LogicMonitor, and we can see the information that we need from an observability point of view.

    About how much engineer time I expect it to save, I cannot necessarily put a number on it because sometimes engineers don't do it at all, therefore there's no actual value for me to give. However, we should be able to get complete visibility of our entire estate, and having LogicMonitor do some comparisons against the number of client sites we have versus the number of firewalls we have will help us know whether the number matches or not. If it doesn't match, there should be an alert, allowing us to rectify the issue and accurately nail down what assets our clients have.

    The impact of LogicMonitor solution on my team's mean time to resolve incidents has been minimal so far, as we're onboarding, but we can see that in the near future it will be a lot easier; if we need to know what firmware versions are on certain things or which features are enabled, we'll be able to get that information right away out of one platform, which is LogicMonitor.

    What is most valuable?

    We could have custom dashboards and build dashboards as we wanted them to show exactly what we want; it's not just an out-of-the-box, 'This is the dashboard you have.' Additionally, the ability to have multiple SSO integrations allows us to get our clients to log in via SSO securely and give them access to their environment and reporting.

    The best features LogicMonitor offers are areas we are very interested in, including Edwin AI; it's part of our package, but we haven't got to that onboarding phase yet. However, Edwin AI was a big piece for us to try and help our service desks triage better and potentially get to resolution without needing to escalate into senior teams.

    Once Edwin AI is live, I would be looking for fewer escalations as a sign that it's genuinely helping the service desk. Good feedback from the team is what we're looking for, but ultimately it's fast resolution for the client that makes the client happy.

    I just want to add the ability that the feature is there for us to add our own modules and ultimately our own features.

    Regarding LogicMonitor's AI capabilities, I don't have specific thoughts on its governance and security, but the entire product had to go through our entire governance process, and everyone seems to be happy with it.

    What needs improvement?

    Regarding how LogicMonitor can be improved, specifically for us, the out-of-the-box integrations for PSAs, specifically ConnectWise Manage, seem to be a very light version, in that it takes a box of, 'We integrate,' but it doesn't actually integrate the way other network monitoring products do. It's not as fully fledged as it could be.

    I would like to add more about the needed improvements, as we currently have it open with our onboarding partner within LogicMonitor. Specifically, out-of-the-box, the default integration only adds a note to a ticket when it creates it, and then as soon as the escalation has cleared, it will just change the ticket status, with no notes in the ticket whatsoever. We then have to go into LogicMonitor and find the alert to learn what actually rectified it, when it should just be in the ticket in the PSA.

    For how long have I used the solution?

    We are currently onboarding, and we're about two months in.

    What do I think about the stability of the solution?

    LogicMonitor has been stable so far.

    What do I think about the scalability of the solution?

    I believe the scalability of LogicMonitor depends on how the user, such as ourselves, builds and designs the product.

    How are customer service and support?

    Customer support is okay. On a scale of one to ten, I would rate the customer support as a seven.

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

    We previously used a different solution: Auvik. Auvik was pretty much just an out-of-the-box solution, and we needed something better that would give us more observability, and that's exactly what LogicMonitor does.

    How was the initial setup?

    Regarding the challenges I have faced in gaining complete visibility across our hybrid infrastructure, I don't think we've delved into the Envision platform that much as part of our onboarding. However, it's been pretty much self-driven from our side; we knew exactly what we wanted and we have the expertise to get the information and make LogicMonitor do what we want it to do.

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

    My experience with pricing, setup cost, and licensing was fine; I just tried to drive a hard deal, but our procurement dealt with LogicMonitor, and it was all nailed down. I think licensing was fine, and as for setup cost, I don't get involved in the numbers that much, but I think there were some comments about professional services time.

    Which other solutions did I evaluate?

    Before choosing LogicMonitor, we evaluated other options, including Domotz; however, nothing really compared in terms of licensing and feature set.

    What other advice do I have?

    On a scale of one to ten, I would rate LogicMonitor overall as an eight.

    The reason I give it an eight is that nothing's perfect, so it could never be a ten, and due to just a few niggles in the process of onboarding, it's not a nine.

    LogicMonitor is deployed in our organization via public cloud in the UK.

    As for which cloud provider we use, we are a Microsoft house, so most of our infrastructure will be Azure.

    The advice I would give to others looking into using LogicMonitor is to make sure you explore all avenues and think broadly about what you could achieve with the product, as it is a lot more versatile than you'd ever think.

    Amit Bhavar

    Centralized monitoring has reduced incident resolution time and improves cross-platform visibility

    Reviewed on Nov 10, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LogicMonitor is configuration and alert configuration. I use LogicMonitor for configuration and alert configuration day-to-day to manage multiple platforms. This is a core use of LogicMonitor.

    How has it helped my organization?

    LogicMonitor has positively impacted our organization because we monitor almost 50 platform applications that are reliable on us, and we are reliable on LogicMonitor, providing notifications when services go down, such as multiple 404 or 500 errors. We see a response and correct improvement regarding specific metrics.

    We get alerts that allow us to respond in minutes rather than hours and help prevent incidents from affecting users. A main challenge has been gaining consistent visibility across on-premises, cloud, network, and application environments without relying on multiple monitoring tools; the Envision platform has helped provide a centralized view into infrastructure health, alerts, and performance while achieving complete visibility depends on proper configuration and integration of all devices.

    LogicMonitor has helped us reduce our mean time to resolve incidents by providing timely alerts, centralized visibility, and useful diagnostic information that enables the team to identify potential causes faster. LogicMonitor is helping other platform members and platform owners as well.

    What is most valuable?

    The best feature LogicMonitor offers is monitoring, and we get timely alerts, so we do not need to wait. Those real-time alerts instantly notify the platform teams when a service or job goes down, helping us respond quickly.

    I find the AI generally accurate and reliable, especially for alert detection, alert correlation, and identifying potential root causes, but I would suggest understanding the features before relying on AI.

    Dynamic Service Insights improve our understanding of digital services by showing relationships and dependencies across infrastructure components, helping us identify service impacts faster, prioritize critical alerts, and make better decisions during incident troubleshooting, making it helpful.

    What needs improvement?

    The configuration of scheduling alerts should be more user-friendly. To make LogicMonitor better, I suggest improving reporting since I see very few options for reporting. Everything is good, including the dashboard, configuration, and alert configuration, but reporting can be improved with more features.

    For how long have I used the solution?

    I have been using LogicMonitor for almost two years.

    What do I think about the stability of the solution?

    LogicMonitor is stable.

    What do I think about the scalability of the solution?

    LogicMonitor is highly scalable and can support growing and complex IT environments, making it easy to add new devices while maintaining centralized monitoring.

    How are customer service and support?

    Customer support is excellent; we have connected multiple times and received solutions while chatting with the assigned technician, who provides a variety of options. I would give customer support a rating of nine.

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

    We used to use SolarWinds, which was good, but there were issues with configuration, leading management to decide on LogicMonitor for a new experience.

    What was our ROI?

    I see a return on investment as time-saving because we monitor multiple platforms without opening each application individually, making it efficient. We need fewer people to manage all the platforms, so this is relevant and time-saving.

    Which other solutions did I evaluate?

    Before choosing LogicMonitor, we evaluated the product based on a colleague's positive experience and found it user-friendly.

    What other advice do I have?

    On a scale of 1 to 10, I would rate LogicMonitor a nine out of 10. I rate it a 9 because I am cutting one point for expecting more options in reporting.

    I have not used LogicMonitor's AI features enough, but we would love to gain more knowledge and advancements from the company.

    I advise others looking to use LogicMonitor to define monitoring requirements clearly and spend time properly configuring alerts and dashboards to align with operational priorities.

    Akash Biradar

    Proactive monitoring has reduced outages and now speeds incident resolution with automated alerts

    Reviewed on Nov 10, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LogicMonitor is to monitor our infrastructure and all the applications. I monitor our infrastructure, including network servers and databases, and LogicMonitor helps us catch issues such as multiple network outages in different locations. It captured these issues, and with our integration with ServiceNow, we were able to identify the issue and resolve it immediately.

    In terms of applications, I monitor multiple web applications where our customers log in and request services. Critical applications are monitored through IIS logs using LogicMonitor, such as 400 and 500 errors where web applications are unavailable to users, allowing us to identify these issues proactively before they impact multiple locations or users. Our team investigated and resolved the issues as soon as possible.

    I have integration with ServiceNow directly through an integration between LogicMonitor and ServiceNow that creates incidents automatically.

    Regarding my main use of LogicMonitor, I appreciate that we can monitor multiple things, including services and network traffic for various use cases. LogicMonitor provides multiple Logic Modules where I can configure and monitor any data source, allowing us to monitor IIS logs, SSIS jobs, and schedule tasks by creating Logic Modules.

    I can also monitor events by having event sources in LogicMonitor.

    How has it helped my organization?

    LogicMonitor has positively impacted our organization as it was crucial. Without this monitoring tool, I quickly realized that we would not have identified issues as effectively, allowing us to save business time and revenue by identifying problems before they affected operations.

    There was a significant network outage during a time when no one was available on shift, but with LogicMonitor, we received alerts and were able to identify the root cause. Our team acted to resolve the issue before business users raised an incident.

    LogicMonitor has significantly expedited our incident resolution times because it automatically checks issues, triggers alerts, creates incidents, and notifies the team, which eliminates manual work for the IT operations team, enabling us to address issues directly.

    What is most valuable?

    The best features LogicMonitor offers are the alerting, integration, and dashboard capabilities, which allow me to easily look into issues at a glance.

    The feature that saves our team the most time day-to-day is the alerting part, as it reduces manual effort in generating reports for multiple teams in terms of capacity management, which helps them adjust CPU memory or disk capacities before they impact our operations. Additionally, it automatically discovers new devices, saving our time since our integration with CMDB means we do not manually add devices to LogicMonitor, which populates them automatically when discovered.

    In terms of features, the best is the capability to monitor logs and Logic Modules, providing us with the flexibility to monitor any kind of source data.

    What needs improvement?

    I think LogicMonitor could improve by offering training or simplifying Logic Module configurations, as they are quite challenging, and providing out-of-the-box scripts could be very helpful.

    Additional improvements should include providing agent-specific, in-depth visibility for monitoring, including enhanced root cause analysis.

    Regarding accuracy and reliability, I pinpoint that alert insights give accurate suggestions 80 to 90 percent of the time, but added features could help achieve 100 percent reliability.

    I have faced challenges in gaining complete visibility across our hybrid infrastructure, such as grouping devices and creating Logic Modules, which can be complex, but once properties are set at the group level, it simplifies the monitoring across devices.

    For how long have I used the solution?

    I have been using LogicMonitor for more than one and a half years.

    What do I think about the stability of the solution?

    LogicMonitor is stable. In the event of downtime or issues, the service sends notifications to keep us informed, and they plan maintenance during non-business hours.

    What do I think about the scalability of the solution?

    LogicMonitor scales well as we add more devices or users. While it is license-based for resources at the device level, there is no limitation on user counts, ensuring good scalability.

    How are customer service and support?

    I find the customer support to be very good. They provide efficient direct assistance and can schedule calls for immediate resolution of any issues. I would rate the customer support a perfect 10 out of 10.

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

    Not in this current organization, but at my previous job, I utilized SolarWinds. Within this organization, LogicMonitor has proven to be very useful.

    What was our ROI?

    I conclude that we save time by using LogicMonitor to identify potential issues before they escalate and impact the business, which ultimately saves money and reduces the need for more employees.

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

    My experience with pricing, setup cost, and licensing has been overall positive, as LogicMonitor effectively monitors everything in one place with excellent customer support.

    Which other solutions did I evaluate?

    Before selecting LogicMonitor, I evaluated options including SolarWinds, Dynatrace, and ManageEngine. I chose LogicMonitor due to its comprehensive infrastructure and application monitoring and favorable cost negotiations.

    What other advice do I have?

    I would rate LogicMonitor a nine out of ten because it performs well in overall infrastructure and application monitoring.

    I have been using LogicMonitor for over a year and have never encountered any security issues. I can confirm it has good security protocols, and the LogicMonitor team is very aware of security concerns.

    Since Edwin AI is license-based, we have not used it yet, but we are considering it.

    To others considering LogicMonitor, I recommend exploring its features and integration capabilities, keeping pricing and requirements in mind, as it is a worthwhile consideration for organizations seeking reliable IT monitoring.

    reviewer2924193

    Monitoring has improved troubleshooting with detailed interface graphs and NetFlow insights

    Reviewed on Nov 09, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for LogicMonitor involves troubleshooting using graphs and NetFlow. During a troubleshooting situation, I check to see if there is an interface causing a bandwidth bottleneck or observe how many connections are flowing out using NetFlow.

    What is most valuable?

    The best features LogicMonitor offers include interface statistics and NetFlow enablement. The interface visibility and NetFlow capability make it easier for my team to troubleshoot and pinpoint issues. The automatic configuration backup is also a valuable feature.

    LogicMonitor has positively impacted my organization by enabling us to create custom graphs in dashboards view to quickly see bandwidth utilization. The configuration backup has helped when trying to determine when the last change happened and what caused the issue for the customer. LogicMonitor has helped to drastically narrow down the amount of bandwidth consumption for a service utilizing the NetFlow statistics section, which has impacted my team's mean time to resolve incidents.

    What needs improvement?

    If I had to pick one area that could be improved, it would be the ease of use with the new user interface, as it is a change but does take some time to get used to.

    For how long have I used the solution?

    I have been using LogicMonitor for eight years.

    What do I think about the stability of the solution?

    LogicMonitor is stable.

    What do I think about the scalability of the solution?

    LogicMonitor's scalability is easy to manage, as I can add a collector within the group relatively easily and quickly.

    How are customer service and support?

    Customer support is good. I would rate the customer support a nine.

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

    We do not use a different solution.

    What was our ROI?

    I have seen a return on investment in terms of time saved due to the amount of information that is provided per data source. Approximately half an hour per incident is the amount of time that my team saves.

    Which other solutions did I evaluate?

    We did not evaluate any other options before choosing LogicMonitor.

    What other advice do I have?

    On a scale of one to ten, I would rate LogicMonitor a nine. I rate it a nine because it is easy to use, the dashboards are clean, and the graphs facilitate easier viewing of historical data.

    LogicMonitor is deployed in my organization in a hybrid and on-premises setup with failover collectors and collector groups. For the hybrid part of our deployment, we use a proprietary KVM. I do not recall any visibility issues across the hybrid infrastructure and the Envision platform has addressed these challenges.

    The advice I would give to others looking into using LogicMonitor is that the collector works best on a Windows server and that the folder structure is good.