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

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

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

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

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

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

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

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

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

Think thoroughly about the structure you want to have in place. Don't just start implementing. Think thoroughly about how you want to be set up, how you want to manage the devices, how you want to manage the people, and how you want to manage the alerting. Plan, scale it out, and implement it properly so you don't have to go back in and do some cleanup work on the backend after the fact.

I would rate LogicMonitor a high nine out of 10.

I rate LogicMonitor eight out of 10. It's easy to add new features to LogicMonitor. They have an active community of users who are willing to share their experiences and how they have extended the solution to do unusual things.

I can't remember the version of LogicMonitor I'm currently using, but I know that my company continuously upgrades the solution as new releases come out, so it would be the most updated version.

In terms of deployment, it's on-premises, specifically for the collectors that do the polling, but those collectors in turn talk to the HTTPS-protected public environment, though my company just needs the address.

Two people from the headquarters and one to two people at each of the facilities in charge of monitoring devices use LogicMonitor. One network engineer takes care of the deployment and maintenance of the product.

More than four thousand elements are being monitored now, and my company is continually looking to expand that.

My advice to others looking into implementing LogicMonitor is that it has exceeded requirements and has continued to do so.

My rating for LogicMonitor is eight out of ten, just because the team has been very responsive to suggestions that my company made to improve the product, especially in terms of usability. Because there's always room for improvement, I'm scoring the product an eight.

My company is an end-user of LogicMonitor, specifically a very active end-user.

The thing is that some features are there, but we have, like, incompetency to add up that feature. So, the product is feature-packed. But some of the features we have to explore still.

Overall, I would rate LogicMonitor an eight out of ten.

So far, the introduction of cloud monitoring with LogicMonitor is testament to their ability to stay up-to-date with different sorts of monitoring and future IT requirements. I have seen progress on this front from LogicMonitor. Ever since we started using the LogicMonitor platform, there have been many updates that have introduced new functionality that seemed to be catered for the future of IT.

There are still some features that we haven't fully integrated that we would like to do. At the moment, we are currently reviewing what the value of these tools will bring to our customers.

We don't use Dynamic Thresholds at this stage. Dynamic Thresholds are something that we would like to review as we proceed with the product. It comes down to use cases. Depending on what you are monitoring, it may make sense. However, in some cases, it doesn't make sense, which is a factor to consider.

In terms of visibility, LogicMonitor provides a wide variety of information. The more devices that you are monitoring, the more information that you can cross correlate. Especially using other features, LM Logs is definitely something I can see value in. From a support perspective, it decreases the amount of time it takes to identify or resolve a problem. So, you receive an alarm, then when the resource looks into the alarm, the LM Logs capability actually allows you to see the log messages at the time of the alarm. Instead of the resource having to manually connect to the device and check the log file, this information is correlated for you within the platform. So, this is not a feature that we use today. I have seen a demo and can definitely say that there is a lot of value from this particular feature. I believe that a lot of providers would see the value in it.

At this stage, we are quite happy with the level of functionality that we have with this tool.

I would definitely recommend trying LogicMonitor for yourself. I believe you will quickly see the value in the different feature sets that are provided and its simplicity, in terms of the user interface. If you have used another platform for IT monitoring before, this is very good in terms of the user interface. It definitely has a great user experience when you are using the platform. It is very customizable in terms of the color schemes that you can use. Definitely give it a go and you will see the value, just as I have.

If you feel like you can't find the tool that meets your requirements, it is definitely out there. Personally, we were looking for a new tool for quite a significant amount of time. We looked at many tools. Coincidentally, towards the end of that sort of campaign of trying to find a new solution, I actually received a call from a LogicMonitor resource. It was quite coincidental. It's actually funny how it happened. So, one of the lessons I learned is there are many platforms out there and you just have to keep looking. Eventually, you will come across something like we did, like LogicMonitor, that will meet your requirements. 

We have had a fantastic experience so far. It is a fantastic product. It is definitely worth looking at. It has definitely delivered on our requirements. I will rate it as a solid nine out of 10.

LogicMonitor offers integrations with various tools, such as data analytics platforms. While some integrations may require additional investment, they provide an open API, allowing custom integrations to be developed. While not all integrations are included for free, many of the leading market tools are supported.  

I work with clients of varying sizes, including enterprises and smaller businesses. Previously, I mainly worked with enterprise clients, but recently, I've configured the system for smaller businesses.

I rate the overall solution a ten out of ten. Before you buy LogicMonitor, figure out how big your setup is and how many collectors you'll need. Understand your needs and environment well to avoid any complications later on.

They have to first evaluate their options, consider their business requirements, use cases, and fix the purpose. If it is to process, LogicMonitor is definitely a tool to go for.

I rate it ten out of ten.

We're fairly self-sufficient. We already use Puppet for automation, and we're starting to move some workloads to Ansible. However, we wouldn't ask LogicMonitor to help us with automation.

Biggest lesson learnt: Know what you want to monitor and what threshold you want to alert from. E.g., if you don't do anything and just start monitoring out-of-the-box, it works. However, if you don't set thresholds, it's not telling you when to take action. So, if you just add things to LM and start monitoring them, you're not done. Until you've set a threshold for where something is actionable, you haven't really finished the job. That's my experience with NWEA. You can click on anything that we've been monitoring, and if you don't have any thresholds set, then you're just making pretty graphs.

I would rate the solution as a 10 (out of 10). I am a fan of the product. It's great.

We use Datadog for cloud monitoring. I rate the overall product an eight out of ten. 

Like any good project, spend plenty of time upfront working out precisely what you want out of LogicMonitor, before you race off and start deploying it. Otherwise, you'll end up doing a lot of reworking. Take advantage of the onboarding resources, and even pay a little bit of money, if needed, to give you that leg up and the headstart in understanding how the platform works. If you know what your customers want to get out of it, and what you want to get out of it as a business, the platform will most likely be able to give you what you want. From there, you'll end up in a comfortable operational place where you can look at taking the next step into process automation with all the API functionality to improve business efficiency.

The strength of LogicMonitor is in the dashboards and the information that's available. Every customer likes a dashboard, so if we can give them dashboards that provide meaningful, real-time information about what's happening in their network and across their business, they see significant value in that. Most solutions don't have that today.

This is a SaaS-based solution. We have URL access to it. 

I'd rate the solution eight out of ten overall. I'm happy with its capabilities. 

I would recommend it to others as it is a very good tool.

Take your time with it. A lot of the delays that we had were around customers not giving us access to their networks to get the collectors installed. We had a very strict timeline that we had to follow when we were doing the migration because our contract was ending with our previous vendor. We had to get everything all up based on a particular date, and it was down to the wire. We were very close to actually not monitoring a couple of customers because they just weren't giving us the access we needed. So, my advice is if you're onboarding the product and you are dealing with many customers, then just make sure you give yourself enough time.

The reporting capabilities are within average. They are good for certain point-in-time reports that you might need. However, most reporting that we do is service reports that we provide our customers at the start or end of the month. Because we try and look at various data from multiple systems in one report, we use an external product to get the data from the LogicMonitor API that we want to put into one report. With the reporting in LogicMonitor, you would have to run many reports to try and get all of those pieces of data. Therefore, we use a third-party product so we can just run one report, have it all automated, and take away the administrative headache. There is nothing wrong with the reporting. It's just for our requirements: We need the data to come from LogicMonitor and other platforms as well.

For the initial phase, rather than having only one or two functional guys participating, it's always good to have one or two technical folks in the discussions. That helps a lot. You don't want surprises if an organization decides to go live with this tool, and then realizes that technical things are not on board with the ideas of the functional team. That's something I can say based on my journey and experience.

Another thing that is important is to keep on having internal conversations; that you value and give importance to everybody. It's good to educate them. Use the help of the LogicMonitor support team for internal question/answer sessions and do anything that will help them feel more comfortable. It's not about two or three members being really happy with this. LogicMonitor is something which can only be successful in automation if all the key teams and team players are on the same page.

The biggest lesson has been how we could make everybody be part of the mission. Previously, monitoring used to be in the hands of one or two, and each of them had a lot of overhead to deal with. But by doing this, we have reduced the complaints from individuals and each stakeholder. They know how they're configured. They know what the escalation chain is, so they're confident. If there is something not working, it's because of the way they have it configured.

