We just raised a $30M Series A: Read our story

SolarWinds NPM Competitors and Alternatives

Get our free report covering Zabbix, ManageEngine, LogicMonitor, and other competitors of SolarWinds NPM. Updated: November 2021.
552,695 professionals have used our research since 2012.

Read reviews of SolarWinds NPM competitors and alternatives

CB
Senior Operations Engineer at a tech services company with 11-50 employees
Reseller
Top 20
Enables us to get up and running much faster, while still maintaining a customized look and feel for our clients

Pros and Cons

  • "We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status."
  • "The only functional area I can think of that has room for improvement would be the dashboards. They could use a refresh. It would be nice if there were more widgets and more types of widgets."

What is our primary use case?

We use it for monitoring our customer networks, for monitoring network devices, and we also use it for monitoring our hosted environment.

We're a managed service provider. We have LogicMonitor deployed so that we not only have our devices input into the system, but we also manage a lot of resources for our clients in it. We have it set up so that they can only see their items in there, through a lot of access control. We have a local presence with the collectors, the polling stations, while the data resides in the cloud. Once we pull the data, it then shifts all the data up to the cloud for long-term storage. LogicMonitor is all SaaS-based, other than the local collectors.

How has it helped my organization?

Before LogicMonitor, we were using another tool, and deployment of that tool took a lot of time, effort, and energy from our team, and it was very customized. While the end-product could have been great, because everything is so customizable, the problem was that we couldn't get up and running very quickly. With LogicMonitor, we didn't lose any of that customized look and feel, but we were able to get up and running so much faster. We went from onboarding even simple networks over the course of weeks to down to about a week.

We're able to monitor most of the things that our customers worry or care about. That's mostly because of the flexibility of LogicMonitor. The beautiful part about this is that if something is not currently in the system at the moment, the support from LogicMonitor has meant that it gets ramped up pretty quickly.

For customers who have multiple monitoring platforms, it's definitely very easy to simplify and get to a situation where there is one place for monitoring everything. That's definitely been helpful for them.

LogicMonitor's collectors, along with its templated integrations and dashboards, enable us to automate our onboarding process and roll it out to new customers. We've learned how to make it our own, based on what LogicMonitor provides us. We've been able to make ourselves more efficient, absolutely. The faster we can get online and onboard customers, the faster we can get to the point of turning their service on. That means that we can go from a non-paying customer who has agreed to work with us, to a paying customer who's now fully onboarded. We then have them working through the specifics of a managed services solution, outside of the monitoring tool, which is very important for us.

The breadth of things it's able to monitor, the simplicity of the deployment, and how quickly we can get it up and running are the biggest factors when it comes to helping us win new business. Functionally, there are no aspects of LogicMonitor that hinder that ability. It has definitely helped our margins, as an MSP, especially on the monitoring side, because we can get up and running so quickly. It's an absolute must for us to have the tool.

Seeing how easy it is to manage devices, how simple it is to add, remove, or modify a device, and the amount of data that's included out-of-the-box whenever you add a device, makes it far superior to any product. There are no add-ons needed. You license a resource or a device and you don't have to worry about adding a plugin to get all the additional metrics and the full depth of device data. This just happened last week on a customer demonstration call with a customer that has experience with SolarWinds. The customer saw how easy it was to get up and running on LogicMonitor and they were immediately sold and said, "Okay, give me a quote." That's a real scenario in which this product helped us. It's those aspects that not only help us gain new customers, but also to retain customers.

Overall, LogicMonitor saves us time. It's hard to quantify how much now, given that we've been using it for as long as we have.

When I consider LogicMonitor for future-proofing our business, with the ability to monitor customers' future IT environments, I'm pretty comfortable with it. That's because anything that we have come to them to request—whether it be a new feature, or having input into the UX and UI designs—they've been very open and very responsive to. Their support has been very accommodating. When it comes to looking at what could potentially be coming down the road, or to being future-proofed, I feel pretty good, given my experience with the types of special requests I've brought to them.

What is most valuable?

One of the most valuable features is the flexibility it gives for monitoring a particular device. There are a variety of ways we can get data into LogicMonitor.

In addition, it is an open platform that gives us the ability to add third-party application integrations, such as Slack or ServiceNow or Webex Teams.

There are also integrated features that allow for forecasting growth within the environment, not only for standard metrics like CPU and memory, but also for hard drive space utilization. Those are some pretty interesting and exciting features that are included in the platform.

On top of that, LogicMonitor has the ability to map out an environment at the network level.

It also enables us to drop a collector and automatically pick up everything in the target IT environment and map relationships. Obviously, you have to have the ability to reach the device. If there is anything stopping you via firewalls, then you can't get to it. But from a hypothetical standpoint, once a collector is in, we can capture everything very quickly based on an IP scheme. This has its advantages and disadvantages. The advantage is that we can capture everything very rapidly. However, if there is a misconfiguration on the client's network, then there could be the possibility of grabbing devices that are not needed. So there is some TLC that needs to be done when handling these, but it is a very useful aspect of the tool when it comes to onboarding.

In terms of instant visibility into all of the technology we will monitor for customers, it depends on the customer. But anything the customer wants us to monitor is leveraged. Some customers will say they only want to monitor telephony, while some will only want to monitor their network. We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status. It's pretty important for being able to provide a valued service to the customer about the overall health and availability of their environment.

We use LogicMonitor's dashboards quite a bit. In fact, we have our own customized dashboards. We use pieces of the templated dashboards and they definitely help in guiding us to places where we can pull certain indicators of how our customer is doing. Overall, we almost always end up having to adjust the dashboards to fit our customer needs, but the templated dashboards are significantly helpful. They tell us the different methodologies that we can use. We then take them and tailor them for the specifics that we need.

It's super-easy to customize the templated dashboards. For example, we have a school district customer with a campus. The template dashboards give us templates for wireless and templates for general networking and a few other things. We pick and choose the different widgets that we want out of those dashboards and we put them on the single dashboard for that particular school. That provides them visibility into all the things that are critical to them without having to go through multiple dashboards. We get rid of the things that they don't care about, things that our next customer may care about. We try to come up with dashboards that are specific to our customers' wants and needs and to give them, as much as possible, a single place to look for something.

LogicMonitor also hits the vast majority of technologies and complex environments when it comes to coverage, including on-prem, hybrid, cloud, et cetera. It does a really good job at covering the most-used technologies.

What needs improvement?

The only functional area I can think of that has room for improvement would be the dashboards. They could use a refresh. It would be nice if there were more widgets and more types of widgets.

For how long have I used the solution?

We've been using LogicMonitor for two and half years.

What do I think about the stability of the solution?

Up until two weeks ago, I would have said the stability of LogicMonitor is phenomenal. We had never had an issue. But two weeks ago, they had a bumpy week and a half.

What do I think about the scalability of the solution?

Scalability is based on our customers. The process for scaling the product out, for handling the resources from the collector side, is very simple. The one thing we've had issues with is that, when it comes to certain widgets on the dashboards, there are limitations on how many instances can be displayed through a widget. That is something that has caused us to rethink the way that we do our dashboards. Not that that's a bad thing, because it allowed us to actually come up with building dashboards for the client, and that has worked out really nicely. But that is one area where the scalability of the product has been a headache.

Not counting our API accounts, we have around 50 people using LogicMonitor. A lot of them are our frontline staff who are using the system to monitor, alert, notify, and to assist customers with getting their environments back up and running. The other accounts are used by our clients to log in and see their dashboards and devices. There are also folks on the backend, like me, who manage the environment, add the devices, manipulate the devices, delete devices—housekeeping.

We use LogicMonitor quite extensively and we have plans to increase our usage. Any of our clients who were not using us for monitoring before, rather we were being used for other projects by them, are either onboarded now or they're coming on board. The percentage of our clients that we have within monitoring is growing day by day and week by week.

How are customer service and technical support?

We leverage their tech support quite a bit. They have a chat and a phone feature. For the most part, we leverage their chat and we use them for a very wide variety of things. Overall, I've been very pleased with their level of support. They've done a really good job of turning things around and helping where we've needed the help.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

Once we were given our initial tutorial of the product, before we onboarded ourselves, it was very easy to do and we have found onboarding and implementation very pleasing. In terms of an MSP onboard, their documentation is some of the best documentation I've seen from a vendor. Based on their documentation, you can very easily onboard yourself. But we also had an executive-level onboarding demonstration.

Our original deployment had professional services involved and it took three or four weeks. But our customer deployments usually take a week. The biggest issue with our customer deployments is having the customer give us the right level of access. Slowdowns don't usually happen from the LogicMonitor side, they're usually from the customer side.

In our own company, we don't have a ton of devices to monitor, so it was really about making sure we got everything incorporated into the monitoring platform, including our cloud services.

