One of the things that I did when I came into the company was to put this solution in place because they didn't have something.

It is one of those tools where you start using it and see how nice the graphs are. I have used other monitoring tools in the past, and their graphing has just been awful. Once you see LogicMonitor and start using it, you realize how easy and nice the application is to use.

We switched from our previous solution because deployment time was entirely too long and it was too complicated.

I was a big user of SolarWinds before. It was easy to pull data out of SolarWinds and then put it into other tools for big-picture analysis across the entire enterprise as opposed to an individual device.

We were using SolarWinds for the last eight years, but when they had the data breach, we said we were not going to continue using it, and we had to find something else to use instead, so we did our evals and we decided on LogicMonitor as being one that we didn't have to support ourselves. We could count on their software as a service process and their support staff has always been very helpful with us in terms of looking at devices that are not in the standard stream such as Silver Peak. We've been able to ask for their help to better understand what we could see from the solution, including how we can monitor and keep it current.

I have been working with SolarWinds for more than four years. So, I can talk about SolarWinds. SolarWinds is good for network monitoring. It has reporting of topology diagrams and all this stuff that we can get over there. Also, a bandwidth analyzer is available, which is a very handy tool. There is also configuration management, which is like an add-on basis. So that is good. But with the recent incident with SolarWinds, it is no more secure. If you wanted an on-premises solution, then probably go with ManageEngine or SolarWinds. But when looking for cloud-based, we thought LogicMonitor will be good for us. We only have to check and gain some knowledge on whatever they provide, the knowledge portal or training. So, that is part training for us.

In the past, we needed to spend a lot of time and effort tweaking and adjusting metrics per customer, though not with LogicMonitor, which is not efficient. With LogicMonitor, we found that the overall time to onboard a customer into monitoring, providing useful and valuable input to the customer based on their environment, is quite quick. So, the time to onboard and provide insight is quite quick. This is a good example of a way that we found the solution to be quite efficient.

We did previously use another solution. The reason why we switched is LogicMonitor has more advanced extensibility in terms of custom configuration. That was one of the drivers. Another driver why we switched was our user experience with the account teams. We found that with LogicMonitor, from the moment that we sort of met over the phone or virtually, we always had a good experience and felt that we were being looked after. That definitely increased our drive to sort of move away from our previous solution. Additionally, there were integrated functionalities, like LM Config, that take configuration backups from network devices and systems. LM Config was a feature that we wanted to consolidate into one platform.

I worked with NETGEAR and other internal tools, but nothing was as elaborate, extensive, graphically oriented, and well-informed as LogicMonitor. It is one of the best product analysts.

I think my team was using Nagios before. That's just a burning trash heap of an old application.

In my organization, as a whole, we have many chefs in the kitchen. We, the infrastructure team, picked LogicMonitor, then we moved all our stuff to it. However, the database team still relies on Nagios because they're like dinosaurs. DevOps uses Sensu Prometheus, collectd, SIEM, and a laundry list of others. The only reason why LogicMonitor hasn't consolidated is because our teams have the freedom to choose their own tools, and we do. Unfortunately, we tend to overspend on duplicate functionality. I don't think it's because LogicMonitor can't do it, but because the infrastructure team picked it, the Dev Ops team was like, "Well, that's your guys' tool. You guys use it. We're going to go pick our own thing." We were like, "Okay, go ahead.

We did not previously have a different solution in place. 

LogicMonitor replaced our other monitoring solution, ScienceLogic, which was very similar to this platform in terms of multitenancy and customisation. The previous platform charged a premium cost for the additional features that come with LogicMonitor. To have the additional pieces native in this product is a huge advantage.

We evaluated about 6 products before moving to LogicMonitor.  The decision to move was based on features, ease of use and commercial elements.

The main reason for migrating to LogicMonitor from Nagios was to eliminate the noise of alerts. It may have been because alerts were not properly tuned, but the visibility with Nagios was not complete. It became a bottleneck. 

Only one or two people had active access to tune things. If anything had to be done, there was just one guy who had to do it. We wanted to move towards a self-managed model. LogicMonitor is a solution which can be in that category, once it's deployed and there is a transfer of knowledge to each school.

We want each department to self-manage: manage their own dashboards and create their own reports based on their requirements. If they have a new device coming up, they can spin up a new AWS instance and onboard that, etc. It's the initial phase which is going to be challenging. But once we have the handover call with the individual customer, it's going to be easy, and that was not possible in Nagios.

We also wanted to have a proper escalation chain, which was not present in Nagios. That's something we have made use of in LogicMonitor.

Finally, we switched to use fewer resources and to speed up turnaround.

We previously used Zenoss, which is an open-source monitoring software, but there is no intelligence behind it to give you the answers about the things that you get on your dashboard. It is a different product. They have a free version, and they have a paid version. The paid version that they do has good support, but the intelligence behind LogicMonitor is what I like the most about it.

LogicMonitor has become our standard for all the products. Each product is basically an acquisition, e.g., we got rid of Datadog recently and phased out Splunk. The other solutions all came with their own tools, and we have gotten rid of all those other tools. A lot of that happened before I joined.

LogicMonitor was a great move for us in terms of consolidating our monitoring tools. We previously used a combination of paid and open source tools to monitor our customer environments. Being able to consolidate to LogicMonitor has allowed us to save significant time in server management when managing the tool. We have also seen a lot better onboarding times for our employees coming to the environment. It has been a great gain all-around.

The customer onboarding time was cut down by a half to maybe three-quarters. As far as the employee onboarding time, they only have to learn one tool instead of having to learn multiple tools. We have consolidated our collector or data source development from probably three languages down to just PowerShell. That has been a huge gain. It's much easier to find resources that can learn or know PowerShell, so that's been fantastic.

LogicMonitor replaced Observium, Zabbix, Nagios, and SolarWinds.

We've eliminated three different monitoring tools by leveraging LogicMonitor. We had two different in-house, custom built tools that were used for a long time that we were able to roll off, and we also used Nagios. I have also used Zabbix and Orion.

LogicMonitor has reduced our number of false positives compared to how many we were getting with other monitoring platforms. We leveraged the solution to focus it down and only look at the specific things that need monitoring, e.g., rather than every time a service is down we get notified, instead if it's not a critical service, then we can just get a flag, go back, and check it. This is rather than getting spammed with hundreds of emails about specific things being down. Thus, we can customize it for what we actually want to know and need for non-issues.

In 2016, we started off our organization. The same thing happened with LogicMonitor. The timing was that we were both startups at the same point in time, so we grew at the same pace. We never checked another competitor of LogicMonitor, and LogicMonitor was our first buy of its kind. We have been with LogicMonitor since day one.

LogicMonitor was able to replace at least two different solutions that we had in the past for monitoring. One of them being Logicworks. LogicMonitor was able to monitor a wide variety of websites, devices, and virtual machines. We were able to consolidate some of our monitoring so we are one single source now instead of multiple.

I don't believe the company had a previous solution.