Statseeker Reviews

Our primary use for this solution is network monitoring.

This solution provides us with a quicker response in troubleshooting. It allows my engineers to do their job faster.

It reduces the troubleshooting time to pinpoint issues quicker. We now have a faster response to outages and thus faster remediation and up-time.

The most valuable features are that it is fast and easy to use. 

This solution is very in-depth and granular. I can look at one-minute data points and it does not roll data up over time.

It may be helpful to have more options in the alerting section.

The stability of this solution is very good.

Scalability is very good.

Technical support is very good. They've always solved every issue that we've had.

We used a home-grown solution prior to this one, so switching to Stateseeker was easy. It is inexpensive, it fits the need, and it was very fast to implement.

The initial setup of this solution is straightforward.

We implemented this solution in-house.

The ROI comes from the reduction in time that our network engineers spend troubleshooting, leaving them to focus on more important issues.

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

We did evaluate one or two other options, but we chose this solution because of the ease of use and deployment, as well as the simple interface.

This is a great product for anybody looking for network monitoring, and I would highly recommend it.

Having that one-minute granularity, that doesn't roll up over time, is incredibly important if we want to do any historical troubleshooting.

I would rate this solution a nine out of ten.

Our primary use for this solution is troubleshooting. We use it for logging and monitoring the routers and switches in the environment. It assists us with capacity planning.

This is a very cheap solution in order for us to accomplish what we needed to do in terms of providing visibility into the network. The visibility is such that it allows us to be a little proactive when it comes down to issues in the environment. It provides us with graphs and stats that we can use to make sure that there is not an issue with the network.

This solution complements our network monitoring. We have other products that provide a more comprehensive type of monitoring, and this one supplements that, especially for the retail environment.

It allows us to have some visibility into our service provider's equipment. It provides us the last-mile circuits down to the stores that we have.

It has helped our network admin team because it gives them visibility into the environment when there are issues. Workload-wise, I think it probably saves them time.

It just allows us to be more proactive. It gives a way to diagnose issues when they arise.

The most valuable feature of this solution is the simplicity of adding new devices into it.

I would like to see more comprehensive reporting and alerting. We do have other, more expensive solutions that handle that aspect of it. However, it would be nice to be able to specify baseline thresholds. If we're approaching those then we would be alerted, and it would probably help us with our job of troubleshooting.

This is a very stable solution. It hasn't gone down.

Scalability-wise, it's a monitoring platform so it's pulling these devices via SNMP. I would say if I needed an additional service to take on the workload then I would just provide additional storage. It's very simple to install.

This component is so easy that we rarely needed to call support. When we did contact them then they were very effective. No issues.

The initial setup of this solution is straightforward.

We deployed this solution with our in-house team.

We have seen ROI through the ability to troubleshoot more effectively. That is where the benefits came in.

When it came to selecting this solution, it came down to cost. Our licensing fees are on an annual basis.

We looked at several options including Voyance, Computer Associates eHealth, and SolarWinds. The Statseeker solution stood out because it was simple to use and easy to deploy.

This is a good solution in terms of ease of use and ease of deployment. It is a cost-effective solution that provides basic functionality. However, the bells and whistles that other vendors have will need to be provided or enhanced in Statseeker in order for it to compete. 

The biggest lesson that I learned is how easy it is deployed.

I would rate this solution a six out of ten.

Our primary use case is for monitoring traffic.

This solution allowed us to track down trouble users.

Being able to look at individual devices is the feature we found most useful.

It's stable as far as I'm concerned.

Scalability has been fine for us, thus far.

I haven't had any personal experience with technical support yet, so I don't know.

The solution's granularity in terms of network visibility is pretty solid. I haven't used it too often lately though. I'm not in that section of the organization anymore.

I don't know that the solution has had much of an impact on the complexity of our network monitoring. It's just another tool we can use.

I'm sure Statseeker has helped a little bit with our network availability, at some point.

From my experience, I'd give it an eight out of ten. It has worked when I needed it to.

Our primary use case for this solution is network monitoring.

We have Statseeker alerts emailed to a Google group, and one of the members of that group is a Slack integration. This means that we get instant alerts on Slack, from Statseeker, whenever an event happens.

All of our UPS units are set to send SNMP traps to Statseeker whenever their batteries are in need of replacement, or they start failing self-tests. Statseeker then generates an alert based on that trap, which proactively tells our UPS people that this battery is in trouble.

The most valuable feature is the ping going out every second, which gives us almost instantaneous alerting.

The user interface allows us to sort according to the source of network packets, which helps us to quickly narrow down problems.

This solution would be improved with better automatic discovery for ping-only devices. Every time we add an access point, which is a ping-only device, we also have to remember to add it to Statseeker. It would be very helpful if while doing a ping sweep of our network, once Statseeker discovers a new device, it performed a reverse DNS lookup on the IP address to get the hostname and then automatically add it.