In terms of maintenance, the collectors have software that needs to be maintained. The collector software is relatively easy to update. We can do it all from the portal itself. It handles the updates and restarting of the services, and it does so pretty quickly. Generally speaking, there is no downtime for the customer, whenever that happens. Outside of that, there are data sources and other source files that need to be updated on a monthly or  quarterly basis, according to how they're released. At times, those can cause some false positive alerts if they are not handled correctly on the import. In general, I'm the one who handles deployment and maintenance in our company.

What about the implementation team?

We did it ourselves, but we had a few days of LogicMonitor's professional services to get the initial deployment going. Those services were more of a consulting function. Overall, we didn't need nearly as much help as some customers might.

What was our ROI?

LogicMonitor has given our customers visibility into issues they didn't even know existed. In some cases, when we do assessments, we will actually load a customer's devices into LogicMonitor. In many cases, it gives us visibility into things like misconfigured stack modules or broken stack modules. Stacks or switches won't be stacked correctly. They'll actually be just this side of failing, and nobody has noticed it. Sometimes there are environmental issues that the customer hasn't noticed, where a particular location gets hot every day around the same time. They don't notice it and eventually it's going to result in something failing.

New customer onboarding, for us, usually consists of two things. One is getting access so that we can get it deployed and get visibility into the customer environment. And the second part of it is access for our team. We don't want the LogicMonitor component to take a lot longer. And, in fact, we're able to get LogicMonitor up and running for our customers much quicker than they're able to give us accounts.

It also reduces mean time to repair. When we see an alert, more often than not it's intelligent enough to help us come up with some sort of a solution faster. We can see a service or a server or a switch go into a critical state. A lot of the time, without something like LogicMonitor, which has the full visibility into the device, you would have to log in to the device and do some troubleshooting to figure out what's going on. It could just be that the temperature of the chassis is elevated and it's causing the system to underperform. I can't tell you how much time it saves us on something like that, but scenarios like that are what we experience on a daily basis. It definitely cuts time off of our troubleshooting and response. It's everything from temperature alarms, to disk space, to bad memory modules, and bad hard drives. You name it, we see it. And instead of having to log in and troubleshoot for an hour or two hours, the data is right there in front of us already and we can automatically dispatch somebody to go repair the device.

What's my experience with pricing, setup cost, and licensing?

We're currently paying $525 per month per device for monitoring, and a dollar per device for configuration management.

We've had customers who have reduced their costs by not having multiple platforms for monitoring. That said, especially with super-large environments, the cost model for LogicMonitor is the one area where we run into issues. It's the one area where it can hinder our ability to win new customers. But that's only in very specific cases of very large customers. We're usually competing with something like SolarWinds. SolarWinds is on-premises and the cost model is very different. Sometimes we have challenges with large environments competing against that kind of cost model, where we're paying per node. When there are 3,000 or 4,000 nodes, that cost model can get very expensive very quickly.

There are three different licenses that we can get. There is the monitoring license, there is a configuration-monitoring license, and there is a log license. We've generally gotten the configuration-monitoring version. We're trying to get to a scale where we can get those numbers down. What we'd love to see is the scale of cost per device going down. The numbers get skewed, even still. The cost for 2,000 or 3000 devices shouldn't be the same as the cost for 500 devices, and by a large margin.

The AIOps is the log portion of the solution. We would love to use it, but the way that they have it licensed, we haven't been able to. They want to license it for our entire portal and it doesn't really make a whole lot of sense to us. For us, it's challenging the way they have it licensed right now. We're working toward it.

It does give us the ability to charge a premium price but it's a little tough to call something a premium product in the monitoring world—even though we may see it as a premium product—because our customers don't look at it that way. For them, it doesn't matter how great the monitoring tool is.

Which other solutions did I evaluate?

We looked at three or four others, but that was several years ago. We chose LogicMonitor because of the simplicity of deployment and the time to get up and running. It's simple, but it's still as complicated as it needs to be to do all of the things that we need it to do.

The biggest lesson I have learned from using LogicMonitor is that other products are inferior. Also, compared to what we knew with the legacy monitoring tools, LogicMonitor has done a great job. There are definitely better ways of doing things than the traditional monitoring tools did. If a new customer has SolarWinds or OpManager or some other on-premises tool, sometimes they're afraid of the cloud tools. What we'll say is that the amount of things that it can do far outpaces the legacy tools.

What other advice do I have?

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.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: MSP
Flag as inappropriate
KN
Techincal Support at a tech services company with 51-200 employees
Real User
Top 5Leaderboard
A stable solution for backend application monitoring

Pros and Cons

  • "This product provides good visibility into applications at the backend."
  • "There should be a facility to integrate with other monitoring applications that are currently running in the environment."

What is our primary use case?

