SolarWinds ipMonitor vs Statseeker comparison

"IPAM is used for IP address reservation and tracking, helping us easily identify live IP addresses."

"The most valuable feature is the availability of end devices."

"IPAM is used for IP address reservation and tracking, helping us easily identify live IP addresses."

"It catches frequent flapping of the network and provides detailed reports of outages."

"This solution has helped us to proactively identify issues and push some of those fixes down to tier one."

"Statseeker helps to quickly see if you have a spike or something going on. In the future, we need to get NetFlow in the tool so we can see what the IP is."

"We're able to recover more expensive ports on our access line devices."

"We are a smaller enterprise, but we're watching approximately fifteen-thousand switchboards with no problem at all."

"If somebody is complaining about slow networking then this solution allows us to see various ports to find out whether they are being overloaded."

"Being able to look back historically at the uptime and downtime is invaluable."

"The monitoring provided by this solution helps us to track down and solve issues."

"The licensing cost is high compared to open source tools."

"The licensing cost is high compared to open source tools."

"The solution does not include enough features and has some performance issues."

"I would like to see a friendlier user interface in the administration tool."

"I would like to have soft alarming. If an inner-base all of a sudden triggers a threshold, we have to rely on a lot of other tools and then we go into Statseeker to verify it. If Statseeker would confirm it preemptively and trigger it into our network panel, that would be nice."

"I would like to see more comprehensive reporting and alerting."

"Maybe they could provide a little bit more flexibility on creating custom dashboards."

"I would like to see the solution incorporate diagnosis of the workstation."

"I would like the ability to update the dashboard. I would also like the ability to access via an API. Then I could produce a dashboard that my C level can understand. This is just so they can go and refresh whenever they want to and see what things look like."

"That user interface for selecting things needs to be a little more intuitive."

"We haven't seen an ROI."

"The solution is a bit expensive because the annual license does not include new features that are priced as add-ons."

"It's probably $5K a year for the license."

"Up until we actually talked to Statseeker, and Statseeker came and gave us an enterprise licensing model for multiple accounts, I would have said the pricing was not good value. The fact they've come to the party now and given us a very good discount, I would say it's probably about right, the pricing they're giving us now. But the retail pricing, if I went out and, as a separate company, and asked for pricing for one account, I probably would say their retail pricing is not competitive. The fact that they've given us a discount now because we have multiple servers across multiple accounts, I would say that pricing is about right, but not their retail pricing. It's too expensive."

"We now feel the pricing is a good value. Previously we had a just a normal license but now we've got an Enterprise license. Since the Enterprise, it's been a lot better value. We did think it was pretty expensive before, but with the Enterprise license it's almost less than half that price. If you have a number of accounts within the organization that use Statseeker, I would suggest get the Enterprise license."

"We paid $5,000 to $10,000 a year in maintenance."

"Statseeker is pretty cheap."

"We pay somewhere between $5,000 and $8,000 yearly in licensing fees."

"One thing that needs improvement is how it's licensed. I understand historically the company licensed it off a same charge for everyone. I understand the company needs to make money, but how they introduced the tiered licensing model, and then multiple layers of licensing was a bit of an issue. So, on the whole, coming up with a licensing model that isn't confusing and complicated and is easy to understand would be one way to improve the product. They have told me lately that they're changing how they license stuff, but they haven't made that - as I understand it - in their marketing material public knowledge as of yet. I would say that at the moment it's a bit convoluted. It's confusing. Some of their basic licensing model is a bit of a ripoff. If you go over five or ten support calls in the basic licensing model they start charging you for support calls. I think that's a bit rich."

"We pay a yearly maintenance fee of approximately $40,000 USD."