What is our primary use case?
We're using LogicMonitor as a software as a service subscription to help us manage and monitor all of our network devices, as well as a lot of our Windows environments.
LifePoint has around eighty different hospitals that we manage, and they all have network devices and connectivity to our corporate data centers where the applications are hosted. We're constantly monitoring the state and health of their network and just making sure that if a fiber seeking backhoe cuts a fiber, that we can know about it and get the respective vendors involved as quickly as possible.
What is most valuable?
LogicMonitor added AI technology to help understand what's normal and that has helped quite a bit, so that's the feature I found most valuable in the product.
The product is also doing quite well with identifying devices and customizing a particular Cisco version or model number. LogicMonitor continues to be active in updating what is available to be monitored, and it's been very good with keeping those things current, so that's another valuable feature of the product.
What needs improvement?
LogicMonitor should always improve AI because we are always striving for real intelligence.
An additional feature we'd like to see in the next release of LogicMonitor is more in the area of identification of when the dominant workload is working. There are certain devices and applications that have cycles of their own. Some are used primarily during prime time, and some are used during the overnight timeframe, and better identification and classification of those workloads would be helpful. For example, we could then do some more planning about, for this particular set of devices, as it has a prime time environment, and we don't want to see a 24-hour average, as we want to see what is the 75th or 90th percentile utilization during the prime time when it is being used, whenever that prime time is.
For how long have I used the solution?
We've been using LogicMonitor for about a year and a half.
What do I think about the stability of the solution?
LogicMonitor is a very stable product. We've not had outages on their part of the environment, though we've had some outages from some of the collectors because they're running a scripting process, and like any other monitoring tool, we need to be careful that we're not overloading those devices gathering the data.
What do I think about the scalability of the solution?
LogicMonitor is a scalable product. My company has been able to deploy more devices on the collectors versus the old SolarWinds environment. LogicMonitor does a much better job for the collector environment than SolarWinds.
How are customer service and support?
Technical support for LogicMonitor was very helpful. On a scale of one to five, with one being the worst and five being the best, I would rate the support team a five.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
The initial setup for LogicMonitor was somewhat complicated for us because our network management was done by a third party. They had to add some ACL rules in the configuration of the network devices to give us access because they had it fairly locked down.
What about the implementation team?
We implemented LogicMonitor via a third party. We had eighty different hospitals and each one of those required time because the network management company we worked with did not always have everything well-documented, and that required a bit of working with them to get things identified. It wasn't a shortcoming on LogicMonitor, but more of a shortcoming of the network management company not having good documentation.
What was our ROI?
LogicMonitor helped reduce the length of an outage of a facility because of the identification of a fiber cut, so my company was able to be on top of that faster, so in that respect, the product gave us less than one year's worth of ROI.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, I would rate LogicMonitor four out of five.
Which other solutions did I evaluate?
We did look at different options before choosing LogicMonitor, but I'd rather not say which ones.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises