Infrastructure Monitoring and Observability Platform

I am a customer of LogicMonitor and have handled B2B business. My usual use cases for LogicMonitor involve our cloud resources and on-premise resources. I have used LogicMonitor for monitoring devices, servers, and websites. I have around 11 collectors and 1,000 devices onboarded for my client account, Welsh Water. I am from Infosys and used LogicMonitor for Welsh Water, so basically it is B2B.

The impact of LogicMonitor solution on my team's mean time to resolve incidents involves automated ticket polling. When we set a limit, it automatically closes the ticket if it is resolved. This saves a lot of time and I don't need to go through piles of unwanted errors. Automated error recovery is something I really appreciate.

Another thing is the scheduling of reports, which saves most of my time and energy. The error handling mechanism comes with a scope, and we have RBAC enabled. Those who know can approach it and nobody else is going to see what is happening in the other team. It helps the team directly resolve errors. Half of the errors which are invalid go away, and half of the errors which just need to be acknowledged can be scheduled as a report and solved by each individual team. This reduces time and energy significantly.

The feature and capability of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

The Partner Academy supported by LogicMonitor is a feature I could highlight and really liked. Learning about the tool is possible through this platform. I can see an instructor teaching me the implementation of LogicMonitor. We don't have many other resources to study about the tool, and we have very limited resources available. The partner portal is one such feature I appreciated.

The latest version has features that satisfy me greatly. I am impressed with the look of the new version, the design, and the dashboard options. It has more tabs but is very easy to navigate with everything on one page. The UI and UX design made as a new feature in LogicMonitor is something I appreciate. I usually use one feature where I can see the resources in a hive structure. All the resources can be seen in a hive manner, with everything color-coded basically in three colors for error, warning, and good status. If anything is coded in red, I can go to that and easily see it. I have seen this feature on the resources page or maybe in the dashboard page where every service and website is shown. My usual health checkup is much easier with this feature.

The collector was really good and I had a good experience with it, especially on load balancing. There exists automatic load balancing which I really appreciated.

LogicMonitor's 24/7 monitoring is a feature I really appreciate. It saves me from the night shifts and I don't need to worry about it. It handles both business time and off-business time without my consent in an automated manner.

LogicMonitor can be improved when we go to the settings page. In the earlier version, it was pretty simple where I had to navigate individually to the individual settings. In the new version, the navigation is easier but the buttons are very close to each other. Sometimes when I'm clicking on something else, I'm clicking on the next button. I need some good alignment to happen on the settings page.

I have been using LogicMonitor for about five years.

I evaluate how stable and reliable LogicMonitor is, and I don't find it unreliable because even the chat is happening very confidentially. I don't think it is unreliable from my end. I have never felt any power issues or power backup issues from LogicMonitor. Whatever I have made for my collector as a backup always stayed in place.

One day I made a mistake by shutting down all the servers at once and I haven't touched anything with it. I went to see the mistake after some 12 hours. When I clicked it on and gave access again, making everything active, every alert was there. Whatever happened within that 12 hours was recorded there. Even if it was not kept in active mode, it somehow gave me all the data. That is the stand-alone stability of LogicMonitor.

I can rate the stability of LogicMonitor from one to ten as eight because it is not classified properly. Though we have the common three classifiers of warning, error, and critical, I expect some classification if it happens for piles of emails or piles of errors. However, I can give it an eight.

I evaluate how scalable LogicMonitor is and I can give it a nine because of its very good UI, except for the spacing in the buttons. It is very navigable and we can navigate to anything very easily and quickly. I can give it a nine. When I am about to learn something, the interface presents it in a way that is easy to understand. When I look at the resource page, I can learn all the cloud resources we are having and the number of devices we are having very quickly. In order to understand the architecture, it is very easy for me. When it comes to adaptability, I can give it a nine as well.

The features and capabilities of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

