Statseeker Competitors and Alternatives

What is our primary use case?

Our primary use of Statseeker is for monitoring and the utilization of our network devices. We initially got Statseeker because we needed more visibility and better historical data.

What other advice do I have?

Try to find someone who's worked with the solution, get their take on it, and maybe try to compare it with a different solution to see the pros and cons. I would rate this as an eight out of ten. There are no perfect products out there, but Statseeker has been great. I've been using it for a few months now and it's served our purposes.

What is our primary use case?

We use Statseeker to monitor all the devices on our network. This includes: * the network switches * our gateways to the cloud * our kiosks that are mounted throughout our building * any other device we deem to be important We want to know exactly when they go down.

What other advice do I have?

Overall, Statseeker has reduced the complexity of our network monitoring once it's installed. It provides a single pane of glass to go and look at a snapshot if anything's down or having any transitions, i.e. within the last hour or last twenty-four hours. You can look at the data coordinator and if you see something red, you know something's wrong. If you don't see anything red, you know nothing's wrong. It just takes a glance. Even our help desk, if they're not in-network experienced, they can tell if something's down. The single pane of glass for traditional and SDN affects our network…

What is our primary use case?

We primarily use this solution for polling and interface utilization.

What other advice do I have?

This is a solid and reliable solution, but it's not intuitive with respect to some of the setup and some of the selection for reports. Eventually, you can work through it. I would rate this solution a seven and a half out of ten.

What is our primary use case?

Our primary use case for this solution is network monitoring.

What other advice do I have?

If this solution offers a trial then I would suggest giving it a try. In my experience, there is not much better than this. We set a two-minute bundle time so that we don't get completely inundated with alerts. There is a bug we have encountered, where if we accidentally add a ping-only device as an SNMP device, and then that device goes down, it doesn't report back as "down". Overall, I would rate this solution an eight out of ten.

What is our primary use case?

We primarily use this solution for monitoring. We use the Mac version. Our investment in this solution was customer-driven. When we have a request from a client business we look at what we have. If we cannot satisfy the request then we look into investments such as this.

What other advice do I have?

While I would recommend this software to a colleague, I would also suggest running different products at the same time to see what works best. I like this solution because I have used different products and I find this one is simpler. I would rate this solution an eight out of ten.

What is our primary use case?

We use this solution to control bandwidth congestion, and also for the recovery of unused data network ports.

What other advice do I have?

This product provides some good functionality. However, the reporting is right to left, which is less than ideal, the cost is significantly high, and the NetFlow capabilities are lacking. My advice is to go with AKIPS, rather than this solution. I would rate this solution a seven out of ten.