LogicMonitor Reviews

My main use case for LogicMonitor is to monitor all the networking devices deployed in our on-premises network.

Whenever the network goes down, I receive an alert from LogicMonitor indicating that a node or device is down, which allows me to check and troubleshoot the device physically or review the logs to determine the issue, how many packets were dropped, and other relevant details.

LogicMonitor provides me with the total number of devices present in the network and allows me to see how it monitors the networking scenario.

LogicMonitor offers the best capabilities, including capturing the node status, checking whether the network is down or up, and seeing how the network is actually working.

I can create customized widgets in the dashboard, which helps me check on networking equipment whether they are servers, switches, Layer 3 devices, access devices, printers, or anything else. If any device goes down, it alerts me immediately.

In LogicMonitor, I can view the node, configure it, manage the bandwidths, and if a node is down, I can manually change the path.

After deploying LogicMonitor, I can get information about the device condition within one to two seconds and receive alerts. Yellow alerts appear first, and when they exceed a set interval of time, red critical alerts come through, which helps my organization check on critical issues.

The alerts and emails sent to customers could be improved and delivered more directly.

The interface is acceptable, and I do not have any suggestions for it.

SNMP configurations and deployment guides could be more user-friendly for engineers deploying the solution.

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

The main challenge occurs when LogicMonitor goes down while the physical device is actually up. Sometimes physical devices are functioning properly, but LogicMonitor is unable to detect this, which results in unnecessary ticket generation that my team must address.

Occasionally, the monitoring does not function properly, and minor issue tickets are generated unnecessarily, requiring my team to resolve them.

LogicMonitor is a properly scalable solution.

Customer support is good and they respond on time, though they could improve their services further.

We were previously using SolarWinds, though I was not fully aware of its complete capabilities. My company switched to LogicMonitor with the decision that it would reduce downtime.

I have seen a return on investment for the employees involved. When manual work was being performed, downtime was very high and significantly impacting the business. After deploying LogicMonitor into the hybrid cloud environment, money was saved. Ultimately, LogicMonitor saves my organization time. Deploying LogicMonitor into the hybrid cloud in our setup achieves both objectives of saving money and saving time.

For licensing, I raise queries and take approval from the owner or client. They handle the licensing portion and manage pricing decisions. Clients care about the pricing, and they provide the license for us to work with.

I am still exploring the AI capabilities of LogicMonitor and learning about cloud solutions. Dynamic services does not interrupt my work, and I follow its processes accordingly.

LogicMonitor has helped me resolve issues faster. As alerts come through, I directly check the interfaces or nodes that are down, and I examine the mean time to resolution to determine how I can bring the device back up. I can also push configuration changes if a device is completely down, which is the best part.

When using LogicMonitor, I recommend creating customized widgets according to your specific problems and solutions, and placing all critical nodes on the same dashboard for proper monitoring.

LogicMonitor partners with us and checks everything including business support and customer satisfaction alongside the timeframes in which clients can be satisfied.

My overall review rating for LogicMonitor is nine out of ten.

Hybrid Cloud

Google

I work as a consultant providing solutions to customers, and I use cloud native services for monitoring. I primarily recommend CloudWatch, and if the customer has a preference for a third-party tool, I provide solutions for DataDog or other services.

I function as an architect in cloud services, particularly hybrid cloud. I need these tools and services that I always offer to customers. When I design solutions, I provide a monitoring solution and recommend these services.

I have multiple customers to whom I have recommended monitoring tools. I have worked on many projects including McAfee, CarMax, AMC, and American Media Corporation. I have recommended these services across different projects.

I have been using CloudWatch for more than ten years. I primarily recommend CloudWatch because customers do not want to spend additional money on other tools. I would recommend a native service so they can save cost. AWS is introducing synthetic monitoring for applications, which is crucial for precise monitoring. AWS X-Ray and Amazon QuickSight integration makes CloudWatch a centralized monitoring tool.

LogicMonitor is used for application insights monitoring, collecting, analyzing, and visualizing data from application infrastructure, and identifying errors. It boasts features including real-time alerting, log ingestion, and visualization dashboards. LogicMonitor offers microservices monitoring and more features in terms of alerting and support compared to CloudWatch, but it is costlier.