The stability of this solution is awesome. Except when it comes time for upgrades, we don't touch it and it just keeps going.

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

Technical support for this solution is great.

We have been using Statseeker the entire time that I have been with the company.

I was not with the company for the initial setup and deployment.

We receive discounted pricing for being an educational user. Compared to other solutions such as Zabbix and AKiPS, this solution is very well priced.

We have looked at a couple of other solutions like Zabbix and AKiPS, and Statseeker has consistently underpriced everybody.

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.

I was primarily using this solution for network traffic analysis. We are switching to another product.

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

The most valuable feature is the ability to look at historical traffic.

A more user-friendly interface would help because it is sometimes difficult to find specific data that you are looking for. It would be nice if I could easily select individual interfaces.

It would be helpful to be able to view specific ports, more easily.

From what we have discovered, it is not really a single pane of glass.

Stability-wise, this is a good solution.

I do not feel that this solution is very scalable. It is sometimes hard to drill down and find specific interfaces that you need to track.

I have not dealt with their technical support.

We did not use another solution prior to this one. However, we are switching from Statseeker to Observium. The reason for the switch is that in Observium, the interface is really well-refined. You can select individual interfaces and you can pull up graphs really easily.

I was not part of the initial setup.

One of our in-house staff performed the setup.

I have not tracked the ROI.

This is a solution that is useful when you can find the information. It would benefit from being able to view specific ports more easily.

For my recommendation, I would suggest Observium over this solution.

I would rate this solution a five out of ten.

Our primary use case for this solution is network alerting.

This solution helps us to track down problems faster. Whether it is a down network switch or a down router, we can get back online faster for the customers.

When we are alerted as to something going down, it could just be power related or a circuit from the ISP. After finding out that it is down, five minutes later I might get an alert to say that it’s back up. This saves me the hassle of having to contact the customer.

The most valuable feature is the alerts that happen when something goes offline, such as a network switch, router, or wireless controller. We also get alerts for temperature issues and IDFs.

I would like to see the solution incorporate diagnosis of the workstation. A lot of times, the Network Engineer will blame the network first, even though it might be a desktop problem. For example, the drivers might be outdated, the memory is horrible, or the CPU is overwhelmed.

I would like to see all of the reports put up in a nice, GUI format, that shows whether devices are up or down, and the severity of any problems.

This is a very stable solution.

This is a very scalable product that we could make even more use of. It could, for example, monitor all of our wireless access points, but we don't use it for that. Potentially, we would be overwhelmed with this much information. We use this solution mostly for switches, routers, and controllers.

I have not spoken with their technical support, as it is another person on my team who administers the solution.

We use other solutions to handle different devices. For example, we run SolarWinds and Network Reporter. We use Cisco Prime to monitor and report on our wireless access points. Cisco Prime also reports on switches and routers, but it would be nice to consolidate everything down to one or two products.  

As our enterprise continued to get larger, we needed a solution that could support and inform us on a lot of devices. This is why we implemented this solution.

I did not perform the initial setup, but my understanding is that it was straightforward.

We handled the implementation and deployment in-house.

I would recommend this solution because I like the alerting functionality for systems that are down or up.

I would rate this solution an eight out of ten.

Our primary use case for this solution is fault management.

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

The most valuable features are the quick retrieval of performance data, and its ability to poll tens of thousands of interfaces at short intervals.

The single pane of glass for fault and performance data is very helpful.

I would like to see NetFlow improved, with better reporting capabilities that are similar to Scrutinizer.

I would like to see some layer two and layer three topology mappings, similar to what NNMi and SolarWinds presents. For fault, it's very good, but for tier one, they like to see pictures.

This is a very stable solution.

The scalability of this solution is very good.

I would rate their technical support a nine out of ten.

We used HP NNMi prior to this solution. However, they out-priced themselves so we switched.

The initial setup for this solution is straightforward. This is a turnkey solution and it is very easy to deploy.

I implemented the solution myself.

We have not seen ROI.

We have used SolarWinds and HP NNMi. We decided that Statseeker was by far the best solution.

My suggestion for anybody considering this solution is to evaluate at least four other products to see what works best.

I think that the NetFlow portion of the solution needs to be enhanced, but the fault and performance stuff is solid.

I would rate this solution a nine out of ten.

We primarily use this solution for monitoring. We check primarily for failures or latency in the network. 

This solution helps us to find the problem endpoints sooner.

Depending on how you sort your data, you can have a problem area come up to the top of your list. It also depends on what you are polling for, such as interface utilization, packet drops, or errors.

The most valuable feature is the dashboard, where you have everything right there on the screen.

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