We are a system integrator and DX Spectrum is one of the products that we implement for our clients. In conjunction with DX Infrastructure Manager (CA UIM) and DX APM, this gives our customers visibility into what is happening end-to-end in their applications.

How has it helped my organization?

Some of our customers are large banks and government agencies, and they are getting value from using it.

What is most valuable?

This product provides good visibility into applications at the backend.

Some of our customers like the Service Desk aspect of it.

What needs improvement?

IP conflicts cannot be resolved automatically in the case where an IP address changes. This is one of the capabilities that SolarWinds has.

There should be a facility to integrate with other monitoring applications that are currently running in the environment. For example, if a customer is already running SolarWinds then it would be helpful if integration between these two was easy to do.

For how long have I used the solution?

I have been working with DX Spectrum for about 10 years.

What do I think about the stability of the solution?

In terms of stability, it depends on the environment. Sometimes, the application does not function well because of the type of security and policies that are in place. Certain policies will block the application, making it unstable. We learned this after some of our customers complained and we investigated to determine why.

When we come across a situation like this we start working with their security department to address the issues, and then everything will start working well.

Overall, I think that it's a really stable product.

How are customer service and technical support?

The support for this product is not encouraging. When our customers have issues, there is a delay in response from the support team. This causes some of our customers to doubt the solution.

Which solution did I use previously and why did I switch?

One of our customers was using SolarWinds, but have since switched to DX Spectrum because they were issues with it. Once they implemented DX Spectrum, they were able to determine the root cause of their problem and solve it.

How was the initial setup?

The installation is straightforward. The length of time required for deployment depends on the environment. For example, in a financial institution, it takes between one and two months because we need to do some information gathering and have confidence that we are meeting the requirements.

There are times when we are mid-deployment and the customer will stop us to say that they want something new. In cases like this, it slows down the implementation phase.

What about the implementation team?

Our in-house team handles the deployment for our customers.

What other advice do I have?

One of the issues that we have is that our customers are not aware of the product's full capabilities and what it can do for them. We are running our own campaign to give our customers a better understanding of the benefit they can get from it.

In summary, I think that it's a fantastic and durable product. For me, it is nice and I am actively recommending it to my clients.

I would rate this solution a nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
NR
Management Information System Officer at Kenmare Resources Mauritius
Real User
Top 20
Effective monitoring, scalable, and useful online resources

Pros and Cons

  • "We are able to monitor our virtual infrastructure, virtual machines, windows servers, databases, and the network using a simple network management protocol. We are able to pull almost all the metrics that we want, receive notifications, and have them integrate with telegrams for certain devices that are critical, such as UPSs."
  • "Zabbix does not draw automatic mapping of the network, this is something they should add in the future. There is a lot of effort that is involved in tailoring some of the settings which could be made easier."

What is our primary use case?

We are using Zabbix in my workplace to monitor the infrastructure.

What is most valuable?

We are able to monitor our virtual infrastructure, virtual machines, windows servers, databases, and the network using a simple network management protocol. We are able to pull almost all the metrics that we want, receive notifications, and have them integrate with telegrams for certain devices that are critical, such as UPSs.

What needs improvement?

Zabbix does not draw automatic mapping of the network, this is something they should add in the future. There is a lot of effort that is involved in tailoring some of the settings which could be made easier. 

For how long have I used the solution?

I have been using Zabbix for approximately four years.

What do I think about the scalability of the solution?

Zabbix is scalable because depending on the size of your infrastructure you can have distributed proxies servers across your network that will feed to the main server for the metric. It is similar to branches, where you can have one product for each branch and then the central server speaking in your central location, it works perfectly.

Our entire IT department is using Zabbix, which is 15 people, but we have approximately 600 devices being monitored.

How are customer service and support?

I have never had an issue that I needed to contact support. However, everything I have needed was able to be found online from the community or the Zabbix site manuals. Zabbix does offer support based on a subscription.

Which solution did I use previously and why did I switch?

I was using Centurion previously but I decided to switch to Zaddix because of costs. I was using the community edition of Centurion and it was very limited but with Zabbix, you can have an enterprise-class monitoring solution for free. I did research quickly and then I phoned Zaddix to see if they could solve all my problems without having to pay anything. This is when they confirmed I could and then I switched.

How was the initial setup?

The initial setup was easy. It took approximately three hours to get the server up and running.

What was our ROI?

By using Zabbix you minimize the cost of operation because you recieve an enterprise-class monitoring solution for free.

What's my experience with pricing, setup cost, and licensing?