CloudWatch's integration is very quick. Since these are all connected internally with the AWS backbone network, no significant integration is needed. I simply enable CloudWatch across AWS services. This centralized tool also offers logs query through Amazon QuickSight, creating visual alert dashboards.

Technical support is obviously good in LogicMonitor, rating it a ten. CloudWatch's support rates at eight to eight and a half.

LogicMonitor excels in performance monitoring, tracking performance, bolstering security, and real-time alerting. However, LogicMonitor can struggle with high ingestion costs, data retention limitations, delayed alerts, and missing critical security events.

There are several areas for LogicMonitor to improve. Overly sensitive real-time monitoring leads to too many alerts, which could be managed via AI to reduce false positives. Cost optimization by offering discounts to enterprises could help manage pricing concerns. LogicMonitor should become more centralized to handle heterogeneous environments, as plugins sometimes do not work across platforms like F5 firewall. Complexity and steep documentation also need simplification.

LogicMonitor might struggle with delayed detection, as alerts may not be immediate under high infrastructure load. Other weaknesses include ingestion costs, data retention limitations, missing critical security events, real-time analysis gaps, and delayed alerts.

I have been working with this solution for more than seven years.

Technical support is obviously good in LogicMonitor.

I have experience with AWS, DataDog, and CloudWatch. LogicMonitor offers logs monitoring capabilities. Integration-wise, LogicMonitor also has an agent that can be installed on a particular service, and all data gets populated on LogicMonitor. I can see all the documents and everything. I can also integrate with ServiceNow and other platforms. The choice depends on how the customer is using their infrastructure to monitor.

The main consideration is cost optimization. Some customers want to optimize their cost for their infrastructure, so I would recommend CloudWatch. For other customers who are open to spending additional funds, I would recommend LogicMonitor or DataDog.

LogicMonitor provides application dynamic monitoring and application insights monitoring. It collects, analyzes, and visualizes data from application infrastructure and identifies errors. I can track performance and bolster security with microservices monitoring using LogicMonitor.

LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support. However, cost is the only matter of concern. LogicMonitor has more features compared to CloudWatch.

I find a few weaknesses at the moment. Alert fatigue sometimes occurs when there is a peak load on the AWS infrastructure, and LogicMonitor takes some time to alert. High ingestion cost is another concern. Data retention limitations present challenges because sometimes I need to check alerts from six months back, but the data retention is only one week, maximum ten days, or one month. Missing critical security events is an issue where some non-critical logs get flagged as false positives. Real-time analysis is required but sometimes only works in a few services and not in all services. Some security breaches cannot be identified through LogicMonitor because those logs are not captured when something happens to a particular service. For example, if an application has vulnerabilities, the application acts like a legitimate service, but I do not know that. LogicMonitor hardly identifies these things. Even when I collect the logs, I cannot exactly know if the log is the faulty one. I think most service vendors are trying to implement AI models to identify this, but it takes some time to get this done. I think LogicMonitor is also trying to do this.

Delayed detection is a significant issue. Because of high load on the infrastructure, sometimes I will not find the alert immediately. It takes five to ten minutes, and after the impact happens, I get notified five to ten minutes later. This delayed detection is the main issue.

Real-time monitoring is required, and that means overly sensitive alerts with too many false positives. If LogicMonitor can use AI or other methods, they can remove those duplicates and maintain the actual alerts. They can identify false positives prior and prevent them by nullifying those things. Cost is another area where LogicMonitor can provide discounts to enterprise companies using most of their infrastructure to reduce their license cost. Complexity should be addressed because if a customer has multiple heterogeneous environments, LogicMonitor should be centralized to get all the data and do the log monitoring. Sometimes some plugins and agents do not work on few services. For example, on F5 firewalls and on-premises firewall physical servers where I want to get some logs, those do not get logged on LogicMonitor. A lack of context and understanding of the tool is also an issue. The documentation should be more clear and simple in simple language. When I first see the documentation, it is pages upon pages, and it is very difficult to understand everything until I gain some control of that tool. The documentation should be reduced so people can easily use that tool. Instead of going very complex, straightforward guidance should be required. My overall rating for this product is nine out of ten.