By doing this we have minimized the internal noise. We have given everyone the opportunity to know the pain involved in monitoring and what it takes to have a better monitoring system in place, and how each person can contribute and think outside the box. They know how to put into place the right parameters and the right numbers. Previously, 70 or 80 percent of things were escalated internally. There was no involvement of the particular customer. If there was a problem for a team, it was somebody's problem, not their problem. Now, it has all become their problem. This is a very high-level benefit of using tools like LogicMonitor, which involves everybody more.

I would give LogicMonitor an eight out of 10. There are a few things that LogicMonitor is also learning from their experience with the customer. Most of the customers are giving feedback to LogicMonitor for improvements and to make changes. I'm sure that very soon it will be a 10, but at this point in time, from my experience and journey, it's an eight.

They are adding features faster than we can implement them. They have a very good development team. They have also made some acquisitions. They acquired Unomaly that did log analysis. It was from a Swedish company. That product is now completely integrated with LogicMonitor, and we bought that extra piece of software because one package doesn't fit all. It is a package that we are using to enhance our product catalog for logs, and it is a very useful one.

I would advise making a good project plan for migrating. That's the most important thing to do. Make a good choice while buying, and take your time. Don't rush into anything. When you're looking for monitoring software, you need to know what you need and what is nice to have. There are always things that you want to have, but they are not really necessary. You should choose products that can fit them all. As a system engineer, I want to have one pane of glass to look at everything. I don't want to switch screens to look at another log file or another system. I want to have it all visible in one system. That's the most important choice you can make as an engineer.

I would rate it a nine out of 10. Its price makes it a nine for me because it is pretty expensive. Otherwise, I would choose it over everything else. I will look at another product, but I'm sure I will come back to LogicMonitor.

We have used dynamics thresholds in only a couple of cases. We didn't necessarily see the application of dynamics thresholds in looking at critical alerts. So, we haven't used that a whole lot. Also, we haven't really leveraged the AI pieces of LogicMonitor. We are at a point with our tuning that we haven't needed to do so. If teams started complaining about specific alerts, like specific servers showing trends, increasing or decreasing, then we would probably do it, but we have been able to handle those concerns with static thresholds at this point.

I would rate the solution a nine out of 10.

If you are looking to implement LogicMonitor for the first time, work through their available documentation. There are a couple of certifications that they offer which are very good and give you a good foothold into the process. Then, talk with people who are currently using LogicMonitor. There is a great support community out there with people who are more than willing to help.

AIOps does provide a very useful data set. They have been continually improving it. AIOps is one of those things, which is there and we use it a bit. While the dynamic thresholding is interesting, the anomaly detection is probably more a nice to have, and not more of the primary features that we use.

We have not utilized the automated discovery and deployment. With managed services, we have to keep track of how we charge customers. Generally, we have a specific list of devices that we're going to monitor, so we don't use the discovery features on LogicMonitor.

As far as monitoring platforms go, I have worked with a wide variety. I would give LogicMonitor a 10 out of 10.

I would definitely recommend LogicMonitor. It's something to look at either when signing up for a trial or for a use case process . It's been a great product. It has customizations when you want them, and out of the box solutions if you don't want them. It works and is reliable. Compared to other monitoring platforms I've used in the past, it seems to be the most powerful and robust that I've dealt with.

The solution monitors most devices out-of-the-box, such as, Windows, Windows Server, Linux, F5 load balancers, Cisco firewalls, and Cisco switches. Those have been pretty easy to monitor. Our issues have been with one-off or nonstandard platforms that we've implemented. Otherwise, everything has been pretty easy to implement.

I would rate it as a solid nine (out of 10).

Do it. Your customers are going to like it, once you show them the dashboards, the pretty colors, and the ability to easily interact with it. That's going to win over your customers. I guarantee it. I've seen it happen. You can say, "I've got this tool that does everything," but if the customer can't tangibly see what the tool is doing, they'll say, "Well, what am I paying you for?" And they don't want to see generic spreadsheets. They want something that's easy to use and interact with.