My communication and interaction with technical support shows they won't make anything out of the league. They maintain their confidentiality between us and the client very well. They also have a corporate approach and what we have discussed will be released via email, which is very perfect. We have quick assistance where they go into the server, look for the issue, and if they find anything, they report to us immediately and within 10 to 15 minutes it is resolved. Rapid problem solving is what I would say in one word. It is very fast.

I can rate technical support from one to ten as nine, definitely nine.

Before LogicMonitor, I used a different solution for the same use cases, and it was SolarWinds. The reason I decided to stop using SolarWinds is that SolarWinds requires agents, as basically all other monitoring and observability tools have this agent to be used, and there is no built-in API with that. LogicMonitor is having REST API and is also agentless, which makes it more advanced.

The challenges I faced in gaining complete visibility across my infrastructure involve especially working with the syslog and the tags. There are many tags for a particular server which I am not confident about which ones we are using and for which purposes we are using them. That is something I really stuck on, but as we don't use them much, I am comfortable with the current setup. I would rate this review an overall eight out of ten.

My main use case for LogicMonitor is infrastructure and cloud monitoring.

A specific example of how I use LogicMonitor for infrastructure and cloud monitoring includes servers with multiple operating systems, whether Linux or Windows, and in the cloud, the three main providers: GCP, AWS, and Azure.

The best features LogicMonitor offers are agentless monitoring and a SaaS platform.

The agentless monitoring feature benefits my team by reducing overhead from an administration perspective.

LogicMonitor has positively impacted my organization by enabling us to detect issues quicker and respond to failures quicker. We are now aware of issues significantly faster than previously, and my team can detect and respond to issues at a much faster rate.

LogicMonitor can be improved by having better dashboards and better reporting.

I have been using LogicMonitor for more than five years.

LogicMonitor is stable.

The scalability of LogicMonitor is good, but it is challenging to have to spin up additional collectors all the time.

Customer support is good if I get hold of a premier support agent first.

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

My experience with pricing, setup cost, and licensing is that the licensing model has changed and is very confusing as it currently stands and overly complicated.

My advice to others looking into using LogicMonitor is to assess that it meets your current needs and not be overwhelmed by the features or future needs. Also, look very closely at scalability, how your business plans to scale, and what you actually want to achieve from the monitoring.

LogicMonitor is deployed in my organization through both public and on-premises infrastructure.

I have not utilized the Dynamic Service Insights feature for real-time visibility.

We have both on-premises and cloud resources as well as network resources. Everything monitored for my client, which I cannot disclose, is done by LogicMonitor itself. The endpoint website monitoring is also done via LogicMonitor.

What I appreciate about LogicMonitor is that it has a number of data sources and data points, which they call LogicModules. One thing that is not available in many other monitoring tools is the level of customization I can do with it. Even at the ground level, I can go into a very particular data point for a single instance and change the metrics for monitoring. The granularity is something that is not provided by many great products, but this one offers it.

The insights from LogicMonitor affect my understanding and management of digital services in my organization as we heavily rely on the insights from LogicMonitor. It cannot go without human verification, obviously, but the insights it gives and the alert notifications which top talkers have generated are easy to portray to clients, to the C-suite, and to executives to make them understand where the bottleneck is and where I am utilizing more resources or where resources are not needed. This helps in cost-cutting as well.

The main area for improvement is that if LogicMonitor's UI were a bit more user-friendly, that would be more useful. Not many people can easily understand the data sources and data points. New joiners on my team cannot get away with it very easily without proper training. LogicMonitor is not as intuitive as Blue Coat or SolarWinds in this regard. You will have to go through the LMCP or you have to pursue complete training, after which you will be able to understand and use it.

I have been using LogicMonitor for the last 2.5 years.

Regarding stability, I have experienced downtimes when LogicMonitor upgrades the portal completely, but it is well-informed in advance and there are collector updates that occur during that time. For half an hour, we will not see any insights or miss any alerts and insights, but they inform us well in advance and they do not do it during business hours. I have not seen any downtime that extends more than what they have decided.