My main use case for LogicMonitor is managing network and switches. We have set up our office in various sites around the world, and LogicMonitor helps us in monitoring the switches, the overall network, the ISP's state, and everything about the network. It's all managed by LogicMonitor.

If there are any alerts or if any switch goes down, we get an instant email through ServiceNow to our mailbox.

The best features that LogicMonitor offers include integration with various platforms and the UI. LogicMonitor has positively impacted my organization by reducing network monitoring time and the overall time spent on reviewing the switches and network-related concerns.

Now we simply rely on the alerts, the emails, the priority of those alerts, the warning, and the severity; everything is managed by LogicMonitor. We don't have to work extensively on it anymore. We rely on the tool and the triggers.

I think if LogicMonitor offered a desktop app or something that can be installed on the machine, it would be really helpful.

Additionally, it times out after every couple of minutes, perhaps 20 or 30 minutes. If there were a way that it could continue running, whether as an app or as a site in the background, that would be helpful.

I have been using LogicMonitor for 2.5 years.

LogicMonitor is stable.

LogicMonitor's scalability is good; it is something that we can work on, and as I already mentioned, we are still working on it.

My experience with pricing, setup cost, and licensing was all feasible; it wasn't that expensive.

My advice to others looking into using LogicMonitor is to go for it and use it; it's worth trying.

Dynamic Service Insights doesn't affect us in any way; it's just that the overall concept of managing the networks is working fine for us. LogicMonitor doesn't help in resolving MTTR; it only manages the network and gives alerts if there is an issue. Once there is an issue, if it's something that can be resolved onsite, we have to send engineers onsite. The ticket resolution is not managed by LogicMonitor. I'm not sure exactly how the cost was saved, but it has helped us in terms of viewing the network from one single tool. We don't have to keep switching from one to another. We have given access to more than 10 or 15 employees already, with two from network and the rest from the other teams.

My overall rating for LogicMonitor is 9 out of 10.

Private Cloud

Microsoft Azure

I am using LogicMonitor for accessing devices in real time to monitor any critical or major alerts. We use LogicMonitor to map alerts to ServiceNow to generate tickets on a real-time basis. This is one of the excellent applications and portals I have used in my career, and it is a strong product for any enterprise, small, or medium-sized company that needs to handle or monitor large-scale devices, cloud devices, or servers.

Regarding the use of Admin AI for diagnosing root causes and orchestrating remediation, I have not yet implemented this. My cloud AI team or ECI AI team may be working on this capability. I need to investigate this further in the future. Currently, I use LogicMonitor for real-time monitoring to check for any critical outages occurring in networks or system servers. I can also fetch reports from LogicMonitor to obtain all the data for a particular client as needed for my company's perspective during data preparation. I refresh reports from LogicMonitor regularly, and I need to check further with my cloud team regarding the AI functionality. As of now, I am not using that option.

I use LogicMonitor for accessing devices in real time and monitoring any critical or major alerts. We map alerts to ServiceNow to generate tickets on a real-time basis. This is one of the excellent applications and portals I have used in my career. It is a strong product for any enterprise, small, or medium-sized company that needs to handle or monitor large-scale devices, cloud devices, or servers.

I can also use the old UI, which is still available to me where the setup is almost the same, although the overall interface is a bit older. Apart from that, there are no issues. We can set up the time zone in the application according to standards, such as EST or any other zone we require.

Based on my experience with LogicMonitor, I dislike a particular design aspect, and I am uncertain whether this design was created by my company or if it is a global configuration. For any particular client, we use network and system or server devices, and these are mapped in the resource or resource mapping group. For those resources of a particular client, we can access all the details, including all thresholds and real-time monitoring. For example, for a client using five network devices and five servers, they may have some ISP circuits or WAN circuits being used by that same client. Whether there is a single circuit or dual circuit depends on the environment or the client setup. We have to search in a different option within the same resource tab to access only those circuit details for all clients. It would be beneficial if there were an option available to add ISP circuit details for a particular client within the same platform, as that would save time accessing it.

