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.
LogicMonitor is the leading SaaS-based, performance monitoring platform for Enterprise IT. With coverage for thousands of technologies, LogicMonitor provides granular visibility into infrastructure, cloud and application performance across hybrid and cloud infrastructures. Automated device discovery, preconfigured alert thresholds and rich, customizable dashboards, come together to give IT teams the speed, flexibility and actionable insights to succeed in today's competitive markets.
Simply install a LogicMonitor Collector and add devices via network scan, bulk add, or orchestration tool of choice. The Collector automatically recognizes devices in your infrastructure and immediately begins collecting performance metrics. From there, use LogicMonitor's flexible data collection mechanism to pull metrics from virtually any device or API, then create graphs, dashboards, and custom alerts to quickly view application status and analyze trends.
Highlights
End-to-end AWS Migration Monitoring: Ensuring migrated resources perform as intended with panoramic visibility into on-premises and AWS services in a single-pane view.
Agentless Collector provides hybrid and multi-cloud visibility in minutes, not days or weeks. Low cost of ownership as teams are not having to constantly upgrade agents to support new features. Devices are recognized and instantly auto-configured based on best practices.
Complete visibility into cloud services: visualize cloud performance, availability, and ROI alongside your monitored on-premises infrastructure for a complete view into hybrid and multi-cloud environments.
Automated device configuration for 2,000+ technologies: LogicMonitor detects what to monitor, what to graph, and what to alert on, automatically, to give you intelligent, actionable monitoring.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on the duration and terms of your contract with the vendor, and additional usage. You pay upfront or in installments according to your contract terms with the vendor. This entitles you to a specified quantity of use for the contract duration. Usage-based pricing is in effect for overages or additional usage not covered in the contract. These charges are applied on top of the contract price. If you choose not to renew or replace your contract before the contract end date, access to your entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
You buy this platform as a contract made up of separate units you combine to fit your environment. Core infrastructure counts by resource type, including cloud, IaaS, PaaS, containers, and wireless access points. Application monitoring bills separately by metrics, synthetic tests, and traces. Log and inspector units bill per GB, with monthly, yearly, or unlimited retention choices that affect price. Other independent add-ons cover config, service insight, website, SaaS, cost optimization, AI, and integration options. Support and extra usage come as separate quoted lines. You scale by adding units per category as your needs grow.
Top-of-mind questions for buyers
What counts as one unit for the core infrastructure and cloud dimensions?
Units count by resource type. One on-prem monitored device, one cloud IaaS resource, seven cloud PaaS resources, or five wireless access points each equal one unit. For containers, seven pods equal one unit. Your account team estimates the unit count that fits your environment.
How do the log and inspector retention choices change what I pay?
LM Logs and LM Inspector bill per GB of data. You choose one-month retention, one-year retention, or unlimited retention for logs. Longer retention lines cost more because data stays stored longer. You can filter data before ingestion to control the GB volume you are billed for.
How do the application monitoring dimensions combine on my bill?
APM bills across three separate lines. LM APM Metrics counts datapoints pushed via API or scraped. LM APM Synthetics counts synthetic test invocations. LM APM Traces counts application spans. Each meters independently and adds to your invoice, so the metric matching your heaviest usage drives that portion of cost.
Request a private offer to receive a custom quote.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Automatic recognition and configuration of 2,000+ technologies with preconfigured alert thresholds and best practices-based setup without manual intervention
Agentless Monitoring Architecture
Agentless Collector deployment enabling hybrid and multi-cloud visibility with reduced operational overhead and no requirement for continuous agent upgrades
Unified Multi-Environment Visibility
Single-pane-of-glass monitoring across on-premises, hybrid, and multi-cloud infrastructures including AWS services with panoramic performance visibility
Flexible Data Collection Mechanism
Capability to pull metrics from virtually any device or API with support for custom graphs, dashboards, and alerts for application status analysis and trend identification
Performance Forecasting and Customizable Dashboards
Built-in performance forecasting capabilities combined with rich, customizable dashboards and full reporting functionality for actionable infrastructure insights
Full-Stack Observability
End-to-end monitoring of AWS applications and infrastructure from code level insights to end-user tracing with robust configuration options
AI-Powered Root Cause Analysis
Davis AI engine performs precise root cause analysis showing causation and correlation to drive automated remediation and reduce mean time to resolution
Generative AI Application Monitoring
Real-time monitoring, optimization, and security of Generative AI applications, LLMs, and agentic workflows with cost optimization, hallucination detection, and PII leakage guardrails
Runtime Application Security
Built-in Runtime Application Self-Protection that autonomously detects and blocks threats across AWS-hosted applications with real-time vulnerability and threat detection
AWS Native Integration
Out-of-the-box compatibility with 100+ AWS native technologies including EC2, Lambda, ECS, EKS, Fargate, Bedrock, and EventBridge for seamless deployment and correlation
Unified Observability Platform
Comprehensive visibility across applications, infrastructure, logs, databases, networks, and digital experiences through a single-pane-of-glass interface
AIOps and Machine Learning
AIOps enhanced with machine learning capabilities to simplify management of distributed environments and automatically prioritize alerts to reduce alert fatigue
Automated Instrumentation and Dependency Mapping
Automated instrumentation with dependency mapping and service relationship views to identify multi-level relationships across services
Open-Source and Container Support
Support for open-source frameworks, container technologies, and third-party integrations for cloud-native environments
Rapid Deployment
Quick installation and easy configuration designed for rapid time to value with minimal setup complexity
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.