I do not find any scalability issues with LogicMonitor so far.

I personally used LogicMonitor technical support directly, and there were no third parties involved such as partners or consultants. LogicMonitor provided a dedicated team to support us. They have a 24/7 team who were always available during setup, and we had numerous meetings and calls to help us understand the setup and how the tool works. On a scale of 1 to 10, where 10 is the best, I would rate the tech support and customer service team as a nine. They are always responsive apart from weekends or public holidays when they take a bit more time, but otherwise, they are quick.

Apart from LogicMonitor, I work with other monitoring solutions and previously used different solutions for monitoring. I have used SCOM and SolarWinds majorly, and a number of others in my previous organizations. However, primarily here with my client, it is LogicMonitor itself.

When reflecting on the initial setup of LogicMonitor, I found that whenever we onboarded, we had a support person and a complete team assisting us for the first initial few days. This was necessary. Anyone without any prior knowledge of LogicMonitor would not be able to figure it out as it is quite different from other monitoring tools, particularly regarding the granularity I mentioned. LogicMonitor provides complete support for migration, setup, and initiation, which is helpful. However, any company wanting to onboard with LogicMonitor alone will find it difficult if they attempt to do so without support.

I personally used LogicMonitor technical support directly, and there were no third parties involved such as partners or consultants. LogicMonitor provided a dedicated team to support us. They have a 24/7 team who were always available during setup, and we had numerous meetings and calls to help us understand the setup and how the tool works.

I have seen return on investment and measurable benefits with LogicMonitor by creating a report on how many resources we are actually using and what the billing should be. I ensure that no unnecessary resources are being monitored just to create unnecessary billings.

We have been utilizing the Dynamic Service Insights feature for real-time visibility for reporting purposes, and we are still to onboard and still to use the diagnostic features which LogicMonitor provides. We are still using the traditional way to diagnose with our teams rather than having LogicMonitor handle the diagnostics.

LogicMonitor's AIOps for diagnosing root cause analysis and orchestrating remediation is quite new for us. The LogicMonitor Plus subscription has now given us Edwin AI, and we are still struggling to get this completely legalized for work. Not all AI features are being used yet. When we gain more knowledge about it, probably in a year from now, we will start using Edwin AI.

The impact of LogicMonitor on my team's mean time to resolve incidents has been great. We find a number of points which create lots of top talkers, perhaps something which creates unnecessary noise with alerting. LogicMonitor flags that on its own, which is quite helpful on a monthly or weekly basis. We focus on lowering MTTR from a monthly basis for each team that works on LogicMonitor.

Regarding missing features, the diagnostic features for Edwin AI are something I am really looking forward to. I am handling LogicMonitor for my client solely right now, with a few other peers. Edwin AI would help resolve lots of server issues and diagnose them to minimize MTTR.

The challenges I have faced in gaining complete visibility across my hybrid infrastructure with the Envision platform are that LogicMonitor started about 2.5 years ago and I struggled a lot to get the teams onboarded on it. Nobody would let go of traditional ways such as AWS monitoring to get onboarded with LogicMonitor, as there is a cost per resource added. The reports it fetches, the insights it gives, and the future forecasting have always been very helpful. We have around 10,000 plus devices from a server point of view, and it is ever increasing. Still, we have many on-premises devices from third parties which are still not on LogicMonitor. We can only hope that those teams agree to onboard as well.

If organizations would like to monitor on-premises and cloud infrastructure, many have different tools for cloud and on-premises devices and differently for network devices as well. That can be cumbersome as the data points and ratios are different. If they would like everything in one place, they should go with LogicMonitor. It handles it pretty well. If they need any deep dive for NOC operations and network devices, they can incorporate another app above it, but for everything all in one place, LogicMonitor is good with it. I would rate LogicMonitor as a product and solution eight out of ten.

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.