When we open a particular monitoring tab in LogicMonitor, we have to open a duplicate LogicMonitor window in the same browser. Based on my understanding, this may be by design, but if it were possible to add those details within the same client environment or client setup in the same tab, that would reduce the time required to access or troubleshoot during any outage. Additionally, I found that LogicMonitor needs some improvement in threshold monitoring. For example, when we monitor a particular device with a temperature issue or high-temperature problem, sometimes I observe that in real time when I log into the device, the temperature shows something that does not accurately match what is displayed on the LogicMonitor platform. That needs fine-tuning.

I have been working with LogicMonitor for the last eleven months.

I have not experienced significant lagging, crashing, or downtime with LogicMonitor during the last eleven months. When I first started using this application, I used it for approximately one to one and a half minutes, and during that time LogicMonitor became unresponsive after refreshing the window. However, it returned to normal operation after that. That is my only experience with such an issue.

I have already mentioned that LogicMonitor is very scalable and useful for large enterprise networks and large enterprise companies. I can confirm that it can be very helpful for all companies.

I have not had to contact technical support yet. I completed a certification through my organization as part of the LM Getting Started Batch 2025 LogicMonitor Basic Training. I learned a lot from that training, including basic modules about LogicMonitor, which was helpful for gaining knowledge. I did contact my company's technical support or Enterprise Tools team when I found some issues such as multiple alerts flooding from LogicMonitor or if an alert had already been removed from the system but still appeared in LogicMonitor, and those issues were resolved. I have not yet contacted any LogicMonitor technical team directly.

Regarding alternatives to LogicMonitor, I can say that in my previous organization at Unify CX, I used PRTG as a monitoring tool, the PRTG Network Monitor. I have also used SolarWinds as a real-time monitoring tool. However, I can confirm that LogicMonitor is one of the best platforms for any organization to use for network, cloud, or system monitoring. It is user-friendly and the overall structural setup is very strong.

Regarding the initial deployment of LogicMonitor, I found it not very difficult, but the setup was quite new to me because I was using it for the first time. Within one or two days, I understood most of it, and as I continued using it more, I gained knowledge about everything, including the setup, access, how to check alerts, alert tuning in this setup, how to check if any alert is in SDT, checking graphs, and all the configurations we have in this setup. It is truly impressive.

LogicMonitor does not require any maintenance on my end. We do not involve ourselves in the maintenance, but there is a team in my organization called the Enterprise Tools Team (ETT). They handle the maintenance portion of the application. We do not have much involvement in it currently.

Regarding pricing, I do not know much about it. I do not have much knowledge about the pricing or how much it costs to a particular organization because I work as a NOC engineer, so my focus is to monitor the network and system components from LogicMonitor on a twenty-four-seven basis. I wish to know more if you want to share that information with me, but I do not have that knowledge currently.

Currently, there is a new UI option that is an advanced UI version for monitoring the application.

Regarding dynamic service insights for real-time visibility, I apologize, but I do not understand what you mean by dynamic service. Could you please elaborate a bit further? As of now, I am not using that service, so I cannot tell you elaborately about this topic. On a scale from one to ten, I would rate LogicMonitor as a nine overall because I cannot provide a ten, as there is always a chance to improve. My overall review rating for LogicMonitor is nine out of ten.

LogicMonitor is used to monitor all security network appliances and system appliances, including servers, Linux systems, networks, appliances, firewalls, routers, and switches. It also monitors cloud infrastructure, including VNet, cloud services, and cloud connectivity solutions such as Azure ExpressRoute, and extends down into individual configurations such as BGP sessions and IPsec tunnels. This monitoring capability serves multiple sectors through a managed service provider model, providing services to finance, real estate, and other industries.

The LogicMonitor alert UI is valuable because it correlates alerts, preventing unnecessary panic by allowing me to review the alert dashboard instead of logging into each individual device or relying on unreliable monitoring tools. LogicMonitor is very reliable compared to many other monitoring tools I have used. Each individual BGP session, IPsec tunnel, and interface is captured accurately, and the logs are highly reliable.

The impact of LogicMonitor on management of service health and business risks is significant. In my previous company, after implementing LogicMonitor, most issues were resolved within one hour without requiring senior engineer intervention, as junior engineers could resolve issues by reviewing the alert information and understanding what occurred.