I like how they've been improving on it over the years. It seems like they're going in the right direction. LogicMonitor fits what our company needs, and we plan to keep on using it for at least five more years, until something else gets better or they're out of business.

We don't use its AIOps capabilities for things like anomaly detection or root cause analysis yet, but that is something we are looking into. I know they're releasing those features in phases. They've got the first phase of AIOps and then they're pushing the next one with the dynamic thresholds, and that is definitely something we're going to be using, especially when you're looking at Cisco Voice systems and how they perform throughout the day. Dynamic thresholds are going to be huge for us, so that's going to be exciting.

We have about 100 people who work directly with LogicMonitor in our company. They're all the way from managers down to the low-level NOC people who are answering the telephone, to the Tier-3 engineers, and even the sales and marketing people. Everyone interacts with LogicMonitor in some way, either supporting a customer, running reports, or looking at the capabilities and what we are monitoring.

Overall, I've been very happy with the solution so far.

LogicMonitor has evolved drastically in the last couple of years. They have made a lot of changes and are moving very fast. They are getting accustomed to machine learning, AI, DevOps, etc.

Don't reinvent the wheel. Just concentrate on your business and put your monitoring on LogicMonitor.

The solution has helped consolidate the monitoring tools that we need to an extent. For example, if our customer is running an HPE machine and doesn't have a license for HPE monitoring, they can at least see the basic hygiene level of hardware through LogicMonitor.

In the last month, we deployed the agentless collectors. We are still in the phase of commissioning those devices, so I don't personally have any experience on this.

I would rate this solution as an eight (out of 10). 

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

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

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

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

It really just comes down to making sure that we're getting alerts on something that actually does need attention.

We're starting to look into the solution’s Artificial Intelligence for IT Operations (AIOps) capabilities for things like anomaly detection, root cause analysis, or dynamic thresholds to see if it might be useful for some of our services.

Take a look at your environment and at what level of detail you will need for monitoring. One of the advantages to LogicMonitor is just monitoring your vSphere environment without monitoring the individual VMs within it. You still get a lot of detail about those VMs as instances. To put a VM in as a resource, instead of an instance, you get a lot more granularity on the operating system side for what you can look at. However, just monitoring your vSphere environment alone gives you a surprising amount of detail.

The biggest lesson I've learned is you need to understand what role your different devices play in your infrastructure in order to successfully monitor them. Get a detailed list of the devices that you do have in your environment that you want monitored and why you want them monitored. The why you want them monitored will tell you what different things you might want to be alerted on because LogicMonitor will collect a lot of information about your devices. Narrowing down what you actually want to be alerted on is the important part.

I would rate the solution as a nine out of 10.

If you only want to use LogicMonitor in the cloud, there's a better tool available. But if it's for traditional infrastructure monitoring, it makes sense; it's a useful tool. 

However, if you are a cloud-native organization and want LogicMonitor, I believe it will be a costly investment because there are many better cloud monitoring solutions available.

There are numerous options, including CloudWatch itself, or Grafana with a connection to a CloudWatch data source. You can use Grafana to monitor as well as others, there are numerous tools available.

They are good, I would rate LogicMonitor a nine out of ten.

The big lesson I have learned from using LogicMonitor is to pay attention to the alerts we receive. Things get escalated to me whenever guys from the other teams do not acknowledge their alerts. I need to pay attention to those because they will tell us whenever a computer or server is being rebooted or if the drives are getting full.

There are six of us in my company on the services and support side. My manager is the person who actually configures it. In addition to me, there is the principal IT consultant for services and support. I do mostly storage and power infrastructure, in terms of servers. We have two more guys who work with Citrix. And there is another guy who does mostly networking. He works mostly with NetScaler ADC.

I give LogicMonitor 10 out of 10. From the time that I started using it, I haven't had any issues with the software at all. I get notified whenever they're doing upgrades and, whenever I need to do an upgrade to my collectors, I get the information with plenty of time to make arrangements if there is something else that needs to be done. I don't believe there have been any upgrade procedures have been done on the platform that have impacted us in any way. It's been a really stable and trustworthy platform.