The solution is free to use but they offer support as a paid service. If you can go read the manuals and do the fine-tuning based on your needs, you do not need to pay anything and you will have a full solution.

Which other solutions did I evaluate?

I have evaluated PRTG and SolarWinds.

What other advice do I have?

You do not need to spend a lot of money on solutions that have similar functionality, such as PRTG or Solar Winds. With Zabbix, you receive a free enterprise-class monitoring solution for free, as long as you know how to use it.

I would recommend this solution to others.

I rate Zabbix a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PA
Owner at a tech services company with 11-50 employees
Real User
Top 5Leaderboard
Scalable, easy to customize, integrates well with any platform, and they have good support

Pros and Cons

  • "The feature that I like the most and the best part is the customization."
  • "We have enquired if there are any possibilities of monitoring non-IPBS devices."

What is our primary use case?

I use this product as my network monitoring solution.

What is most valuable?

Being an engineering product, the customization is easy for us compared to SolarWinds and ManageEngine.

It's a total integrated package. The feature that I like the most and the best part is the customization.

This product integrates well with any platform, and I don't see any issues with it.

What needs improvement?

We have enquired if there are any possibilities of monitoring non-IPBS devices.

Currently, I am using another security tool called Nizami Network to monitor the security solutions or automation-based networks, which is something that Everest, SolarWinds, or Manage Engine cannot do. 

For how long have I used the solution?

I have been using Everest IMS for a couple of years.

We are using version 5.3, which is the latest.

What do I think about the stability of the solution?

In my experience, this has been a stable product.

What do I think about the scalability of the solution?

As the number of devices changes, this product adjusts, so it is scalable.

There are 250 users in our organization.

We plan to continue using this solution.

How are customer service and technical support?

I count on Everest's technical support more than anything else. I am 110% satisfied with their support.

Which solution did I use previously and why did I switch?

Previously, we used SolarWinds. It's a good product, but the pricing is too high, and customization is not possible.

We last used SolarWinds two years ago.

How was the initial setup?

It's a straightforward installation process. 

The length of time for deployment including installation, customization, and everything needed to get it running will take at least a week's time.

What about the implementation team?

We had help from Everest for the implementation and deployment.

What's my experience with pricing, setup cost, and licensing?

The price is much better than SolarWinds.

We pay for a number of devices on the accounts and since it is on-premises, we pay the maintenance charges for the year.

What other advice do I have?

I don't require a technical team. I only require a team of two people for monitoring.

I would recommend Everest IMS to others.

On a scale from one to ten, I would rate Everest IMS a nine.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Jose Robles
CEO & Founder at SISTECO
Reseller
Top 20
Lightweight, network discovery works well, and generally maintains the health of your network

Pros and Cons

  • "Network Discovery is a feature that our customers like a lot."
  • "The technical support could respond a little bit quicker."

What is our primary use case?

We are a service provider in the IT industry, and this is one of the products that we implement for our clients. We are using this product ourselves, and we have several customers who are also using it.

It is basically used for monitoring alerts, such as memory from a server has gone down.

What is most valuable?

Network Discovery is a feature that our customers like a lot.

The ability to maintain the health of the network is very good.

The user interface is okay.

This is a very lightweight solution.

What needs improvement?

The technical support could respond a little bit quicker.

A better console would be an improvement.

For how long have I used the solution?

I have been working with PRTG Network Monitor for approximately five years.

What do I think about the stability of the solution?

The stability is excellent.

What do I think about the scalability of the solution?

The networks in Guatemala are not very large, so scalability has not been an issue for us.

Our clients are typically medium-sized businesses.

We are working towards increasing the number of deployments.

How are customer service and technical support?

I would rate the technical support and eight out of ten. They could be a little better in terms of response speed. Usually, they respond the next day.

How was the initial setup?

The initial setup is straightforward and very simple. The length of time required for deployment depends on the size of the network but usually, we're talking about two hours.

What about the implementation team?

We provide technical support to our customers who are using this product.

On average, two people are required for deployment and maintenance.

What's my experience with pricing, setup cost, and licensing?

The pricing is okay and it is cheaper than some competing products.

Which other solutions did I evaluate?

The other product that our customers normally consider is SolarWinds.

SolarWinds is a more robust solution, and as such, it is much more expensive than PRTG. Most of the time, based on budget, our customers choose PRTG.

What other advice do I have?

For me, this is a nice solution and I would rate it an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
Get our free report covering Zabbix, ManageEngine, LogicMonitor, and other competitors of SolarWinds NPM. Updated: November 2021.
552,695 professionals have used our research since 2012.