The remediation functionality could be improved. Given the power of the tool, implementing a one-click option to change configurations via SSH or API access to appliances would be beneficial. The remediation component could also include automation capabilities.

I have been working with LogicMonitor for one and a half years.

Before LogicMonitor, I used a different tool for log search, though I cannot recall the name. The main differences between previous tools I used, such as SolarWinds, and LogicMonitor are that previous tools do not display everything in one dashboard. They typically show a number of devices and alerts, and to see alert details, I had to click through to see more information. LogicMonitor displays everything in one comprehensive dashboard, which prevents me from forgetting what I see when navigating away from a link.

I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free resources but not as powerful as LogicMonitor. For small businesses that want to utilize LogicMonitor and are just starting out with limited customers, a pricing model targeted to this segment would be beneficial, perhaps at three or two dollars per device per month.

LogicMonitor has advanced AI and AIOps capabilities for diagnosing root causes that I have not yet utilized. LogicMonitor has positively impacted my team's MTTR for incidents. When one switch goes down, multiple alerts trigger not only from that switch but also from peer switches. Suddenly, a hundred alerts may appear, but the issue can be narrowed down by identifying the down device instead of processing all the noise. One switch showing as red means I can ignore the other alerts coming from other switches, which is very helpful as the entire team can see this information in one dashboard. I rate this product a ten out of ten.

Public Cloud

Microsoft Azure

My main use case for LogicMonitor is real-time monitoring, alerting, performance tracking, and infrastructure visibility.

In LogicMonitor, I can create a dashboard to monitor proactively, manage alerting, capacity planning, and operational visibility. Our network team monitors bandwidth utilization, device health, and server availability to prevent outages, making this one of the best use cases with LogicMonitor.

LogicMonitor is good for dashboards and reporting, allowing us to easily track the real-time performance of servers and network devices, as well as create custom reports for operational visibility, representing the main cases we are working with.

Day-to-day, I rely on real-time monitoring, which includes monitoring network devices such as routers and servers for CPU utilization and server memory use. Alerts are triggered when server disk usage reaches 90%, which is beneficial for monitoring alert management.

In addition to the aforementioned features, LogicMonitor provides log and event correlation, helping to correlate logs, alerts, and metrics for troubleshooting. It aids in investigating application slowdowns by checking logs and CPU spikes together, supporting day-to-day operations through real-time monitoring, alerting, dashboard, reporting, auto-discovery, topology mapping, and proactive infrastructure management.

In our organization, LogicMonitor is deployed to provide centralized monitoring of infrastructure, network devices, server applications, and cloud resources, allowing us to monitor routers, switches, and servers from a single platform while enabling proactive alerting and operational visibility across hybrid IT environments.

The best features of LogicMonitor include alerting and escalation, triggered when CPU utilization exceeds 90%. Additionally, topology mapping provides visual dependency mapping of infrastructure, mapping relationships between servers, network devices, and applications, leading to faster issue detection and troubleshooting, along with centralized operational monitoring.

LogicMonitor has positively impacted our organization by allowing early detection of memory spikes on production servers, enabling the team to resolve issues before they affect service, and making day-to-day work much less stressful for us.

LogicMonitor helps improve outcomes, including improved infrastructure uptime, faster issue resolution, and better visibility across servers, network devices, and cloud resources. In terms of metrics, I can point to uptime percentage, availability of servers and network devices, and faster incident resolution times, as well as a reduction in the number of monitoring-related incidents.

In terms of improvement, I suggest that the pricing could be on the higher side for smaller organizations, advanced customization has a learning curve, and alert tuning may require initial optimization to avoid too many alerts.

Areas for improvement include optimizing alert noise, enhancing dashboard customization, increasing pricing flexibility, and reducing the learning curve for new users.

I have been using LogicMonitor for 24 months.

LogicMonitor is a stable and reliable monitoring platform that supports continuous monitoring of infrastructure, networks, and clouds with strong uptime and consistent performance. Specifically, my team uses LogicMonitor daily to monitor servers, routers, network devices, applications, and cloud resources with minimal operational disruptions.

The customer support is very good.

Previously, we used SolarWinds, and the reason for switching was that we could not access real-time dashboards or monitor servers, routers, switches, and CPU utilization effectively, which is why LogicMonitor has proven to be a much better platform for our needs.

The use of LogicMonitor significantly helps save time and reduce downtime in our organization.

Our pricing and setup costs are organization-specific and based on company deployment across network areas. The pricing model is subscription-based.

Before choosing LogicMonitor, we evaluated SolarWinds.

I advise others looking into LogicMonitor that it is a very good platform.

LogicMonitor is a strong choice for any organization seeking proactive monitoring, centralized observability, and improved operational visibility across the IT environment.

I would rate this review 9 out of 10.

Hybrid Cloud

Other

My main use case for LogicMonitor is monitoring the network devices in the environment.

For example, I monitor switches, UPS, routers, network devices like internet service providers, and all kinds of network devices.

I also segregate sites and devices by adding them into user groups and checking if any specific site went down to monitor it through LogicMonitor. I also check the configuration of the devices and have multiple uses for the platform.

The best features LogicMonitor offers are real-time updates on the devices and their health status, with all information available at one site. I can log in on the device from the tool only.

When I mention real-time updates and being able to log into the device from the tool, it gives a full view of the devices so that I can rectify issues quickly.

LogicMonitor has impacted my organization positively by reducing the troubleshooting time and providing real-time monitoring of device health to keep the devices up and running.

There is a significantly decreased response time. Before using LogicMonitor, it used to take 20 to 30 minutes to rectify an issue, but now it takes around 15 minutes.

I think LogicMonitor can be improved by including AI capabilities and putting suggestions such as if a UPS is down, there might be a power issue, or if only a switch is down, maybe check the cable. The platform could check routing issues and add suggestions on the device itself about what the issue might be to summarize the problem.

Regarding LogicMonitor's AI capabilities, I think its governance and security are in initial phases, so reliability is low.

Regarding the accuracy and reliability of LogicMonitor's AI output, I would rate it at 80 percent.

I have been working with LogicMonitor for two and a half years.

I had a great experience with LogicMonitor, and I found the review questions to be insightful. I give this product a rating of 8.

I primarily use LogicMonitor as a centralized infrastructure monitoring platform, which helps me to identify performance issues, outages, and capacity bottlenecks before they impact the users. It is basically used for monitoring servers, network devices, cloud infrastructure, storage systems, and similar infrastructure components.

LogicMonitor offers standout features such as agent-plus monitoring, easy scalability, multi-vendor support, and cloud monitoring integrations, which are valuable features. LogicMonitor has positively impacted my organization by improving scalability, allowing me to expand monitoring from a small environment to a large, cloud-based infrastructure without any changes in the architecture. It also supports enterprise operations effectively.

Since using LogicMonitor, I have improved infrastructure visibility, which has resulted in faster incident response, reduced downtime, better capacity planning, and a significant reduction in manual monitoring efforts, providing me with substantial benefits.

LogicMonitor has a few areas that need improvement, such as more simplified customization for advanced monitoring, better pricing flexibility for smaller organizations, improved reporting templates, and an easier onboarding process for beginners.

I have been using LogicMonitor for the past four years.

LogicMonitor is reliable and stable.

LogicMonitor is scalable and very good at monitoring and capturing the alert systems, with alerts configured based on threshold anomalies and device groups, making it one of the strongest features.

The support team is good, but the response time is low; they need to focus on improving the response time.

I have not used any other solutions previously. LogicMonitor is the only tool I have used.

The challenges I faced during the deployment of LogicMonitor include fine-tuning alert thresholds, reducing alert noise, and customizing monitoring for some legacy applications.

The challenges I faced in gaining complete visibility across my hybrid infrastructure include fine-tuning alert thresholds, reducing alert noise, learning the platform's advanced configuration options, and customizing monitoring for some legacy applications.

There is a good return on investment, as I have saved a lot of time and can monitor all alerts with fewer employees thanks to LogicMonitor, which has definitely saved money.

The pricing part is taken care of by my accounts team, so I do not have the details.

I did not evaluate any other options.