This solution is pretty stable, and we haven't really had any problems.

I have not used technical support for this solution.

We did not use another solution prior to this one.

I was not involved in the initial setup of this solution.

One of our in-house teams handled the implementation.

I would recommend this product. It does what it is supposed to do.

This solution will help to find problem endpoints sooner, or other issues such as throughput and network congestion.

I would rate this solution an eight out of ten.

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.

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

The most valuable feature of this solution is NetFlow.

In terms of being able to see everything at once, Statseeker is not quite there yet.

It would be very nice to have the Cisco ACI option included in the regular license.

The newer version has bugs in a feature that I want to use, so I am unable to upgrade from my current version because of that. They are aware of this problem and will let me know once it is solved.

The stability of this solution is great compared to other solutions, such as SolarWinds. Statseeker is one step further.

Technical support is great, and I don't think that I'm going to have an issue with them.

In the past, we used SolarWinds and find that Statseeker is more stable.

The initial setup for this solution is straightforward. Everything is online, and you simply follow the instructions on the web page step-by-step. It is very clear and nothing is difficult.

We performed the deployment in-house.

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

The Cisco ACI option is not included in the regular maintenance fees.

We evaluated ThousdandEyes and decided that it was not quite as mature as Statseeker, so we opted for this solution.

We also considered Splunk.

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.

Our primary use of Statseeker is for our interface. In our data center, we are typically a Cisco shop. We can now look thirty days into the future based on past stats of trends or fashion. 

If we have 10 servers in the field office, we can jump up to twenty based on utilization. We have the evidence. It is a lot of manual work to create those reports, but a bit easier now.

Statseeker helps solve an asymmetrical routing issue we had before. We could see traffic going out of one interface, but not coming back in.

An operations guy made a change and told us it was good. We didn't check it, we had too much going on. When I clicked in and looked at the traffic, you could tell it wasn't right. I had to log in and correct them so. That is a pretty good example of basic metrical routing.

Statseeker is quick and very simple to use. We want to keep it like that. It has to be simple.

The solution has affected our workload with all our network admin teams. They don't use this tool as much as I probably would like them to use it for initial troubleshooting. 

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.

This solution hasn't affected our network availability. It's helped because we can see when things go down or when things come up. If we have a circuit maxed out, we can reroute the traffic, and do different things like that.

For a reduced cost, it is not possible because our network is so big and part interface. Maybe if we got a single router in the field office it would reduce the cost. 

It's probably not a model we are going to go with because we like to have dual connectivity, dual routers, and dual switches set up.

With Statseeker I'd like to see some flow, i.e. what's tuning-up the network. The trend I like is managing the traffic load by going to the cloud. 

Statseeker tells you routing-wise how things are working, in terms of transmit and receive. You shouldn't be transmitting more than you are receiving. It depends on the traffic, but it should just mix and match. 

With Statseeker, we caught a lot of issues. We have a lot of operational issues.

The stability of the solution is up and running. We had once had an issue a couple of years ago with upgrading the code. Resolved it within ten minutes.

It does scale well. You have to pay for your account, but I had no issues. We've used this tool for probably eight years, maybe ten. 

The scalability of the solution helped us to implement SDN. It's going to take probably until next year. We have too many other projects going on right now.

We have multiple data centers and multiple campus locations. We have dual wire carriers. We can see transmit coming in, receipt coming out. 

I have Statseeker set up for routing. I can see when the interface goes down. Then the traffic flow over onto the other router. It's nice to have that.

Statseeker tech support was bad around 2-3 years ago. I have had the new support for maybe 6 months to a year. I'll be upgrading the codes. I haven't rung customer support in a year or so.

For software and hardware, how we spend the money depends on demand and what we have going on. One year, we could have campus refresh, and if we have a little bit of change left over we'd spend it on software. We have had Statseeker as long as 8-9 years ago.

The initial setup was straightforward. We did discovery of how many devices go onto a monitor. It didn't take too long to do it.

We bought directly from in-house sales, the Australian guys.

We have sixteen to twenty-thousand interfaces at a minimum.

Statseeker reduces the complexity of your network monitoring. It is easy. You don't have to go in and show the guys how to log in and check this and that. They can just click whichever router is required for the interface. 

I would like a single pane of glass. It's not there. We have so many devices. We have a huge network. We go over fifty thousand nodes in the US, UK, Ireland, and Poland.

We use different tools. Statseeker is one of them. Not all of them offer a single pane of glass for administration. You have to click in, dive in, and dig into the ways.

On a scale from 1 to 10, I'd rate Statseeker with a 9 based on what I have seen there now. I'd like to get the flow. I'd like to get more visibility. It's probably me being harsh. But the tool works. I am very happy with it.