I have utilized the Dynamic Service Insights feature in LogicMonitor, which has improved root cause analysis by quickly identifying the affected dependency chain, resulting in faster incident response, reduced mean time to resolution, and better visibility for management and operation teams to understand service health, leading to better risk assessment during outages or performance issues.

The faster response time and reduced MTTR have been noticeable, although I do not have the exact numbers.

I have not used LogicMonitor's Edwin AI for diagnosing root causes or orchestrating remediation.

I have not used the autonomous learning feature of Edwin AI.

I would rate LogicMonitor a seven out of ten. My advice for others looking into using LogicMonitor is that they can proceed with this particular tool as it is a good tool for monitoring systems and a stronger option than other monitoring tools available.

Private Cloud

Microsoft Azure

My main use case for LogicMonitor is to have visibility on the servers in our network, various networks, and cloud resources.

I use LogicMonitor to look at various logs, and I have used the logs that I have obtained from LogicMonitor to pinpoint issues and fix them.

The dashboards are really very helpful and they can be customized, which helps us.

I think agentless monitoring and the dashboards are my favorite features. With agentless monitoring, there is no need to install software on every device, and that cuts down time because we have a lot of devices. The dashboards are customizable, so various teams and roles can use those dashboards in a way that suits their needs.

When I see things in real time, I am able to get to them faster. When there is any kind of issue on any of our various servers, because we have many servers in our environment, seeing things in real time is very helpful.

It has had a solid impact and has helped us to resolve issues faster with everything in real time and the alerts. Some noticeable changes could be how our dashboards look and how we are able to see things in real time.

LogicMonitor has a very steep learning curve. The user interface sometimes can feel unintuitive. The mobile app has some limitations.

The only challenges we have are sometimes the setup, which can take some work to avoid too much noise. When we need support, they have been helpful.

I have been using LogicMonitor for three years.

LogicMonitor customer support is good. I advise getting a demo and working with the customer support because I think LogicMonitor works well.

I am not sure what we used before, as it might have been before my time. I do know that we switched because whatever we were using before was not functioning in a positive way.

There was DataDog that we looked at, and I thought LogicMonitor was better.

The pricing was a bit high. The setup was pretty fair.

I have seen a positive return on investment. I cannot give specific metrics, but it has definitely saved time for my team.

I gave LogicMonitor an overall review rating of 8.

On-premises

My main use case for LogicMonitor is to monitor our client environments, which includes servers, websites, and similar resources.

In my daily work, I monitor all kinds of servers and websites through LogicMonitor. It depends on the particular use case or the client requirement, and it involves all kinds of alerts related to the resources that a computer uses: CPU, memory, and networking.

I don't think anything unique exists about my main use case for LogicMonitor; anyone who uses LogicMonitor uses it in the same way, with only the types of alerts configured being different.

LogicMonitor has positively impacted our organization by reducing our volume of incidents that we work on. Proactive monitoring has definitely improved, but false alerts keep on coming.

I don't have any numbers to share, but I can say, with my experience, the incident volume has dropped by about 30%, maybe more.

The best features that LogicMonitor offers include its UI and the report creation feature. I appreciate how it gives you reports in terms of how it has monitored something, such as CPU usage over a week.

I find the UI of LogicMonitor is pretty good compared to other tools I've used, and we do use the reports for internal reviews and root cause analyses. I find it very clean.

LogicMonitor tends to continuously ping the servers and the environment, which can create a lot of false alerts. Another thing is that it is not very good for application monitoring.

LogicMonitor can be improved by reducing the number of false positives it generates and by enhancing the application monitoring part, which does not work well; Dynatrace still dominates the industry for that.

I have been using LogicMonitor throughout my career for three years.

LogicMonitor is stable.

LogicMonitor's scalability is good, and it is scalable.

The customer support for LogicMonitor depends on the plans that you have.

Previously, we used Zenoss, which was irrelevant, and that's why we switched to LogicMonitor.

I don't have any numbers to share, but I can say, with my experience, the incident volume has dropped by about 30%, maybe more.

I do not manage the pricing, setup cost, and licensing for LogicMonitor.

My advice to others looking into using LogicMonitor is that it's a good tool to use, and if you don't have any monitoring for applications, you can definitely go for it. I would rate this review a 7.

Public Cloud

Other